:::::::... 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/attachment.php?attachmentid=2453825&d=1387010535
http://forum.xda-developers.com/showthread.php?t=2276036
Devil Kernel Manager
DevilAppSGS.apk
http://forum.xda-developers.com/showthread.php?t=2558082
https://play.google.com/store/apps/details?id=com.metalignus.devilappsgs&hl=en
Trickster MOD
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
ROM Toolbox Lite is excellent with the stuff available in it...
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&feature=search_result
I also found this nice Lulzactive controls app
specifically for the Lulzactive Governor and explains things nicely
https://play.google.com/store/apps/details?id=com.tegrak.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=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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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!
::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: ::::::::::::::::: :::::::::::::::::
.
@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?
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?
Click to expand...
Click to collapse
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)
.
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)
Click to expand...
Click to collapse
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?
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?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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?
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.
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
by flashing this:
3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip
http://www.androidfilehost.com/?fid=23269279319202534
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
Click to expand...
Click to collapse
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?
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
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
so really that recovery is only activated within the boot.img
ztotherad said:
so really that recovery is only activated within the boot.img
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
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.
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
Click to expand...
Click to collapse
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
.
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
.
Click to expand...
Click to collapse
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 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
Click to expand...
Click to collapse
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
Related
Ok, here it is guys! I know all you stock captivators have been anticipating this!
This is the stock KH3 and now KI1/KI2 kernel with clockwork recovery injected. Also my first go at a project like this.
The only issue I see is that /system won't unmount, so no nandroid backups (they won't restore). /system will now unmount, but restoring a nandroid backup will totally bork your phone, don't even try! (unless you are ready to odin/heimdall back!)
I have to give a huge thanks to eXistZ, he helped point me in the right direction, and generously gave me scripts he uses. And let me bug him on a regular basis. Thanks dude! And a thanks to Chainfire for pointing me in the right direction to finding why system wouldn't unmount.
Anyone is available to use the kernel any way they like. Cook it in roms released here, flash it to your personal rom, or stock KH3! Take it apart, look at the pieces, see if you can make it better! I am far from a pro at this, and it may not be perfect, use at your own risk..yada yadda.
Nandroid is still broken, still looking into it.
Update 9/11/11
I am releasing this now, because it appears that the /system not unmounting issue causes problems for full wipe roms, with big system changes. This should help. Just don't try to do a nandroid restore, it will make your phone hang at the at&t logo! You have been warned!
It is also possible to format /system from cwm if anyone feels the need (you can't boot after, so only do so if you are also planning on also installing a rom).
The links below should be fixed to point at the new versions.
KH3
Here is the odin flashable version flash it first if your on stock: Link Mirror
Here is the KH3 cwm flashable kernel5! Flash it second to get init.d support if your on stock or don't already have cwm LINK It has init.d support and the same tweaks listed for the KI1/KI2 kernel below.
Here is a heimdall package for stock kh3 with the cwm kernel3 built in. Link It will wipe your phone! Make A backup as necessary. Hopefully it can help people go from stock to a custom rom in fewer steps, or recover from a soft brick Let me know if you find an issue with it. It contains factory.rfs, dbdata.rfs, chache.rfs, param.lfs, modem.bin and the cwm_kernel zImage.
KI1 KI2
Update 9/29/11
I'm just going to do one version for KI1/KI2 now that it appears the same kernel will work on both.
Here is the original odin flashable kernel to give you cwm, flash it first to get cwm if you don't already then flash the cwm with init support. Link And my original post with the stock kernel.
Now for the good stuff!
mtcarey modded my kh3 kernel here, to add init.d support, made changes to allow ADB / DDMS to run as root, and symlinks from Busybox to "ls" and "ps" have been removed from /sbin so that DDMS will work correctly. They now fall back to Toolbox links in /system/bin. Thank him in his thread! Awesome work! I think I have all of those mods pulled to ki1/ki2, plus:
+ Juwe11's LMK settings
+ Tweaked Kernel Scheduler Settings
+ Tweaked IO Scheduler Settings
+ Tweaked Ondemand Governor/Sampling Rate
+ Tweaked Readahead to 512 on internal/external SDs (mmcblk blocks)
You can get it here: Link Mirror
If your on stock you will need to flash the odin version to get cwm then the new tweaked one for the init.d scripts, /etc/init.d/S99complete is needed! If you remove it, the phone won't boot!
For any of you losing root when you flash my kernel or for anyone on straight stock, you can get root by flashing ChainsDD root: http://forum.xda-developers.com/showthread.php?t=682828 or what I mention below.
If your on straight stock and don't already have cwm, flash my odin version first, then ChainsDD from the above link, or:
Grab my cwm zip that I made from ChainsDD and my latest kernels (with tweaks)
KH3 and root
KI1/KI2 and root
Hopefully those will help.
SWEET!
This Man Is A Beast, like the good one on X-men!!
Great Job.
You all reading this and wondering;
= its Stable
= its has awsome batterylife
= easy to use
= and worry free.
GO TEAM PHOENIX!!!
For those wanting the stock E3 recovery back....(for the life of me I don't know why) I will be posting it here today.
hah, a fellow ohioan would be the one to release this. good work bud.
So...are you guys gonna make my cappy NOT suck anymore?
Sent from my GT-I9000
Awesome! You rock dude, thanks!
Great job ! Appreciate the hard work by all !!
Dont forget to vote his thread.
a-hem' Fivestar*
Amazing!
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
Thanks a lot...
U R THE BEST!.. Good luck with your future work. Hope to see more work from u.
Thanks again for all the hard work.
keller.jeff said:
So...are you guys gonna make my cappy NOT suck anymore?
Sent from my GT-I9000
Click to expand...
Click to collapse
Send it to me, I don't think they suck!
But, yeah, custom stuff on your phone can only make it better.
Awesomeness.....!!!!
Sweet! Nice job y'all!
Any reboot during call issues like on kf1? I know its early on, but wondering if anyone has experienced this on any kh3 version. Thanks for ur work. No cwm has kept me from trying kh3. Can't wait to flash.
Sent from my SAMSUNG-SGH-I897 using XDA App
i know what crash you are talking about, and i had it too on kf1, but have yet to experience it on h3. that doesnt mean its gone though because i havnt given it the same stressing as f1.
Da Bomb...
Did this break data connection for anyone?
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
I would like to know how to do this. But I will try to do it by myself first.
If I getting stuck please let me PM for your help
I've heard word of "the best" battery life. Can anyone attest to this? I can't believe that from Samsung's track record....
Great work!! Flashing after post. Far as battery life. Every phone and phone user is different. So life varies. Me I crank brightness up use wifi, and GPS always. Like tonight buying a car 260 mile round trip used GPS to get there started with 100% and was. On 26% whenever I got there. Just appreciate that you have a device that makes your life easy and fun! I always turn wifi off and do my best to conserve battery. The captivate is truely a bad ass device. My brother was over last night. And we were playing with phones. He dropped his iPhone 4 and used my cappy cause its better he said
Sent from my SAMSUNG-SGH-I897 using XDA App
great work dude.......
Many of us will use CyanogenMod 10 and Siyah kernel build by gokhanmoral, as it is maybe one of the best combinaison for a powerful and smooth device. My past experience with CM7 and Syiah Kernel show me some questions will hardnessly find a right place in the CyanogenMod 10 nightly builds | DISCUSSION THREAD neither in [KERNEL][ICS] SiyahKernel v3.0 thread. The issues you may experience could in fact be due to this specific combinaison, and when posting in CM10 thread you will be told to use only the custom Cyanogenmod Kernel, and when posting in Syiah thread you will be told your issue is CM10 relative and has nothing to do with the Kernel!!
Thus the idea to create an area dedicated to users running both Syiah kernel and CM10 ROM. They won't waste time posting and being flamed on both threads. I already can see some users jumping from one thread to another one.
When posting in this thread, you will lighten the main discussion threads, and browsing them will be easier.
Before you post, do a minimum of search in both threads to ensure there is not an easy and quick answer.
Then think twice, be as much as precise as you can when presenting your issue. We all will gain in efficiency and save our time.
Please keep this thread clean and useful in order to avoid "mass browsing". Refrain from flaming and adding to the crap ; do not offense, even in case of n00bish and stupid question; avoid any needless posts about your mood such as "Go Syiah", "Codeworkx, you are the best", "I love my phone" or any out of topic consideration.
learn a litle bit about BBC Code, and try to organise your post.
Be accurate and smart as much as you can. Answering will be easier and your post will help other users.
Both main threads are heavily busy, so I hope this one will help us in getting quick answers for both advanced users AND n00bs.
[color=#ooBFFF]It is up to you now to keep this place clean and convenient.[/color]
SEE POST 2 FOR LAST UPDATES AND POST 3 FOR BOOT TO GECKO
Unfortunately Mozilla decided to drop SGS2 development. I will still let the post in case Mozilla Dev team change their mind.
All credits are given to Teamhacksung, Cyanogenmod and Gokhan for their hard and clever work. Below are links to original work:
CM9 :
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=1419102
Cyanogenmod : http://www.cyanogenmod.com/
Teamhacksung : http://teamhacksung.org/
ROM download link : http://download.cyanogenmod.com/?device=galaxys2
You can download directly the nightly build to your device with Rom manager Premium.
Unless you are a flash addict, best is now to stick with official and stable CM9, currently 9.1
http://www.cyanogenmod.com/devices/samsung-galaxy-s2
CM10:
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=1794758
Modem + RIL installer : http://forum.xda-developers.com/showthread.php?p=31416701
CM10.1:
XDA Forum main discussion thread : http://forum.xda-developers.com/showthread.php?t=2036229
Still under development as Samsung code source is missing.
Syiah kernel :
XDA Forum Dev thread : http://forum.xda-developers.com/showthread.php?t=1555259
XDA Forum discussion thread : http://forum.xda-developers.com/showthread.php?t=1658647
Syiah Kernel for SGS2: http://www.gokhanmoral.com/
Kernel download link : http://www.gokhanmoral.com/
Extweaks thread by droidphile : http://forum.xda-developers.com/showthread.php?p=23616564#post23616564
Comprehensive and exhaustive list of Extweaks UV values by gecko95gek: http://forum.xda-developers.com/showpost.php?p=26755476&postcount=850
You can download directly the kernel to your device. Open your browser, go to gokhanmoral website. You will find an optimized version for device, with all listed kernels. Clic on it, the changelog will appeared as well as a download link.
Extweaks and Dual Booting FAQ by Droidphile
http://tinyurl.com/cvjcl52
http://forum.xda-developers.com/showpost.php?p=24233132&postcount=5
UNDERSTANDING ANDROID
Below is a link to a must read document about Android and how it works on your device. The pdf is quite big, 485 pages, but do not be afraid. All is very well explained, in a very clear english and academic fashion, so even n00bs can understand. There is a lot of pictures and very practical explainations.
http://tinyurl.com/dxr8dpx
All rights reserved www.hardkernel.com
Kernel cleaning scripts
Most often, custom Kernels create special directories and config files. If you want to switch from one custom Kernel to another one, it is not a bad idea to run this script before flashing the new Kernel. It will do some cleaning on your file system by removing all custom tweaks let by the Kernel.
http://forum.xda-developers.com/showthread.php?t=1363738
##My current configuration : [color=#ooBFFF]CM10-nightly-20121107[/color] + SyiahKernel [color=#ooBFFF]5.0.1[/color]##
##I am an Archlinux user, and some settings and way to operate are sometimes different from Ubuntu. So do not hesitate to ask here in case of any problem with Linux in general, and Arch in particular.##
Below is a list of major usage difference, known issues or tricks.
I will do my best to keep it up to date and exhaustive, according to my own usage of my SGS2 device and what I can read on the forum.
Noteworthy differences
Syiah Kernel use its own touch CWM. You can move around with touchscreen or screen buttons. When you backup, restore or install zip from sd card, use INTERNAL SDCARD instead of SDCARD (the opposite of CM9 practice).
Most kernel settings are done with an app called EXTWEAKS. This is a free app from Android Play. You need to give root access to Apps under Settings > Developper options > Root acess to allow EXTWEAKS to operate the changes. Settings from Extweaks will override the ones from CM9, like CPU govenor and clock speed.
Flashing Syiah kernel will install many .syiah folders and config files on your device. If you want to get rid of them when back to CM9 default kernel, flash syiah-resetdefaultprofile.zip (link to the file on his website under SiyahKernel v3.0beta3 section). It is NOT mandatory, as CM9 will be fully functional with these config files, but it is best to keep your system as clean as possible.
Using this kernel in the correct way, enjoying all the fine tunings, is not so easy and need a bit of knowledge. IF you have no idea about how work your CPU and GPU, stick to the default configuration. Wrong settings will cause malfunction, lags, glitches and make scrolling jerky.
Since version 3.1b1, dual booting is enabled. All settings are done in the Syiah custom CWM. It allows you to choose at boot time between two ROMs
[*]BLN IS WORKING NATIVELY SINCE KERNEL 3.2b4
GOOGLE NOW IS A HUGE BATTERY DRAINER ON CM10
2012/09/13
CM10 is now my first ROM. Flashed CM10-nightly 0913
flashed syiahkernel 4.1.5.
2012/09/13
Flashed CM10-nightly 0928
Battery is still draining very fast
some issues with superuser. Moved to SuperSu from chainfire (Play store)
2012/10/15
Flashed CM10-20121015-experimental-i9100-jbmalioshwc2-vsync_sysfs-changmin (link above under CM10)
Battery is better, memleak fixed.
Flashed Syiah-s2-v4.1.5-cm10-jbmali-vsync-sysfs
Flashed new gapps 20121011
2012/10/20
Flashed CM10-20121017-nightly
Flashed Syiah-s2-v5
2012/11/07
Flashed CM10-20121107-nightly
Flashed Syiah-s2-v5.0i
2012/12/09
You will find a 4.2.1 experimental CM10 ROM at this following link :
http://forum.xda-developers.com/showthread.php?t=2036229.
Teamhacksung has made a very hard work to port 4.2.1 to the SGS2, as they don't have any opensource drivers/kernel from Samsung.This build is still experimental.
2013/01/04
I am still on my old config with CM10 as I am not convinced CM and SyiahKernel are yet fully stable.
2013/02/28
I WILL NOT FOLLOW THIS THREAD ANYMORE .
CM 10.1 is totally broken on this device and there isn't even a stable release. Samsung broke things.
Gokham has some trouble building Kernels.
DUAL BOOT CM9/B2G : A QUICK & DIRTY HOW-TO
DEVELOPMENT ON SGS2 HAS BEEN STOPED. IT SEEMS WE WILL NEVER SEE THIS OS FULLY WORKING ON OUR DEVICES
B2G is Boot To Gecko, a Mozilla OS for device project. I have been following it since a while, and it is a very active and promising OS for your SGS2. It is in its very early stage, so do not expect to use it daily, but it is improving very fast.
When Gokham talked about dual boot, I immediatly think to B2G, as I am not interested in any other custom ROM than CM9. Thanks to its new 3.2.2 Kernel, it is now very easy to give it a try.
The work has been done by PULSER, building the B2G image, and GOKHAM, for dual boot capability. So a warm thanks to both of them, and of course to the B2G Team.
I will come back in the coming weeks with a more fine tuned How-To, as I did the install in the rush this morning.
How-To
I did everything on Ubuntu 11.10. Windows users will use Odin, and I am sure it works with other Linux distro.
I assume you have SyiahKernel v3.2.2. on your SGS2
I assume you have a working SGS2/Linux communication. It means a working ADB, USB and Heimdall. I used heimdall 1.3.1, and some users report issues with 1.3.2. Furthermore, I used Command Line, as the heimdall GUI front-end didn't work for me, and I didn't take time to investigate.
I assume B2G will be your second ROM.
Download the last two files of the list here (system and data image):
http://villainrom.co.uk/pulser/B2G/
Untar <Boot2GeckoDualBootsystem.tar> and rename it <hidden.img> if Pulser haven't changed the name (was mistakenly named <hiddenfs.img>)
Unzip <data.img.zip> and get a 2G <data.img>
Boot your device in CWM Recovery.
As mentionned on SyiahKernel website, Mounts and storage > format /secondrom_data and /secondrom_cache.
Reboot your device in Download Mode.
Plug your device
Run this command is to make sure heimdall is working
Code:
$ heimdall detect
Device detected
It shall return <detected>
Code:
$ heimdall flash --hidden <PATH/TO/HIDDEN.IMG>
---- you will see progress until 100%. It hangs a litle bit around 88%, just wait.
Reboot device on Android
Run this command on Linux:
Code:
$ adb push <PATH/TO/DATA.IMG> </sdcard/.secondrom/data.img>
File is big, so it takes a while (a few mn).
Reboot. On the dual boot screen, you have 3 sec to press your Home Button. Then you shall see :
Booting for the second ROM...
IF second ROM doesn't boot quickly (around 10-20 sec), then there is a mess somewhere.
Normally, you will quickly boot to B2G Lock Screen.
!!At this state, you will have nothing more than the lock screen. You need then to make-isntall Gaia!!
Let's make-install Gaia now
1-Dirty and quickest way-TRY THIS ONE FIRST
I did not yet tested this shortest way. It will save you a lot of time cloning unusefull stuff from Git.
You may have in this case an error with adb. Try to copy your own adb executable in the path where make gaia is supposed to find it.
Plug your device running the second ROM, B2G.
Then:
Code:
$mkdir ~/B2G
$ cd ~/B2G
$ git clone https://github.com/mozilla-b2g/gaia
$ mkdir /glue/gonk/out/host/linux-x86/bin
==> copy your adb executable in this directroy. Check permission
$cd gaia
$ make install-gaia
This is very minimal, but shall work.
2-Academic way
Code:
$mkdir ~/mozilla/gits/B2G
$ cd ~/mozilla/gits/B2G
$ git clone https://github.com/mozilla-b2g/B2G
$ cd B2G
$ make sync
Time for a beer...or two!! It takes long
Boot your device to second ROM, B2G now.
Plug your device to the computer.
Check if adb is fully working :
Code:
$ cd ~/mozilla/gits/B2G/
$ adb devices
List of devices attached
00194a183cd97e device
!!If you have no number and device, adb is not properly working on your system.!!
copy adb executable in /usr/bin
*EDIT : do not stress on adb, as in this case, when making gaia, an adb will be built.
Assuming you are still in the gaia folder
Code:
$cd ..
$ make install-gaia
ET VOILA.
You will soon see the gaia frontend.
useful links:
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Setting_Up_Boot_to_Gecko_Build_Environment
https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2
http://forum.xda-developers.com/showthread.php?t=1518467
https://www.villainrom.co.uk/forum/threads/introduction-to-dual-boot-of-boot2gecko-b2g.5436/
http://johnhammink.blogspot.ca/2012/05/part-3-updating-your-gingerbread.html
There is a very active B2G mailing list.
All credits to B2G dev, PULSER and Gokham.
On a serious note now first of all great posts you have made here. You have one way a right to be here so people can talk about the development issues that they are facing with the kernels but on the other hand this has nothing to do with development and you are actually not developing anything. Thus this thread should be moved to General Section and not here.
Plus there are threads of were people can talk about what they are facing on the perspective threads of the kernels that they are using. But anyway best of luck.
While the thinking and intention are good,I think this thread would best be put in the General or Q&A section,as it isn't development.
Anyway,the threads are already too cluttered,that's a fact...
Please, may a Mod move this thread to Samsung Galaxy S II I9100 > Galaxy S II General.
It has no reason to be under the development section.
Thank You
EDIT: Thread has been moved to a best place, as it is not mint to talk about development, but more of daily use.
This thread is a very good idea. Will be using it in the near future when I try cm9 again.
Sent from my GT-I9100 using XDA
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
Click to expand...
Click to collapse
No need for you negativity. If you don't think it will work. Don't use the thread.
There is a need. Because people are using siyah on cm9. Whether they will continue, another persons guess, but why do you have to point out the negatives. Is it to prove your knowledge to the contrary? Well done!
Just say nice thread, or even better, nothing if you don't agree and let people get on with it.
rice and pea(ce)
bleuxeon said:
That's a good idea.
But gokhanmoral him self change his mind twice a day regarding the support of CM9.
So I m afraid your thread would have no sucess until he clearly stand that:
1) Siyah will support CM9
2) Siyah wil NOT support CM9
Click to expand...
Click to collapse
1-I am not after sucess , just think there is a place for such a thread, being me or anyone else. If I am wrong, that's fine the thread will die by its lack of participation.
2-your post is exactly what I don't want here: unusefull from a practical standpoint. You are not helping anyone with your remark.
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
more2come said:
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
Click to expand...
Click to collapse
Which governor did you use?
Sent with Tapatalk from my GT- I9100
gabx said:
1-I am not after sucess , just think there is a place for such a thread, being me or anyone else. If I am wrong, that's fine the thread will die by its lack of participation.
2-your post is exactly what I don't want here: unusefull from a practical standpoint. You are not helping anyone with your remark.
Click to expand...
Click to collapse
I anderstand.
My main idea remains : how can you create a thread about a kernel while in the same time the father of that kernel say that he wont support CM9..or maybe he would?
It sounds crystal clear that your thread is like talking about Galaxy SIV when Galaxy SIII isnt here
well actually Gokhanmoral said so himself:
"kjetal advised me a nice and good build of cm9 and I hope to install it tomorrow. and I hope not to come back to a samsung rom in near future...
that's all for now. I have to go back to work"
And I'm pretty sure his signature says 'cm9 nightly' as well...
shr33kant said:
well actually Gokhanmoral said so himself:
"kjetal advised me a nice and good build of cm9 and I hope to install it tomorrow. and I hope not to come back to a samsung rom in near future...
that's all for now. I have to go back to work"
And I'm pretty sure his signature says 'cm9 nightly' as well...
Click to expand...
Click to collapse
great news!
I simply hope he will not change his mind again.
more2come said:
I was trying nightly 20120319 and siyah beta3 for a while and had no major issues.
In comparison to the kernel compiled by codeworkx, I had massive scrolling lags in trebuchet launcher with siyah.
Click to expand...
Click to collapse
Did you install Extweaks? If no, I would recommend.
Start to play a litle bit with CPU and GPU settings. Do not hesitate, it won't break your device. Just go step by step. You should quickly see some improvment.
I'm using b3 with the latest nightly and loving it . I don't need mtp when I've got airdroid!
Sent from inside a black hole.
bleuxeon said:
I anderstand.
My main idea remains : how can you create a thread about a kernel while in the same time the father of that kernel say that he wont support CM9..or maybe he would?
It sounds crystal clear that your thread is like talking about Galaxy SIV when Galaxy SIII isnt here
Click to expand...
Click to collapse
it is not quite true that I won't support CM9.
actually, I am thinking about using it as my primary rom.
but there are some facts now: I am using Samsung ROM, I cannot test anything about CM9 and I am very busy.
those facts make it impossible for me to support CM9 now.
when I install CM9, it will be harder to support Samsung ROM. that is why I want to finish dual-booting.
subscribed.
gokhanmoral said:
it is not quite true that I won't support CM9.
actually, I am thinking about using it as my primary rom.
but there are some facts now: I am using Samsung ROM, I cannot test anything about CM9 and I am very busy.
those facts make it impossible for me to support CM9 now.
when I install CM9, it will be harder to support Samsung ROM. that is why I want to finish dual-booting.
subscribed.
Click to expand...
Click to collapse
Many thanks Sir for this clarification.
PS : I just tried to make you a donation, but when I click "donation" then I go to PAYPAL in Turkish (or other that I dont know) and I can't anderstand it at all.
I have allready made you a donation but PAYPAL was in my own language this time.
Ramelov said:
Which governor did you use?
Sent with Tapatalk from my GT- I9100
Click to expand...
Click to collapse
I tried ondemand (default), interactive and smartassV2 .
All lead to the same result, very laggy scrolling.
Scrolling lags decreased with beta5, but performance still is worse than the CM9 kernel by codeworkx.
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is KITKAT(Android 4.4.4).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
Bluetooth working --Still a WIP as some devices don't connect
Camera working --Still a WIP as the camcorder records in blue and a few minor issues
home key doesn't turn device on need to use power button--FIXED in the next nightly should be 4-5-2014
Battery draw around 50mA in sleep
Some experience SOD when hotword detect is active
Location service has stopped with Googles update looking into now
You tell me what you find.
4G Models are not currently supported
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(New Site is up Check it out)
Evervolv Bug Tracker: http://bugs.evervolv.com/
(Please have discretion when reporting issues, and be descriptive / helpful. Also understand that we'll have some growing pains with this. So don't expect everything to be perfect.)
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
If you already have evervolv installed you should see this build under testing if you refresh and can download that way.
No more nightlies Moved to 5.0 Lollipop
ev_tenderloin-1-23-15 Last and final for 4.0 -> Fix netflix
FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
--This is a flashing TWRP recovery with data/media and SELINUX support. I have tested 100% of the features and everything is working great as far as i can tell. Soo
with that being said. Use at your own risk 8). Make sure you save a backup from your current recovery just in case. BACKUP BACKUP BACKUP
--Broke Vibration as i updated kernel.
Click to expand...
Click to collapse
NOTE: Recommend a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
GAPPS
---These are the gapps i use. You should be able to use any that are KitKat compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Grabbing logcats and dmesg along with last_klog.
These are helpful in figuring out what is going on
Install the sdk in you PC http://developer.android.com/sdk/index.html
Logcat
"adb shell logcat >logcat.txt"
This will run until unplugged or ctrl c and all the content will go into that file
dmesg
"adb shell cat proc/kmsg >dmesg.txt"
This will run until unplugged or ctrl c and all the content will go into that file
Last_klog
"adb shell cat proc/last_klog >lastklog.txt"
This is for if you have a reboot run this right after the device starts back up and it will get me the last dmesg from before it reboot and will help determine the cause of the reboot.
This will help me and everyone that uses this ROM as i can determine the cause of issues.
Thanks
Thank you for the continued HP Touchpad Development and support Flintman.
Cheers:highfive:
Touchpad Toolbox By Jcsullins
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
[GAPPS][4.4.x/4.3.x] OFFICIAL 0-Day PA-GOOGLE APPS (Use Mini or Micro packages)
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Moody66 said:
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Click to expand...
Click to collapse
I haven't tested as its still a wip from Google. I do have it as broken in the op. But good to know that it boots 8)
Sent from my SCH-I545 using xda app-developers app
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
flintman said:
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
Click to expand...
Click to collapse
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
I have flashed with this recovery about 20 times now and only got the reboot to hang once. I'm looking into it.
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
install xposed + gravitybox. it works like a charm and has this feature and many others.
Sent from my Nexus 4 using Tapatalk
Okay, I am doing something wrong. I have downloaded the recovery multiple times from multiple devices. I have tried installing via TWRP and manually extracting the image to /boot.
Each attempt, I get:
Checking uImage... Invalid Size
BOOT FAILED!
Please SELECT to continue
Any thoughts? I can still load my backup copy of TWRP without issue.
Update:
After purging the other copies of TWRP from /boot, the new version loads without issue. Thanks flintman!
Discovered that the TP 4G not compatible with the test 3.X Kernel yet
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
If we flash your twrp will it remove cwm or add another entry? I've never been able to have two recoveries working. I would much rather not have to use the power button and what not all the time in cwm but want to make sure I'm covered if something goes wrong. Thanks
Sent from my TouchPad using Tapatalk
Due to the limit of the boot directory it will remove all recoveries before installing this one.
Sent from my SCH-I545 using xda app-developers app
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
SteveoSupremo said:
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
Click to expand...
Click to collapse
So I replaced the ulimage in the boot directory and was able to install the 1/10/14 rom. So I guess I needed to search and just try a little more.
anyway -- I think it's a little slower than the first 4.4 version.... Maybe I need to reboot.... thoughts?
steve
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
I am curious. Have you tried turning the 4g off. Like airplane mode then just turning wifi back on? Was thinking of getting one of these models to tinker with.
Moody66 said:
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Click to expand...
Click to collapse
I think it was because of sync.... it's running smooth now. after I loaded a different set of GAPPS.
Now I have to figure out the camera apk. it would help if I RTFM.... Thanks Flintman for the awesome update!
Which version of gapps is recommended for 01-10-14 version?
New Test build up which fixes vibration
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
Do you think you can get me some dmesg and logcats??
Q&A for [PATCHER][APP] Dual boot any ROM on all Galaxy S4 variants!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Support for Galaxy S4 Mini GT-I9195
Hi, I tried this on a GT-I9195 using the "Galaxy S4" preset... Both ROMs seem to be installed, but once I install the second ROM, there doesn't seem to be any way to boot back into the first ROM.
I'd love for this to work on my device (serranoltexx). Could I help add support for this device in some way?
Thanks
utjunkie said:
Hi, I tried this on a GT-I9195 using the "Galaxy S4" preset... Both ROMs seem to be installed, but once I install the second ROM, there doesn't seem to be any way to boot back into the first ROM.
I'd love for this to work on my device (serranoltexx). Could I help add support for this device in some way?
Thanks
Click to expand...
Click to collapse
I started to wonder how did you install them in the first place???
qtwrk said:
I started to wonder how did you install them in the first place???
Click to expand...
Click to collapse
There were no errors and both ROMs are physically taking up the space; just it boots into the second ROM no matter what I do. It sounds like it's pretty close, can I help make this work?
Dual Boot with MIUI 4.9.26
Hello,
i tried to install the MIUI v5 4.9.26 Multilang but I got the error in the picture attached to this post.
Could you help me to install It? I have Omega ROM for first space and for the second I would install MIUI. I've already patched the ROM with the app for Android on the Omega and the tool create a dual.zip of the original MIUI ROM. I tried to flash it from recovery (TWRP 2.8.0.1 with Aroma MOD)
Thanks,
Whity
utjunkie said:
There were no errors and both ROMs are physically taking up the space; just it boots into the second ROM no matter what I do. It sounds like it's pretty close, can I help make this work?
Click to expand...
Click to collapse
i assume you followed instruction precisely ?
tried both app switcher and zip file switcher ?
Cam someone send me the link to the snapshots?
Sent from my GT-I9505 using Tapatalk 2
Alucard 1.4oc kernel issues
Hey, i am trying to flash Alucard 1.4oc over SlimKat on my Dual partition.. The patched script seems to install fine, but my boot just stops at the Samsung logo, vibrates twice and restarts... I can see that they made some changes to their updater_script, but I have not figured out if this is the source of my problems,or if it is not related to my multi-boot at all..
So, i just wanted to know if anyone has patched 1.4oc on anything other than Primary with success.
App Sharing
twcobra said:
+1
Click to expand...
Click to collapse
sronweb said:
As I understood from previous posts there is some work in progress but nothing yet released. Currently you can share only apps (which is a lot for me...)
Click to expand...
Click to collapse
Well, I was trying to reply to the question on app sharing. I have used both the full share and the individual. I stopped the full share because of the differences between Gapps with the different ROMS. However, the full share seems like a better bet because it is a straight swap of partitions. The individual app sharing has been working, but as it has been noted, data is not part of that... Also, i find the use of hard links challenging when i am trying to look at my filesystem and figure out what is where. Not to mention that it doesn't really let you manage all the apps you care about for all the ROMS in one place. I have needed to go to every ROM if i want to uninstall a shared app and really have it go away.
that said, i don't really want to go down the path of partitioning my external sd card and using something like Link2SD. I am going to wait and see what our patch master produces for his latest updates that try to handle sharing of data, as well.
Response to Primary Rom update question
1) From recovery, flash the DualBootUtilities
2) Select Primary
3) Do a full wipe
4) Exit to recovery
5) From recovery, install your new primary ROM as usual
The big point noted by the OP is to avoid using recovery wipe utilities because they may wipe parts/all of secondary ROMS (those in Dual and MultiSlots)
---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------
So, I can get these kernels to boot up fine from the primary ROM which is current some recent nightly of CM11
However, when i flash over my dual (SlimKat 8.10) or multi-slot-1 (DirtyUnicorns v8.2) i can't get past the initial Samsung logo. The phone vibrates once .... twice .... then reboots.
EDIT: I should note that i have 2 other kernels that are booting fine for my secondary ROM
Can someone confirm if they are using either of these Alucard kernels succesfully on something other than the PRimary ROM.
thanks
FuzzyPete said:
1) From recovery, flash the DualBootUtilities
2) Select Primary
3) Do a full wipe
4) Exit to recovery
5) From recovery, install your new primary ROM as usual
The big point noted by the OP is to avoid using recovery wipe utilities because they may wipe parts/all of secondary ROMS (those in Dual and MultiSlots)
---------- Post added at 09:58 PM ---------- Previous post was at 09:40 PM ----------
So, I can get these kernels to boot up fine from the primary ROM which is current some recent nightly of CM11
However, when i flash over my dual (SlimKat 8.10) or multi-slot-1 (DirtyUnicorns v8.2) i can't get past the initial Samsung logo. The phone vibrates once .... twice .... then reboots.
EDIT: I should note that i have 2 other kernels that are booting fine for my secondary ROM
Can someone confirm if they are using either of these Alucard kernels succesfully on something other than the PRimary ROM.
thanks
Click to expand...
Click to collapse
Ok, got my kernel patched and working. As it stands right now, it looks like the current releases of the Alucard AOSP kernel (1.4oc) do not patch correctly. I confirmed this for 1.4h and 1.4oc. It took a lot of painful sleuthing, but i finally determined that the Alucard kernel for AOSP gets a patch for the init binary. I could not tell from the commits why this was needed originally, but it appears that Alucard changed something on his end, or the ROMS have changed something else on their end or whatever.. Regardless, the init_kk binary is now incompatible with 1.4 AOSP kernel.. I didn't have a dev environment handy to just change the config and rebuild the DualPatcher app, so i did the following to confirm:
1) Ran the DualPatcher app for the 1.4oc kernel
2) Started recovery, and flashed the patched kernel
3) went to the shell, unpacked the ramdisk and replaced the patched init with the original from the Alucard kernel ramdisk
4) repacked the boot.img, copied it to MultiKernels
5) rebooted
At this point, my ROM booted fine.
9.0 Apk crashing
I also have the same problem. Tried to patch several different ROM for S5 but the app crashes at 0%. Using the 9.0 app
App crashes 9.0
I have the same problem. 9.0 app crashes at 0% when trying patch S5 dual boot ROM. Changed to standard patcher option and tried various ASOP ROMs.
Tried to patch 5.0 PA GAPPs with latest dbug apps failed. Patched CM12 is running ok.
I have a problem updating my ramdisk on the secondary rom(slimkat 4.4.4), can you help me?
I have a problem failed to patch kennel..
Both on v9 debug and v8
I am on ozcan rom v6.2
I have also tried on CM12 but does not work please help
ouwesh said:
I have a problem failed to patch kennel..
Both on v9 debug and v8
I am on ozcan rom v6.2
I have also tried on CM12 but does not work please help
Click to expand...
Click to collapse
Use the 17mb version on alpha 9.0
Dualboot TW Update
Hi guys,
I'm using the Dualbootoption developed inhere. As primary I'm using TW, as secondary DirtyUnicorns. Now the thing: I could make a Update of Touchwiz by Kies. I now, Root Rights will be removed and the Bootloader will be closed. So after the update I have to unlock the Boodloader and to root the Phone again to use the Dualboot Option or only to unlock the bootloader.
Just a few Information please
Best Regards,
Aeneas
AeneasG said:
Hi guys,
I'm using the Dualbootoption developed inhere. As primary I'm using TW, as secondary DirtyUnicorns. Now the thing: I could make a Update of Touchwiz by Kies. I now, Root Rights will be removed and the Bootloader will be closed. So after the update I have to unlock the Boodloader and to root the Phone again to use the Dualboot Option or only to unlock the bootloader.
Just a few Information please
Best Regards,
Aeneas
Click to expand...
Click to collapse
I think you must be rooted to set the kernel for your primary rom, and also have an unlocked bootloader to have custom recovery so you can flash dualboot patched roms
jigsawcrank said:
I think you must be rooted to set the kernel for your primary rom, and also have an unlocked bootloader to have custom recovery so you can flash dualboot patched roms
Click to expand...
Click to collapse
Yeah that's clear. But I have the dualboot option yet. To change after the update its enough only to root the smartphone or also to unlock the Bootloader?
Regards,
Aeneas
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