Hi I would like to ask whether rooting the phone is the same as unlocking bootloader. Thanks!
No, it's not.
Rooting allows you to view and edit system files.
Unlocking the bootloader allows you to install custom (non-official) kernels.
So rooting my phone and unlocking the bootloader is 2 different issue?
Or does rooting my phone actually unlocks my bootloader as well?
Rooting does not unlock bootloader.
Unlocking bootloader can help root your phone (installing a pre-rooted kernel, for example).
Is it then possible to install a custom firmware without unlocking the bootloader or will there be problems if I install a custom firmware without unlocking the bootloader.
These two custom ROMs are the only ones that can be installed without unlocking the bootloader.
http://forum.xda-developers.com/showthread.php?t=1705255
http://forum.xda-developers.com/showthread.php?t=1578109
OK THANKS! SHALL GO CHECK IT OUT And can I ask, does the phone by itself already have a kernel? If it has, what is the use of installing another one?
Stock ROMs have their stock kernels.
Custom kernels can add some features, such as (for example) the chance to overclock the CPU. Almost every custom ROM needs a custom kernel to work properly.
Feanor88 said:
Stock ROMs have their stock kernels.
Custom kernels can add some features, such as (for example) the chance to overclock the CPU. Almost every custom ROM needs a custom kernel to work properly.
Click to expand...
Click to collapse
Wrong. Custom ROMs do not need custom kernel to *function or work properly*.
The custom ROMs are installed at the Read Only Memory of your phone.
For that, you need to use an installer which has to be somewhere outside the Read Only Memory. Only such location on your phone is the kernel. So a custom kernel does nothing but adds an installer outside the Read Only Memory (that is the CWM Recovery).
Now to intall a kernel, you need an installer outside of your Read Only Memory as well as the kernel. That's the PC, and the installer is Flashtool. So, flashtool is used to install custom kernels on your phone.
Note: The two ROMs which can be installed on locked bootloaders are exceptions to this rule.
Thanks,
Rick
Sent from my SK17i using XDA
If it were like you said, any custom kernel could work with any custom ROM, as long as it has a Recovery to flash the ROM. There are different custom kernels because there are different ROMs, and each custom ROM works only with one or more custom kernels, but not with everyone. If you were right, one single kernel with recovery would be usable for every custom ROM.
Feanor88 said:
If it were like you said, any custom kernel could work with any custom ROM, as long as it has a Recovery to flash the ROM. There are different custom kernels because there are different ROMs, and each custom ROM works only with one or more custom kernels, but not with everyone. If you were right, one single kernel with recovery would be usable for every custom ROM.
Click to expand...
Click to collapse
Yea. It would be. Infact it is.
However, ROMs like CM9, which are NOT based on the stock ROM will not be able to work on the stock kernel. It will require a kernel which has been designed specifically for CM9. On the other hand, we had seen MiniCMSandwich, which looks like CM, but is based on stock ROM. This will work on any kernel that has a custom recovery. MESA, Rage, X, Stock Exteneded and so on...
So, to put it in other words, suppose you plan to flash an HTC Phone ROM as it came in the HTC device on your Xperia Device. You plan to just change the drivers. You will need a kernel which is designed for the HTC ROM.
But, if you, on the other hand, start with the Xperia ROM and change the aspects of this ROM into the HTC ROM's, you can make the ROM work on any of MESA, X, Rage or extended.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Yea. It would be. Infact it is.
However, ROMs like CM9, which are NOT based on the stock ROM will not be able to work on the stock kernel. It will require a kernel which has been designed specifically for CM9. On the other hand, we had seen MiniCMSandwich, which looks like CM, but is based on stock ROM. This will work on any kernel that has a custom recovery. MESA, Rage, X, Stock Exteneded and so on...
Click to expand...
Click to collapse
Stock extended, yeah. Try to run MiniCMSandwich on Gingerbread stock extended kernel. Will it work? Of course not. All the kernels you named are based on stock ICS kernel, so it's simple to run ICS based ROMs on them. This doesn't mean that every kernel with recovery can make them work
Feanor88 said:
Stock extended, yeah. Try to run MiniCMSandwich on Gingerbread stock extended kernel. Will it work? Of course not. All the kernels you named are based on stock ICS kernel, so it's simple to run ICS based ROMs on them. This doesn't mean that every kernel with recovery can make them work
Click to expand...
Click to collapse
Stock GB is to Stock ICS is same as Stock Xperia ICS is to Stock HTC ICS. They are different ROMs. Completely.
The ROMs have instructions according to which it behaves with the kernel. These instructions are all same for kernels that are based on stock ICS. So if you want to try any ROM that is based on stock ICS and such kernel will do.
But CM, GB, HTC ROMs and so on, are completely different.
Say you want to port an HTC ROM to Xperia ICS. You can do the following (I am taking example of the bootanimation file)
1. Simply change the bootanimation.zip file at /system/media of the stock ICS ROM.
So your ROM is based on the stock ROM itself. You just change the files, not the way the files are accessed. You do not even change the way the kernel is accessed. So any kernel based on stock ICS *with recovery* will do.
2. Change the whole Read Only Memory Partition.
This makes all the files replaced, the way HTC has made the ROM. This time you will need a kernel *again with recovery*, built to be accessed by the very specific ROM.
Thanks,
Rick
Sent from my SK17i using XDA
Related
I've been doing this whole "reading" thing about flashing and all that, but some confusion is still there.
I have rooted my newly got SGS2 (i9100, UK).
Now what ? I'm looking at Darky's rom, but there are two files to flash separately: kernel (darkcore1.7) and ROM itself.
1. I was just wondering what is kernel in this situation ? Can i keep my current kernel, which was flashed by superoneclick(2.1.1) or do i absolutely need to flash darkcore ?
2. Same question applies to any other rom out there - can i use different kernel to the rom i may want to flash ? A lot of them come in sets (rom+kernel)
3. Another question - if i mess up kernel flash somehow, does that kill "download mode" of the phone (voldn+pwr)?
I have SGS1 flashed just another day, due to it being "expendable" now that i have SGS2, so jumped in and flashed it following instructions, but without solid understanding. Either stuff gets too complicated or i'm getting too old for this **** (I do have a background of messing with PCs, videogame consoles (ps1 era to ps3/360), winmo6 phones, gadgetry in general...engineer at heart )
You can use any kernel with any ROM. And no I don't think your Download Mode will be gone if you mess up a Kernel.
Kernel don't come in sets. You can choose your favorite there. See Dev section for more details.
Regards.
Correction: SuperCore, not darkcore...
Can i use cwm app (v2.0)to flash any kernels ? Or does it have to be odin ?
sliex said:
Correction: SuperCore, not darkcore...
Can i use cwm app (v2.0)to flash any kernels ? Or does it have to be odin ?
Click to expand...
Click to collapse
Rom>>That depends upon the instructions as always in the rom you choose for a custom rom .
Kernel is flashed via Odin Via CWM app or via CWM recovery .
Kernel is the core of the system between hardware and operating .
jje
Ok, so saying that, What stock Kernel can I use for Cyanogenmod7 ROM?
I was using "XWKE7" previously.
The ZIP file that i downloaded actually replaced my kernel with its own.
I'm asking this as I wanna use Tegrak overclock which is only compatible with stock kernels.
Rjmcgauley said:
Ok, so saying that, What stock Kernel can I use for Cyanogenmod7 ROM?
I was using "XWKE7" previously.
The ZIP file that i downloaded actually replaced my kernel with its own.
I'm asking this as I wanna use Tegrak overclock which is only compatible with stock kernels.
Click to expand...
Click to collapse
Stock kernels will not work with cyanogenmod. There are no overclockable kernels available for it yet.
Sent from my GT-I9100M
So I had followed a guide (GalaxyS2Root.com i think the site was) for rooting my phone and successfully rooted my i777 device. Had no problems.
Upon researching this forum to start figuring out what else was possible with my phone, I found some information on what I had just installed and learned a few things and decided I wanted to install a custom ROM (but, I haven't gotten around to doing it yet)
So the package I had used to root my phone (which is using the AT&T-provided ICS rom) was "Siyah-v3.4.2-nomswap-I777.tar".
I noticed the "nomswap" in the name as well as the version.
I read a few peoples' posts asking about JB roms, and some replied that mic swap is required for all JB roms.
So, my questions:
1) I need to install an MSWAP kernel first before a JB rom? Or the other way around, rom first, then the MSWAP kernel?
2) If I install the MSWAP kernel but choose not to install a JB rom all the sudden, will my stock AT&T ICS rom continue to work fine?
3) Do I require the updated Siyah 4.3.3 kernel for the new JB roms?
Thanks.
The determining factor for whether or not you need mic swap is the ROM's base. Android version has nothing to do with it - some JB ROMs will require mic swap, others will not. Mic swap is for ROMs built on I9100 or AOSP base; without mic swap is for ROMs built on I777 base.
You should understand that every ROM is packaged with a working kernel, so there is no need to flash a different kernel on top of it. However, if you prefer a different kernel, you can always flash it after flashing the ROM.
chewyfood said:
So I had followed a guide (GalaxyS2Root.com i think the site was) for rooting my phone and successfully rooted my i777 device. Had no problems.
Upon researching this forum to start figuring out what else was possible with my phone, I found some information on what I had just installed and learned a few things and decided I wanted to install a custom ROM (but, I haven't gotten around to doing it yet)
So the package I had used to root my phone (which is using the AT&T-provided ICS rom) was "Siyah-v3.4.2-nomswap-I777.tar".
I noticed the "nomswap" in the name as well as the version.
I read a few peoples' posts asking about JB roms, and some replied that mic swap is required for all JB roms.
So, my questions:
1) I need to install an MSWAP kernel first before a JB rom? Or the other way around, rom first, then the MSWAP kernel?
2) If I install the MSWAP kernel but choose not to install a JB rom all the sudden, will my stock AT&T ICS rom continue to work fine?
3) Do I require the updated Siyah 4.3.3 kernel for the new JB roms?
Thanks.
Click to expand...
Click to collapse
You should have the most up to date kernel in general. All roms are packaged with kernels already otherwise it wouldn't run at all, so it overrides whatever is already there. And DO NOT USE ANYTHING FROM GALAXYS2ROOT. For the rest, you'll have to use Google as I've done my spoonfeeding for today.
Sent by from my Zanpakuto using Getsuga Tensho!
Also as a side note. Any of the leaks require u run the kernel the rom comes with . As in Siyah and Dream won't work with the leaks yet.
Thank you for all the information. Very useful.
On a side, I only learned of XDA and the AOKP ROM as a result of reading GalaxyS2Root.com.
So basically, with every release of a ROM, I can just flash it and be OK. I don't need to manually change the kernel beyond flashing the ROM itself...
If that is the case, what is the purpose of the kernel downloads (Siyah 4.3.3 or the sort)?
chewyfood said:
Thank you for all the information. Very useful.
On a side, I only learned of XDA and the AOKP ROM as a result of reading GalaxyS2Root.com.
So basically, with every release of a ROM, I can just flash it and be OK. I don't need to manually change the kernel beyond flashing the ROM itself...
If that is the case, what is the purpose of the kernel downloads (Siyah 4.3.3 or the sort)?
Click to expand...
Click to collapse
Because not all roms use Siyah as a kernel but it can be flashed separately.
Sent from Team Pirate! Using Tapatalk 2
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.
So I've tried a bunch of different ROMs (CleanROM, Alliance, Beans, CM, OMNI, "Stock", probably more), but I've never really understood kernels. It seems some custom ROMs have a kernel built in (or several to choose from via Aroma), while others do not. Right now I'm running AOKP (4.4.2) with the kernel from OMNI (3.0.64-OMNI-g5f47648), presumably because that was the previous ROM I flashed with a kernel. I'm not too concerned with customization, more with stability.
I've been having a few minor bugs and crashes and I'd like to try perhaps the stock kernel to see if that might help, but I have some questions:
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
2) Are there multiple versions of kernels that correspond with the Android version of the ROM?
3) What's the best/easiest way to flash a kernel, presumably through the custom recovery like a ROM?
4) Where can I find the stock kernel? I found this thread (http://forum.xda-developers.com/showthread.php?t=2610870) with the stock MJ9 kernel, but going back to my first two questions I'm not sure if it would work with my current ROM.
Thanks ahead of time for any insight anyone can provide.
michaellasalle said:
So I've tried a bunch of different ROMs (CleanROM, Alliance, Beans, CM, OMNI, "Stock", probably more), but I've never really understood kernels. It seems some custom ROMs have a kernel built in (or several to choose from via Aroma), while others do not. Right now I'm running AOKP (4.4.2) with the kernel from OMNI (3.0.64-OMNI-g5f47648), presumably because that was the previous ROM I flashed with a kernel. I'm not too concerned with customization, more with stability.
I've been having a few minor bugs and crashes and I'd like to try perhaps the stock kernel to see if that might help, but I have some questions:
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
2) Are there multiple versions of kernels that correspond with the Android version of the ROM?
3) What's the best/easiest way to flash a kernel, presumably through the custom recovery like a ROM?
4) Where can I find the stock kernel? I found this thread (http://forum.xda-developers.com/showthread.php?t=2610870) with the stock MJ9 kernel, but going back to my first two questions I'm not sure if it would work with my current ROM.
Thanks ahead of time for any insight anyone can provide.
Click to expand...
Click to collapse
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
Yes. TW and AOSP kernels are different.. The only one, that I believe, that can be used with both is Devil kernel for Dual Booting
2) Are there multiple versions of kernels that correspond with the Android version of the ROM?
Yes. Usually every version of android that gets updated.. the kernel does as well
3) What's the best/easiest way to flash a kernel, presumably through the custom recovery like a ROM?
Yes you can flash kernels through a custom recovery. Most of the time they are included with the Rom that you flash. A lot of the custom ones out have flashable zip for you to flash them through a recovery.
4) Where can I find the stock kernel? I found this thread (http://forum.xda-developers.com/showthread.php?t=2610870) with the stock MJ9 kernel, but going back to my first two questions I'm not sure if it would work with my current ROM.
No this will NOT work with a AOSP rom.. The kernel will be specific to that ROM and every other TW 4.3 ROM, but NOT AOSP
lacoursiere18 said:
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
Yes. TW and AOSP kernels are different.. The only one, that I believe, that can be used with both is Devil kernel for Dual Booting
Click to expand...
Click to collapse
Thanks for the explanations, that helps tremendously. I'm confused now, however, because several people on the AOKP thread (http://forum.xda-developers.com/showthread.php?t=2453566) claim to be on "stock kernel". Is there a stock kernel for AOSP that I'm missing?
michaellasalle said:
Thanks for the explanations, that helps tremendously. I'm confused now, however, because several people on the AOKP thread (http://forum.xda-developers.com/showthread.php?t=2453566) claim to be on "stock kernel". Is there a stock kernel for AOSP that I'm missing?
Click to expand...
Click to collapse
Yea the one that flashes with AOKP.. loll
lacoursiere18 said:
Yea the one that flashes with AOKP.. loll
Click to expand...
Click to collapse
Well that's what I thought, but why then would I be using an OMNI kernel (3.0.64-OMNI-g5f47648) when I have flashed the last three AOKP nightly ROMs that have come out? Or am I missing something here?
michaellasalle said:
Well that's what I thought, but why then would I be using an OMNI kernel (3.0.64-OMNI-g5f47648) when I have flashed the last three AOKP nightly ROMs that have come out? Or am I missing something here?
Click to expand...
Click to collapse
Maybe he uses that kernel.. AOSP kernels, I believe are pretty similar.. I may be wrong, I am by NO MEANS a kernel guru..I would open you zip of your ROM (AOKP) and take a peak.. if there is a boot.img than it flashes a kernel.. and if your says OMNI then thats the kernel the dev has used..
Stock
If I'm on the stock rom and want to go back to the original kernel can I just restore the boot img in recovery?
nealman said:
If I'm on the stock rom and want to go back to the original kernel can I just restore the boot img in recovery?
Click to expand...
Click to collapse
Should be able to if you back it up previously.. but make sure it is same rom.. TouchWiz for TouchWiz.. AOSP for AOSP
lacoursiere18 said:
Should be able to if you back it up previously.. but make sure it is same rom.. TouchWiz for TouchWiz.. AOSP for AOSP
Click to expand...
Click to collapse
Thank you sir. It worked just fine.
I have a noob question, I'm currently using n3bula 3.9 custom rom and it's been running fine for a while. I noticed that users chose the agni kernel whereas I chose the stock one. So my question is, is it possible to flash just the kernel from recovery without losing my data? I've spent so much time and effort customizing my phone, therefore, I just want to change the kernel. Any help will be appreciated. Thanks.
yazalsaidi said:
I have a noob question, I'm currently using n3bula 3.9 custom rom and it's been running fine for a while. I noticed that users chose the agni kernel whereas I chose the stock one. So my question is, is it possible to flash just the kernel from recovery without losing my data? I've spent so much time and effort customizing my phone, therefore, I just want to change the kernel. Any help will be appreciated. Thanks.
Click to expand...
Click to collapse
I would think that as long as it doesn't break anything you should be fine. Probably do a backup first if you're worried about it.
Thanks for the response Michael, however, that was the response I was dreading! I'm actually worried I'll lose my WhatsApp and Viber accounts because even if I backed up my data, I'd still have to register my old WhatsApp and Viber numbers all over again which I don't have anymore.. ??
What is the most versatile stock rom that i will flash after rooting and putting a recovery? Or it depends on the custom rom to which stock rom it will require?
shadow_chaser said:
What is the most versatile stock rom that i will flash after rooting and putting a recovery? Or it depends on the custom rom to which stock rom it will require?
Click to expand...
Click to collapse
Not sure if i got your question right, but there is not so many options for z5c.
Most versatile stock based custom is Kryptonian. Other one is xpower, but its more about debloating than adding mods.
Both devs have said that new version should be just around corner.
Then is of course cyanogen based roms, but unfortunately at least in my opinion not for every day use.