Hi All,
I've been trying a few different kernels on my d2spr, and though I backed up my system in complete before flashing anything, I'm curious if there's an easy way to remove kernel scripts before flashing a new one to avoid having to restore a backup every time.
For instance - I run the kernel cleaner script, then I flashed kernel X. After a bit I decided I wanted to give Freeza's stock optimized a run, so I again flashed the kernel cleaner script, then Freeza's kernel.
I'm noticing that a lot of the previous kernel X (edited and new) scripts are still on my system. Like qcom post boot sh, and other files files.
Is there a good way to get rid of these when going between kernels? I find that when they stay on the system, my OS starts acting wonky / cpu settings don't stick after rebooting / etc.
Thanks for any assistance!
-Dirk
dirkdigles said:
Hi All,
I've been trying a few different kernels on my d2spr, and though I backed up my system in complete before flashing anything, I'm curious if there's an easy way to remove kernel scripts before flashing a new one to avoid having to restore a backup every time.
For instance - I run the kernel cleaner script, then I flashed kernel X. After a bit I decided I wanted to give Freeza's stock optimized a run, so I again flashed the kernel cleaner script, then Freeza's kernel.
I'm noticing that a lot of the previous kernel X (edited and new) scripts are still on my system. Like qcom post boot sh, and other files files.
Is there a good way to get rid of these when going between kernels? I find that when they stay on the system, my OS starts acting wonky / cpu settings don't stick after rebooting / etc.
Thanks for any assistance!
-Dirk
Click to expand...
Click to collapse
root explorer>system>etc>init.d. I had this issue with the kernal I am running-Click Here To See My Post
dirkdigles said:
Hi All,
I've been trying a few different kernels on my d2spr, and though I backed up my system in complete before flashing anything, I'm curious if there's an easy way to remove kernel scripts before flashing a new one to avoid having to restore a backup every time.
For instance - I run the kernel cleaner script, then I flashed kernel X. After a bit I decided I wanted to give Freeza's stock optimized a run, so I again flashed the kernel cleaner script, then Freeza's kernel.
I'm noticing that a lot of the previous kernel X (edited and new) scripts are still on my system. Like qcom post boot sh, and other files files.
Is there a good way to get rid of these when going between kernels? I find that when they stay on the system, my OS starts acting wonky / cpu settings don't stick after rebooting / etc.
Thanks for any assistance!
-Dirk
Click to expand...
Click to collapse
Init.qcom.post_boot.sh isn't added by any kernel. It has to be there.
You can easily remove any additions by browsing the zip you flashed. See what things were added.
However, if anything was replaced, you will need to restore a backup or reflash your rom.
Sent from my buttered S3
In the Op of THIS THREAD there is a Kernel Cleaner listed. It's also linked in the post HERE.
Related
I'm a little confused on the subject of kernels and roms. Im not sure whether you have to start fresh on your phone every time you change either the rom or the kernel. If you don't have to start fresh, I mean redo all your apps and settings etc, then I would be a lot more tempted to play around with more roms and kernels.
On a second note, if I wished to change a rom or kernel, what do i need to do while in recovery, minus making a nandroid backup.
Any Help is Welcome! Thanks!
You can change a kernel without much effort and without wiping anything out. In recovery, wipe dalvik cache, and then flash the kernel. It should be a signed flashable zip.
But kernels are tricky. If you use the wrong one, you could lose things like bluetooth. Some are designed for AOSP roms, and some are designed for Sense roms, so just make sure you pick a kernel that is compatible with the Rom you are using.
Once the new kernel is flashed, you will probably not notice anything has changed, because the kernel handles all the underlying processes.
Roms on the other hand, change everything. When flashing a new rom, it's always a good idea to do a complete wipe of your phone. Even if you are flashing a newer version of the same rom.
You can use apps like Titanium backup to restore missing apps, and settings once the new Rom is on.
Thanks
Thats great to know. Thanks so much.
Hi all,
Has anyone tried the new bananacakes kernel 0.4 based on the official kernel source?
I tried installing it but my phone randomly resets every now and then. I've gone back to a Nandroid backup for now but I'd really like to use the new kernel.
Can someone who has successfully updated their InsertCoin ROM with the new kernel post some tips?
Thanks.
TBH, if you have problems with a kernel or any other file you flash or install, you're better off not using it anyway. Just "suffer" with what you've got.
You could always try a different ROM with a kernel (if compatible) or try a different kernel with the existing ROM.
Have you tried reflashing/installing the ROM and kernel from new after full wipe? Sometimes you can get issues with a file and undoing then re-flashing/installing can sort this most of the time (providing the file is stable). Are there any instability notes with the ROM/kernel? If so you may want to wait until stable versions are posted.
I updated the kernel without doing a full wipe, didn't want to lose all my settings.
Oh well, I'll do a full wipe and give it a try.
Thanks.
I have experimented with different ROMs and two versions of TWRP, and have installed the fff bootloader. (I have two working cracked-glass KF's that I picked up cheap in addition to a like-new one, so I can try different ROMs, etc., at the same time.)
I had presumed until recently that the kernel was a part of the ROM that was locked in by the ROM developer. It appears, though, judging by the two lengthy threads about a kernel 3.0, that users can install different combinations of kernel and ROM.
Can somebody explain, or point to an explanation of, the relationship between a kernel and a ROM and how one installs a desired combination of the two? Can one install a new kernel over an existing ROM, install the kernel and then a ROM, or is it necessary to do something else, such as editing a .zip file before installing it?
I realize that if I were to read a few hundred messages in a few threads, I might come up with the answers myself, but I might also transition from being a still-coherent old guy to one with senile dementia before I got to that point. Aside from my personal needs, though, it seems that an explanation of this matter deserves to be someplace where it can be easily found.
The kernel is the main component of the operating system (ROM). The kernel is essentially the middle man between the applications and the processing being executed at a hardware level. Basically the kernel is the communicator between software and hardware.
With that said, ROM developers will use a specific kernel with their ROM. You are not locked in to use the kernel which came with "x" ROM. A new kernel can be installed. You want to make certain if you are using an ICS ROM you parallel it with an ICS kernel. If you flash an incompatible kernel that could be a problem. Some kernels work better with some ROMS. Different combinations produce different bugs. It's just a matter of tinkering until you find the combination which suits you best. Hash's latest 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1591850) is popular and seems to be mostly stable with the ICS ROMS for the KF.
Installing a kernel is just like flashing a ROM although you don't need to wipe anything. Just boot in to recovery and select the kernel you've downloaded.
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
aarons510 said:
Should the custom kernel be installed after the ROM? It would seem that that would be necessary if the ROM itself comes with a kernel, as it apparently does.
Also:
? Are both the kernel and the rest of the ROM installed into the system partition, /dev/block/mmcblk0p9? If not there, then where?
? Does the kernel include the compiled code for all the standard linux commands, or only the system-level ones? Does it include the Dalvik interpreter?
Click to expand...
Click to collapse
1. boot.img
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
linktohack said:
1. boot.img
Click to expand...
Click to collapse
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
2. Kernel come with system calls, or API, the commands you mentioned is binutils (most popular is GNU's). In Android you can install busybox to get these commands.
Click to expand...
Click to collapse
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
aarons510 said:
What part of my question is this an answer to?
Click to expand...
Click to collapse
I think he meant to tell you that the kernel is usually distributed as boot.img in the ROM zips.
aarons510 said:
I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
Click to expand...
Click to collapse
The kernel is installed along with whatever ROM you install. Let's say you pick MadeUpRom and it features kernel #8 with it. You'd have to flash kernel #11 after installing said ROM.
aarons510 said:
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
Kernels are installed to the boot partition, which is separate from the ROM's /system partition. Installing a new kernel will overwrite the existing one. For the dalvik, read this to understand it better: http://stackoverflow.com/questions/7541281/what-is-dalvik-and-dalvik-cache
aarons510 said:
What part of my question is this an answer to? I'm guessing that it's meant to answer the questions in the third paragraph of my original post, but it's a bit cryptic, to say the least. I do want to confirm that the new kernel gets installed after the ROM is installed, if that is indeed the case.
I just checked the version of ICS I have installed on one KF and the CM7 installation I have on another. On both of them, the system calls seem to be in /system/bin while the file manipulation and document processing commands are in /system/xbin. Most of the latter are, indeed, symlinks to busybox while many of the former are symlinks to toolbox.
So, when one installs a new kernel, is one just over-writing /system/bin and maybe other directories with a new set of system calls, or is something else going on? And where does the dalvik interpreter fit in? Is it part of the kernel, part of the ROM, or neither?
Click to expand...
Click to collapse
In Android world, a kernel is an image contains a Linux kernel and a ramdisk which is named *boot.img* and will be *write* (byte copy) to the boot partition.
A complete ROM is a singed zip file contains at least /system files and a kernel. When you flash a ROM, it will unpack and *copy* file of /system to the system partition (that's why we wipe the system partiton aka. factory reset before we flash a new ROM) then *write* boot.img to boot partition.
Usually, a kernel needs external modules, offen reside at /system/lib/modules, so developer create an *uncomplete* ROM, which contains only kernel and these external files. This flashable kernel looks like a ROM, but it's really small size compare to complete ROM.
Like I said above, files in /system/bin/ and /system/xbin/ is not related to kernel (boot.img). They are just binaries, compiled to use system calls that kernel (and modules) offer.
--- Dev only ---
System calls is not binaries, they are CPU interupt instructions. Your programs need to be compiled to call them.
In linux, system calls are called through interupt *0x80*
After flashing a kernel, they say to do a full wipe (and then reinstall the ROM?).
My question is whether after the wipe, can I restore a nandroid backup? Setting it up from scratch and just the way I like it is quite tedious if I were to do this each time, plus download the apps from the market etc. My arc is my main phone so I don't have the luxury of flashing ROMs and kernels all the time.
Do let me know if that's possible. If not, can you tell me how you guys do it?
My arc is running Stock ICS 4.0.4 with an unlocked bootloader.
I believe you got it all wrong.... you need to do a full wipe before installing a new ROM (to make sure it works properly and nothing is left from the old one).... not a kernel... You can flash kernels as often you want without any wipes. Just dont forget the WIFI-modules (only of needed by ther kernel).
xtacy! said:
My question is whether after the wipe, can I restore a nandroid backup?
Click to expand...
Click to collapse
Just think about it, it would be pointles to delete evrething and then restore it back..
P.S.: sh*t I pushed the wrong button and thanked you instead of quote....
yea..there is no point restoring the nand after flashing a kernel...full wipe and fresh installing rom is highly recommended..
Best way is to tryout a kernel..if everything is well and good then better stick to it.
afterall wat do u look in a kernel? OC,UV, good battery life and smooth UI..once you attain all these then stick to it..
btw i have tried many kernels this month without doing a full wipe..i never faced any problem as such..i just uninstall all OC, UV apps just to be safe
Thanks for the replies guys. And an extra thanks to Antochrist for his mistake. LOL!
Another reason for my question was because one of the kernel developers said to do a clean install.
Let's say I flash a kernel with additional wifi modules. Suppose I want to get back to stock kernel and its wifi modules, do I just flash the stock kernel or do I need to do anything extra to fix the wifi?
xtacy! said:
Let's say I flash a kernel with additional wifi modules. Suppose I want to get back to stock kernel and its wifi modules, do I just flash the stock kernel or do I need to do anything extra to fix the wifi?
Click to expand...
Click to collapse
yea u just need to flash the stock kernel as wifi modules are included in the stock kernel itself
xtacy! said:
Thanks for the replies guys. And an extra thanks to Antochrist for his mistake. LOL!
Another reason for my question was because one of the kernel developers said to do a clean install.
Let's say I flash a kernel with additional wifi modules. Suppose I want to get back to stock kernel and its wifi modules, do I just flash the stock kernel or do I need to do anything extra to fix the wifi?
Click to expand...
Click to collapse
I think clean install only needed for new rom, not new kernel
cmiiw
Sent from mobile
Similar issues
Happy new years everyone!
I am pretty new to using custom ROMS and kernels and have made a standard noob mistake
which was forgetting to back up all the original software (ROM, kernel, etc). I realized this quite later
and though I have found the original ROM for my GT-P5110 I seem to have trouble finding the stock Kernel
(the one it had when it left the factory; 4.0.4) I did a search and have found my search-fu to be weak.
Can anyone help me find the stock rom for the GT-P5110 (Galaxy note 2 10.1)?
And one more thing, should I get the Galaxy S3 LTE vs. LG Optimus G vs.your opinion?
(I am in South Korea btw) Is Korean version is any different or any harder to root or to
flash a custom ROM, anyone have any experience?
Many thanks
But I did not get the Right Answer...
arpith.fbi said:
yea u just need to flash the stock kernel as wifi modules are included in the stock kernel itself
Click to expand...
Click to collapse
Thanks for the info that WIFI modules are included in the kernel and no extra additions need to be made.. I Don't know abt it ..
NOW assuming u now a lot abt Linux/Android could you please answer this for me..
- Does Restoring NANDROID
- Restore 'Stock Kernel' along with 'RIL file', RAMDISK - INIT### n stuff
Which Hyperion users need to fiddle with..
But kernel and ram disk are stored in the boot partition so does NANDROID back that up too ?
and Can you help me with RIL file related info..
Thanks
NANDroid only backs up ROM. It doesn't back up kernel. Kernel is always flashed externally, it's the same with all Android devices.
僕のLT18iから送られてきた
Is there a normal procedure people follow when flashing new kernels on JB in order to ensure they are removing any scripts or tweaks left behind by previous custom kernels?
On ICS, I used to wipe cache/dalvik and flash faux's reset kernel just to be sure, but faux hasn't released a kernel like that for JB yet.
I understand the faux reset kernel replaces the boot.img(?) but I was just curious if there is standard procedure most people follow to make sure new kernel flashes are starting from scratch.
PeterGunz said:
Is there a normal procedure people follow when flashing new kernels on JB in order to ensure they are removing any scripts or tweaks left behind by previous custom kernels?
On ICS, I used to wipe cache/dalvik and flash faux's reset kernel just to be sure, but faux hasn't released a kernel like that for JB yet.
I understand the faux reset kernel replaces the boot.img(?) but I was just curious if there is standard procedure most people follow to make sure new kernel flashes are starting from scratch.
Click to expand...
Click to collapse
bro, most of the time, i just follow the authors instruction on how to install the kernel. i don't do wipes when installing kernel ever since gingerbread and i never encountered any problem.
crazybone21 said:
bro, most of the time, i just follow the authors instruction on how to install the kernel. i don't do wipes when installing kernel ever since gingerbread and i never encountered any problem.
Click to expand...
Click to collapse
Thanks. I noticed some people having trouble with scripts sticking around after flashing new kernels, so I was just double checking,