[Q] Custom Kernel Stock Rom? - Captivate Q&A, Help & Troubleshooting

I am wondering if i can flash a custom kernel over my stock 2.2 Rom? So that i can change the boot animation splash screen along with maybe overclock/undervolt. But mostly i want the bootanimation.zip splash screen. Any way i can do this?

Allmaechtig said:
I am wondering if i can flash a custom kernel over my stock 2.2 Rom? So that i can change the boot animation splash screen along with maybe overclock/undervolt. But mostly i want the bootanimation.zip splash screen. Any way i can do this?
Click to expand...
Click to collapse
You can do that using Odin (not the one click).
I suggest you go check AdamOutler's video on how to flash a kernel from stock 2.2. It is well explained and will work on every kernel that has cwm recovery in them (speedmod, ursa minor, onix.. etc).

Related

[Q] Installing Custom Animation on Stock Rom

On the perception rom forum there is .zip for custom animation. When I had that particular rom on my phone, I installed them fine with cwm, but now I am on the stock i896 rom and I am wondering if installing these .zip files would still work, or are they made for that rom?
They wont work. The custom bootanimations are only for custom roms.
joeshmoe08 said:
They wont work. The custom bootanimations are only for custom roms.
Click to expand...
Click to collapse
not boot animation, transition animations

[Q] Custom boot animation on JVO

Hi,
I'm using deodexed rom from http://forum.xda-developers.com/showthread.php?t=948790 , and speedmod for JVO from http://forum.xda-developers.com/show....php?t=1044519
In description to speedmod author says that the kernel supports custom boot animations, but rom support is required to make it work.
I'm not sure what the "rom requirement" means. Does anyone know?
Can I just upload bootanimation.zip to /system/media?
At the moment it doesn't work - when I do so, then the boot animation is actually changed, but not to my uploaded animation, but to "fail safe" animation, which is simple "android" text shining.
Do I do something wrong, or do I need some special support from rom (except for my kernel which supports it)?

[Q] How to remove or replace 2nd boot screen ?

I have a rooted i9000 and flash the gto kernel.
Then it add a 2nd boot screen to my phone.
Baseband version : I9000XXJVT
Kernel version : 2.6.35.7 [email protected]#BETA4.2_4
There are the video of my boot screen
http://youtu.be/2eylQ-ub81o
How can I remove or replace it?
(I find some code in other post : fastboot erase splash2
But I don't know I can use it in which mode or status.)
The second boot screen that appears when you boot your phone is the ROM's boot screen, which is changable (depending on your ROM). The first one shown is your kernel's boot screen.
What ROM are you using?
upichie said:
The second boot screen that appears when you boot your phone is the ROM's boot screen, which is changable (depending on your ROM). The first one shown is your kernel's boot screen.
What ROM are you using?
Click to expand...
Click to collapse
sorry for missing information
Baseband version : I9000XXJVT
Kernel version : 2.6.35.7 [email protected]#BETA4.2_4
There are the video of my boot screen
http://youtu.be/2eylQ-ub81o
when I use JVT ROM don't have any problem , still one boot screen.
after flash gto kernel , the second boot screen appears
I don't believe you can change the kernel's bootscreen without recompiling it.
for replace change kernel...if u want a personal image contact your kernel developer
i changed my boot animation by using an app called bootanimation utility
first had to put the new boot animation in my internal sd card
Super_Sebas said:
i changed my boot animation by using an app called bootanimation utility
first had to put the new boot animation in my internal sd card
Click to expand...
Click to collapse
That won't work. We are talking about the kernel bootanimation.
ooo ok
my bad
just trying to help

[Q] Weird display during boot after custom FW install

After installing GalaxyROM_v14 I have weird display during boot after custom FW install
See picture.
Any idea?
I think it's sometimes caused by the custom kernel. I've seen similar behavior during boot on some custom kernels. If everything works otherwise, it's nothing to worry about.
I get something similar when booting into recovery with DamianGTO's kernal.
Sent from my GT - I9000M running Tornado JVR Gold with Tornado kernel.
I also get this when i try and open some apps/games but then it runs normally afterwards
That would normally be associated with a voodoo kernal.

Kernel Confusion

Hi,
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery mentions a "hardcore's kernel". What kind of kernel is that? Is it the actual system kernel used by the ROM one is installing afterwards or is it just some sort of boot kernel for the recovery application?
It also mentions hardcore's even though the kernel logo during booting refers to Semaphore.
No one?
neroux said:
Hi,
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery mentions a "hardcore's kernel". What kind of kernel is that? Is it the actual system kernel used by the ROM one is installing afterwards or is it just some sort of boot kernel for the recovery application?
It also mentions hardcore's even though the kernel logo during booting refers to Semaphore.
Click to expand...
Click to collapse
It is not the Stock kernel, it is a customized kernel which can be used for the custom ROM installation via ClockworkMod_Recovery.
thanks.
Thanks forupeople but that was not exactly the question. I would like to know whether the mentioned kernel is the actual kernel on which a ROM then is running on or whether all ROMs come with their own kernel and this is something else.
Really no one?
neroux said:
Hi,
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery mentions a "hardcore's kernel". What kind of kernel is that? Is it the actual system kernel used by the ROM one is installing afterwards or is it just some sort of boot kernel for the recovery application?
It also mentions hardcore's even though the kernel logo during booting refers to Semaphore.
Click to expand...
Click to collapse
All ROM's have kernels included in their package, without it your phone wont be able to boot..In this case Hardcore ( its actually a speedmod kernel, maybe tweaked by Hardcore) is being used to give you CWM recovery on Stock ROM's which do not have CWM recovery but only 2e recovery., after you flash CM, its removed and the new kernel from your update, is used
Instead of Odin, CWM recovery is used for ICS and JB installation
xsenman said:
All ROM's have kernels included in their package, without it your phone wont be able to boot..In this case Hardcore ( its actually a speedmod kernel, maybe tweaked by Hardcore) is being used to give you CWM recovery on Stock ROM's which do not have CWM recovery but only 2e recovery., after you flash CM, its removed and the new kernel from your update, is used
Instead of Odin, CWM recovery is used for ICS and JB installation
Click to expand...
Click to collapse
Thanks. I have to admit I am not really very familiar with the boot process, however I was under the assumption that CWM is just a replacement for the stock's basic boot/recover loader and both do not need an actual Android kernel as they both come before it in the boot order.
neroux said:
Thanks. I have to admit I am not really very familiar with the boot process, however I was under the assumption that CWM is just a replacement for the stock's basic boot/recover loader and both do not need an actual Android kernel as they both come before it in the boot order.
Click to expand...
Click to collapse
To make it simple.
Boot loaders are generally locked, hence needs to be rooted (unlocked), in oder to add CWM to it.
Custom kernels or kernels that are customized, do this function of rooting (unlocking the boot loader) as well as adding the CWM (customized recovery features) to the boot loader.
Only customized kernels will work with custom ROMS.
Hence when you flash a custom kernel on top of a stock ROM/with stock kernel, it is replaced and gives the added features (that stock kernel lacks) that is needed for flashing Custom ROMS
The reason being Gingerbread stock kernels will not work for ICS ROMs..hence must be replaced and this is vital for phones operations, since one main function of kernel is to control the hardware.

Categories

Resources