I was just wondering if you flash a new ROM is it necessary to flash a kernel right after? I just recently flashed the ICS port on my Nexus S and I was wondering if I have to flash my kernel again. Thanks
No, you do not have to flash a kernel after flashing a rom. Plus, using that rom (which is in its very early stages), it's not recommended that you flash anything on it.
Slaii1030 said:
I was just wondering if you flash a new ROM is it necessary to flash a kernel right after? I just recently flashed the ICS port on my Nexus S and I was wondering if I have to flash my kernel again. Thanks
Click to expand...
Click to collapse
every rom has its own kernel do not flash another one unless u got problems with stability/battery.
[email protected] said:
do not flash another one unless u got problems with stability/battery.
Click to expand...
Click to collapse
...or you want better performance and many new features.
Hello everyone,
STOCK+ Team ($omator & Grooby) are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROM by Samsung.
Why should i use this kernel?
Our kernels are uber-minimal modification of stock kernel used only for rooting (no custom recovery is installed). So the kernel it's like stock just rooted, and there is small chance (or any chance) that it will be detected as modified by service center at the first look
Please find latest of kernels listed below:
ROOTED! I9100XXLPH - ICS (4.0.3) - CL: 1104396 - B.Date: 16-02-2012 -[/b] Touch CWM Recovery Download HERE!
ROOTED! I9100XXLPB - ICS (4.0.3) - CL: 99600 - B.Date: 29-01-2012 - Samsung Recovery Download HERE! or Touch CWM Recovery Download HERE!
Instructions:
1. Flash zImage.tar of choosen kernel using odin (you will find it in package)
2. enable usb debugging in settings->applications
3. while still connected and odin/kies is turned off, run RUNME.BAT (also in package)
4. Install latest Superuser.apk from market!
5. Profit!
If you like our modifications, support us with even a little donation for a beer -> Click to donate!
Don't forget to follow our service at Twitter (@SamsungUpdates) or (soon) Samsung-Updates.com
Best regards for all XDA-DEVELOPERS members! we love ya!
* reserved *
* reserved again *
Looking good mate. Good luck
Sent from my GT-I9100 using XDA App
Touch recovery added to stock kernels, you can choose now if you want a kernel which is only ROOTED with all rest stock by samsung or, base samsung kernel with touch recovery included and rooted
Enjoy!
Thank you..
Is odin version lony ?
goodluck! trying this maybe in the near future
tonz22 said:
Thank you..
Is odin version lony ?
Click to expand...
Click to collapse
Yup, its odin version
Looking forward to see more stock kernel from you. Good luck
Can we get a CWM flashable zip of the touch based version?
Sorry for my stupid question but is this only for ICS? I'm little confused, or can we use this for stock to?
Sent from my Samsung Galaxy SII using Tapatalk
Its for ICS as stated in first post if you want to request any other kernel let me know in this thread.
Also, for now we provide only ODIN images, which is most suitable for people with or without CWM already installed.
Thanks!
(ODIN is in the package.)
I havent used odin in a whille. Could someone please refresh my memory, which do I flash this under, pda, phone or csc? I obviously know this isn't bootloader
Grooby said:
Its for ICS as stated in first post if you want to request any other kernel let me know in this thread.
Also, for now we provide only ODIN images, which is most suitable for people with or without CWM already installed.
Thanks!
(ODIN is in the package.)
Click to expand...
Click to collapse
Like i thought, I got confused.by the stock if you could do a kernel for stock ROM with touch recovery it would be awesome.
You just got Samsunged from Tapatalk
Do we need to execute runme.bat if the phone is already rooted and has su installed?
First of all its a stock rom (dont mix it with team name which is STOCKPLUS) + the touch CWM added (su will install automatically) so just flash with ODIN as PDA and enjoy samsung rom with good recovery and root
secondly, if you got a su installed then you dont need to run runme.bat, just install superuser from market or from package shipped with kernel (adb install Superuser.apk)
Enjoy!
Nagarebozhi said:
Like i thought, I got confused.by the stock if you could do a kernel for stock ROM with touch recovery it would be awesome.
You just got Samsunged from Tapatalk
Click to expand...
Click to collapse
It is stock kernel with touch recovery to get stock rom with touch recovery just install stock ROM (LPB) and then flash this kernel simple and clean
MrBadgerMilk said:
I havent used odin in a whille. Could someone please refresh my memory, which do I flash this under, pda, phone or csc? I obviously know this isn't bootloader
Click to expand...
Click to collapse
put it as PDA
Grooby said:
put it as PDA
Click to expand...
Click to collapse
It will increase custom binary count huh?
Sent from my GT-I9100 using XDA App
Grooby said:
It is stock kernel with touch recovery to get stock rom with touch recovery just install stock ROM (LPB) and then flash this kernel simple and clean
Click to expand...
Click to collapse
But you said it was for ics?, I want a kernel for 2.3.5/2.3.6
But
Grooby said:
Its for ICS as stated in first post if you want to request any other kernel let me know in this thread.
Also, for now we provide only ODIN images, which is most suitable for people with or without CWM already installed.
Thanks!
(ODIN is in the package.)
Click to expand...
Click to collapse
"You just got Samsunged from Tapatalk"
Hi, I'm unsure of how to tackle this.
I've flashed my way from stock rom and lost the backup somehow. Therefore I intend to download the original firmware package from Sammobile or Kies. The thing is; I want to continue using my Custom firmware as primary ROM and have the original one as secondary ROM. This is hopefully possible through Siyah Kernel and tools. Although, I'm not sure if flashing the original ROM will tamper with my kernel. Is it safe to do it this way? Is it even possible? And what will happen if i get an OTA update after a successful flash of the original ROM?
It's important for me to dual boot, but the custom ROM I have doesn't have great image processing from the camera, so... I want the original as backup.
Thanks in advance.
erfah said:
Hi, I'm unsure of how to tackle this.
I've flashed my way from stock rom and lost the backup somehow. Therefore I intend to download the original firmware package from Sammobile or Kies. The thing is; I want to continue using my Custom firmware as primary ROM and have the original one as secondary ROM. This is hopefully possible through Siyah Kernel and tools. Although, I'm not sure if flashing the original ROM will tamper with my kernel. Is it safe to do it this way? Is it even possible? And what will happen if i get an OTA update after a successful flash of the original ROM?
It's important for me to dual boot, but the custom ROM I have doesn't have great image processing from the camera, so... I want the original as backup.
Thanks in advance.
Click to expand...
Click to collapse
Swap your own rom from secondrom utility's.
Than install the stock rom via Odin
And swap back your own custom rom to be the first rom.
Because you use a custom recovery you don't get any ota updates.
After flashing Install siyah Kernel back.
Verzonden door mijn GT-I9300 met xda premium
I have a GS2 I9100XWLSW, suffering the EMMC brick bug. Still with stock kernel and recovery. Rooted with Framaroot.
First of all I'd want to flash a recovery, and a safe kernel - to avoid any possibile brick bug.
Later on I plan to flash Cyanogen or Omnirom, once a Lollipop stable versions is out.
Looking around I've found many ways to do this, but I'm unsure which one is safes (and possibly easier too):
- Installing Philz through Odin? Surely the kernel is safe, but CWM is and old version, not supporting KitKat ROM, right? Would I then need to flash an updated CWM + Kernel once I update to Lollipop? How?
- Using Clockwork mod install app to install a CWM? Can I install last CWM and still run on JB? But what about the unsafe, still not patched, stock kernel? Would still need to later update with a new Kernel for Lollipop? How?
- Others?
In particular, there's something concerning my GS2 that I didn't fully understand.. seems like differently from other phones, CWM needs to be installed together with a specific Kernel to work. Is this something true only for Philz's version, or is it so for CWM itself?
Malhavoc Blackdrake said:
I have a GS2 I9100XWLSW, suffering the EMMC brick bug. Still with stock kernel and recovery. Rooted with Framaroot.
First of all I'd want to flash a recovery, and a safe kernel - to avoid any possibile brick bug.
Later on I plan to flash Cyanogen or Omnirom, once a Lollipop stable versions is out.
Looking around I've found many ways to do this, but I'm unsure which one is safes (and possibly easier too):
- Installing Philz through Odin? Surely the kernel is safe, but CWM is and old version, not supporting KitKat ROM, right? Would I then need to flash an updated CWM + Kernel once I update to Lollipop? How?
- Using Clockwork mod install app to install a CWM? Can I install last CWM and still run on JB? But what about the unsafe, still not patched, stock kernel? Would still need to later update with a new Kernel for Lollipop? How?
- Others?
In particular, there's something concerning my GS2 that I didn't fully understand.. seems like differently from other phones, CWM needs to be installed together with a specific Kernel to work. Is this something true only for Philz's version, or is it so for CWM itself?
Click to expand...
Click to collapse
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
gsstudios said:
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
Click to expand...
Click to collapse
Thank you! Ok, let's see if I got everything right:
- First I need to flash Apolo, but I can't find the 4.14 version. Do I still use Odin? Instructions are unclear. The official thread seems this: http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756/post41742325
- By flashing Apolo 4.14 I should get a new kernel (EMMC safe) and TWRP (which version?)
- With the above, I can still run my stock JB 4.1.2, right?
Then, once I want to flash a Lollipo ROM:
- Do I need to update TWRP? Does this break my ability to run my current JB 4.1.2 ?
- Flashing the Lollipop ROM will overwrite the Apolo Kernel 4.14 with a suitable Lollipop kernel, right? Or am I forced to also flash a Lollipop kernel manually (either Apolo or anoter)?
Thank you in advance!
Malhavoc Blackdrake said:
Thank you! Ok, let's see if I got everything right:
- First I need to flash Apolo, but I can't find the 4.14 version. Do I still use Odin? Instructions are unclear. The official thread seems this: http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756/post41742325
- By flashing Apolo 4.14 I should get a new kernel (EMMC safe) and TWRP (which version?)
- With the above, I can still run my stock JB 4.1.2, right?
Then, once I want to flash a Lollipo ROM:
- Do I need to update TWRP? Does this break my ability to run my current JB 4.1.2 ?
- Flashing the Lollipop ROM will overwrite the Apolo Kernel 4.14 with a suitable Lollipop kernel, right? Or am I forced to also flash a Lollipop kernel manually (either Apolo or anoter)?
Thank you in advance!
Click to expand...
Click to collapse
What I said before about apolo requires the usage of CWM. If you can, flash philz kernel (through odin)first then you can flash apolo 4.14 (TWRP) using cwm. All kernels for the s2 are safe from the emmc brickbug (just make sure you read the first post of the kernel threads). TWRP version should be 2.7.0.0, but it should work fine with all zip files.
When you flash a lollipop rom, you most likely will not have to update TWRP (unlikely as the source code for lollipop isn't going to change). You can still flash back stock JB from a backup with no problems. Yes, flashing lollipop will replace apolo with a compatible kernel.
gsstudios said:
Sincw you are on stock jelly bean rom, use apolo kernel 4.14 as it uses TWRP which supports most zips and doesnt have to be updated that often. Lollipop roms only require cwm versions 6.0.4.8+ or TWRP 2.7.1.0+. Usually i don't recommend using cwm manager to install cwm as the app installs an old version of cwm anyway and requires people to pay if they want the latest version.
If your cwm is out of date, you will need to update the kernel (not just the recovery).
Installing a newer cwm will not modify the kernel to make it unsafe.
Click to expand...
Click to collapse
gsstudios said:
What I said before about apolo requires the usage of CWM. If you can, flash philz kernel (through odin)first then you can flash apolo 4.14 (TWRP) using cwm. All kernels for the s2 are safe from the emmc brickbug (just make sure you read the first post of the kernel threads). TWRP version should be 2.7.0.0, but it should work fine with all zip files.
When you flash a lollipop rom, you most likely will not have to update TWRP (unlikely as the source code for lollipop isn't going to change). You can still flash back stock JB from a backup with no problems. Yes, flashing lollipop will replace apolo with a compatible kernel.
Click to expand...
Click to collapse
All right, so, to recap, is this right?
- Flash Philz (of course the version for my kernel and JB) with Odin. This will also install CWM (an old version, not supporting KitKat and Lollipop)
- With the above, I can do a nandroid backup, which also includes Philz's kernel. Does it also include the recovery itself?
- Flash Apolo 4.14 through CWM. This will change both the Philz Kernel and the CWM recovery with Apolo Kernel and TWRP. Jelly Bean will still run, right?
- From this TWRP, I can flash and run both the current JB and future Lollipop without changing recovery, right?
Malhavoc Blackdrake said:
All right, so, to recap, is this right?
- Flash Philz (of course the version for my kernel and JB) with Odin. This will also install CWM (an old version, not supporting KitKat and Lollipop)
- With the above, I can do a nandroid backup, which also includes Philz's kernel. Does it also include the recovery itself?
- Flash Apolo 4.14 through CWM. This will change both the Philz Kernel and the CWM recovery with Apolo Kernel and TWRP. Jelly Bean will still run, right?
- From this TWRP, I can flash and run both the current JB and future Lollipop without changing recovery, right?
Click to expand...
Click to collapse
You are 100% correct with all of your questions. Happy flashing!
gsstudios said:
You are 100% correct with all of your questions. Happy flashing!
Click to expand...
Click to collapse
Thank you very much! Also found the Apolo version you were talking about. BTW, the reason I have to pass through Philz to flash Apolo is just because that Apolo version is available in .zip format only, right? Because if there was a .tar, I could just flash the stock rom with Apolo through Odin, without going through Philz first, right?
Malhavoc Blackdrake said:
Thank you very much! Also found the Apolo version you were talking about. BTW, the reason I have to pass through Philz to flash Apolo is just because that Apolo version is available in .zip format only, right? Because if there was a .tar, I could just flash the stock rom with Apolo through Odin, without going through Philz first, right?
Click to expand...
Click to collapse
Wow, you sound like you have flashed custom roms before. You are correct again.
gsstudios said:
Wow, you sound like you have flashed custom roms before. You are correct again.
Click to expand...
Click to collapse
Never before, but being a software developer I get these things not too hardly. Also, I'm really reading a LOT of guides everywhere to avoid doing a mess! :laugh:
Thank you again for your help.
gsstudios said:
Wow, you sound like you have flashed custom roms before. You are correct again.
Click to expand...
Click to collapse
I finally did all of the above, and I can confirm that everything worked perfectly. I just skipped during the Apolo flashing the clean script suggested, and just did Clean Cache + Dalvik Cache.
Now I have TWRP and Apolo v4.15.
Noticed however that TWRP is v2.6.3 , while you said that I would probably need 2.7.1.0+ to later flash Omnirom or CM12
Is it okay anyway, or do I need to flash a new one? Can I risk breaking something if I try to flash a new TWRP? I mean: may I end up flashing a TWRP not supported with my kernel / JB and get bootloops or something bad?
Malhavoc Blackdrake said:
I finally did all of the above, and I can confirm that everything worked perfectly. I just skipped during the Apolo flashing the clean script suggested, and just did Clean Cache + Dalvik Cache.
Now I have TWRP and Apolo v4.15.
Noticed however that TWRP is v2.6.3 , while you said that I would probably need 2.7.1.0+ to later flash Omnirom or CM12
Is it okay anyway, or do I need to flash a new one? Can I risk breaking something if I try to flash a new TWRP? I mean: may I end up flashing a TWRP not supported with my kernel / JB and get bootloops or something bad?
Click to expand...
Click to collapse
You will need to flash a newer recovery. If you use philz recovery, you can install all lollipop roms and kikat roms without a problem
Link to download latest philz recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip
Flash it with TWRP. Cheers.
gsstudios said:
You will need to flash a newer recovery. If you use philz recovery, you can install all lollipop roms and kikat roms without a problem
Link to download latest philz recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip
Flash it with TWRP. Cheers.
Click to expand...
Click to collapse
That link is indeed philz's latest version for i9100 (also from size it seems with just the recover, and no kernel, right?), but does it still run on JB with Apolo kernel? On Philz's thread I read something about latest versions supporting only kitkat / lollipop. Does it mean I have to flash this Philz's update just before flashing Lollipop, or I can flash it already and running my JB + Apolo, without problems?
Also, I heard that Philz is no longer updating his recover (is it?), so if possible I would prefer to stick with TWRP.. if there is a TWRP version which suits my needs with my device, of course!
I see a lot of ROMS posted list kernels other than mine (NC2). Do I need to flash those kernels prior to flashing those roms or not?
Also, If I want to go back to a NC2 roms will I night to flash that kernel back?
I am confused, please lmk. Thanks!
panxpany said:
I see a lot of ROMS posted list kernels other than mine (NC2). Do I need to flash those kernels prior to flashing those roms or not?
Also, If I want to go back to a NC2 roms will I night to flash that kernel back?
I am confused, please lmk. Thanks!
Click to expand...
Click to collapse
No need to flash kernal.
But, If your developer of Rom said that custom Kernal is required then you should flash custom kernal....
For backing to stock rom you need SP TOOLS (Smart phone tool) & Scatter file.
Every custom Rom does have its own kernel included which works perfectly with it. You don't need to flash any kernel. Just if you want to change the kernel you can change it afterwards. If you want to go back to your rom you have had before, just backup your system folder with twrp for example recovery and then you can restore it back. Hope that helped.