I'm currently running my S3 with the german XXBLH3 Firmware and rooted with CF-Root.
Now I want to apply this mod to expand my memory: http://forum.xda-developers.com/showthread.php?t=1772234
The problem is that my Kernel doesn't support init.d, so the mod doesn't work at all.
Is there a way to get init.d support with stock Kernel? I don't really want to install a custom Kernel and rather keep the original one.
I found this http://forum.xda-developers.com/showthread.php?t=1710980 but it's apparently only for HTC one X and one S.
Can anyone confirm that it works on the S3 ?
otherwise, is there a insecure stock Kernel with init.d support that comes close to the one in XXBLH3 ?
And if I install a custom Kernel with autoroot (Siyah f.e.) will CF-Root interrupt it?
2 ways to do it..
1. Flash a already hacked stock kernel
2. Pull out your kernel and hack it to include init.d support..
sent from here, there, somewhere!!
Okay the first method sounds easier. But where do I find one?
I'm currently using this with stock kernel flash through recovery http://forum.xda-developers.com/showthread.php?t=1710980
Sent from my GT-I9300 using Tapatalk 2
nex86 said:
Okay the first method sounds easier. But where do I find one?
Click to expand...
Click to collapse
You have a kernel thread in the stickies..if you don't find the one you want..post your kernel here..i will add init.d support to it :good:
I have a noob question regarding flashing a custom ROM with the HOX+
1) Do I always have to flash a kernel when flashing a rom? If not or if so what are the benefits of doing this.
Thanks all. I look forward to being able to help other users as I lean more.
ifixrjs said:
I have a noob question regarding flashing a custom ROM with the HOX+
1) Do I always have to flash a kernel when flashing a rom? If not or if so what are the benefits of doing this.
Thanks all. I look forward to being able to help other users as I lean more.
Click to expand...
Click to collapse
from my experience with flashing a few ROMs, the kernel, usually but not always, included in the ROM.
some ROM like AOSP/AOKP for our device don't include the kernel.
I'm a noob myself so dont take my words for it :laugh:
ifixrjs said:
I have a noob question regarding flashing a custom ROM with the HOX+
1) Do I always have to flash a kernel when flashing a rom? If not or if so what are the benefits of doing this.
Thanks all. I look forward to being able to help other users as I lean more.
Click to expand...
Click to collapse
You don't need to flash kernel every time you flash custom ROM as long as your kernel is compatible with the ROM. For example: if you already flash nik3r's elite kernel, you can switch to every sense ROM without flash kernel again. But if you want to flash AOKP/AOSP/CM ROMs, you need to flash spesific kernel, which is maxwen's blade kernel.
Thanks perfect explination
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
FredC94 said:
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
Click to expand...
Click to collapse
Necessary? No. I have switched kernels without using the script for the n10. (It is around somewhere on here, in the Apps section I think) But it does FEEL better when you do.
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
But if its the same kernel (updated) then flash without wiping anything because they will use the same ram disk (if they use one anyway).
iKarido said:
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
Click to expand...
Click to collapse
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
---------- Post added at 07:56 AM ---------- Previous post was at 07:44 AM ----------
Memp2Atl85 said:
Do I simply flash the zip file in clockwork mod or what? Currently using Franco and want to give Trinity a try
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Straight from the Trinity Ten Thread.
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had.
Click to expand...
Click to collapse
I know... Thats what I had just said.
iKarido said:
So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Click to expand...
Click to collapse
In my experience bootloop problems from kernel incompatibility with flashing over each other is pretty rare. I actually used to use a combo on Franco's ramdisk with the glados kernel on my phone and it worked perfectly fine. Even Morfic (the maker of Trinity kernel) said you can flash his kernel on top of Franco's and it will give you a sort of hybrid of them both. See here:
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
The governors and such arent part of the ramdisk, thats why. It would be nice to be able to load up the specific governors you want in any kernel, but sadly thats not possible. Those are part of the actual kernel itself and the ramdisk stuff is usually performance tweaks and mods to the system.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
FredC94 said:
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
Click to expand...
Click to collapse
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
iKarido said:
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
Click to expand...
Click to collapse
I am not worried. I have never bricked because I know what I am doing. The lucky part was sarcasm.
EniGmA1987 said:
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
Click to expand...
Click to collapse
That's clear, thanks a lot :good:
Another thing I just thought of is you can make a Nandroid backup of just the boot image as soon as you flash a ROM, give it a name of whatever ROM you are on "-kernel" and then you can restore that boot image whenever you want to restore back to your stock kernel + ramdisk. Alternatively, you can save a backup of your kernel in Trickster MOD and restore it that way at a later point. But both of these methods first require that you still be running your stock kernel and ramdisk that came with the ROM you are on. If you already flashed something else, you will have to re-flash the ROM again to get back to the stock files first
You could just grab the kernel from the rom and throw it into a flashable zip if you don't have a backup, instead of flashing the entire ROM again.
While on my old Sensation, i often flashed diffrend roms, but never a Kernel that was not includet in the rom.
From what i have read in this forum, youd could increase the batterie time, if a custom kernel is flashed.
The tutorials for flashing a kernel are well writen, so i don't see a problem here. And yes, i am aware, that i nee to unlook the bootloader to flash a custom kernel.
My question is, how to chose a kernel? For what information do i have to look?
And for understanding. Do i have to flash another rom to get a custom kernel running, or could i stay on the stock rom and try the kernel itself?
Does a custom Kernel mean, i loose some of the functions that are in the stock kernel /rom or do have all kernel the"basic" functions of the stock kernel and just have addional functions and optimization?
Thanks for your time and help.
eismaus said:
While on my old Sensation, i often flashed diffrend roms, but never a Kernel that was not includet in the rom.
From what i have read in this forum, youd could increase the batterie time, if a custom kernel is flashed.
The tutorials for flashing a kernel are well writen, so i don't see a problem here. And yes, i am aware, that i nee to unlook the bootloader to flash a custom kernel.
My question is, how to chose a kernel? For what information do i have to look?
And for understanding. Do i have to flash another rom to get a custom kernel running, or could i stay on the stock rom and try the kernel itself?
Does a custom Kernel mean, i loose some of the functions that are in the stock kernel /rom or do have all kernel the"basic" functions of the stock kernel and just have addional functions and optimization?
Thanks for your time and help.
Click to expand...
Click to collapse
You don't need to flash custom kernel to increase battery life.
All you need to flash a custom kernel is unlocked bootloadr. Be sure to save DRM keys if bravia engine is important to you.
Then look for a custom kernel for stock roms, and custom stock tom too if you wish, or you can choose a non-stock based rom abd kernel.
hi everyone.
well, i've searched a lot about kernels in different threads, but didn't find any detailed and comprehensive information about kernels.
i rooted my SGSII with Odin through a guide which installed Siyah-s2-v6.0b4.tar kernel and CWM based recovery on my phone.
i flashed RootBox-JB-i9100-V4.2 ROM and now have 3.0.64-CM-g32f12dd kernel.
Before i flashed a custom ROM i got stweaks working, and after i flashed rootbox i recieve a message:"no kernel support" on stweaks.
This is leading to my first question- does my kernel change when i use different ROMs?
now i want to try and change my kernel to one who is supported by stweaks and has touch CWM and works with RootBox, but i'm not sure how to flash kernels.
This is leading to my second question- can anyone describe the whole procedure of how to change kernels on SGSII?
thanks for your attention.
There's nothing to describe. Custom kernels are flashed in CWRecovery mostly (some have Odin flashable versions as well). Always follow the exact flashing instructions for the kernel in question which are always on the first page of the thread devoted to the kernel in whichever development section, and are always very clear/simple to follow.
Only some kernels like Siyah or DorimanX support STweaks.Look up here on S2 forums in the Android Development section for kernelsThere are some others that have STweaks support.Also,.don't flash kernels made for Sammy ROMs.If you wanna flash DorimanX, then flash 9.39, not 8.39.
ido.n said:
This is leading to my first question- does my kernel change when i use different ROMs?
Click to expand...
Click to collapse
Yes, if the ROM comes bundled with its own kernel(s). :good:
ido.n said:
hi everyone.
.....
This is leading to my first question- does my kernel change when i use different ROMs?
...
thanks for your attention.
Click to expand...
Click to collapse
Yes.. The ROM ZIP usually contains Rom+kernel+modem combination
ido.n said:
hi everyone.
.....
This is leading to my second question- can anyone describe the whole procedure of how to change kernels on SGSII?
thanks for your attention.
Click to expand...
Click to collapse
1.Just go the kernel thread you want to use.(Mind that you cant use siyah with Rootbox). Search for a kernel which supports 4.2.2 (eg. Dorimanx 9.x) and download the CWM Flashable zip in the thread.
2.Download Hawker Paul`s Kernel Cleaning Script
3.Flash Hawker Paul`s Kernel Cleaning Script first trhu CWM
4.Then Flash the Kernel ZIP
Hit Thanks if I`ve helped you
thanks everyone! you're great!
absolutely clear now.