heredago's blog

February 3, 2013

Custom kernel Nexus 4

Filed under: Uncategorized — Tags: , , , , — heredago @ 23:01

Faux kernel:

The way I see it, yeah. If what you want is a kernel that allows you to over clock your gpu/cpu and a kernel that has a lot of configurable options that normally wouldn’t be possible on stock (swipe2wake is built in, custom governors, a bunch of options I’m not really familiar with) I recommend faux or Bricked. You’ll have to tweak your kernel if you want something good to come out of faux.

Franco kernel:

If you’re looking for something that you can flash and forget, franco is what you need. The default options on franco are amazing. The only thing you might need/want to tweak are the colours and/or your voltage.

The easiest way is to download his app and use that to flash and control his kernel.

Basically, every ROM comes with its own kernel. So when you switch ROMs, whatever kernel you have will be overwritten with whatever kernel that comes with the ROM.

Yes Franco’s kernel is compatible with CM10.1. Most kernels are compatible with most ROMs.

The only thing that you need to remember is to be careful and not flash a different device’s kernel, if the flashing involves tinkering with the bootloader, doing so will brick your device.

Also, some kernel developers (like Franco) modified the boot.img to modify the ramdisk. When you wanna switch from such a kernel to a different kernel, it’s best to re-flash your ROM so that the boot.img is reset to stock configurations. Not doing so will result in a bootloop.

Refer to the side bar for more information about kernels, there’s an excellent guide written by IAmAN00bie

Installing a Custom Kernel

Just flash the zip in your recovery of choice. No need for wiping cache or anything. However, one thing to note that might save you some headache in the future is: what exactly are you flashing? When you flash a kernel, you are not just flashing the kernel, you are writing to the entire boot partition. The boot partition is made up of the kernel AND the ramdisk (the ramdisk is an image that the kernel mounts read-only at boot, it is basically used by the kernel to mount the rest of the system images). Some kernel devs pack their own ramdisk into their boot.img that you are flashing, so when you try to flash a DIFFERENT kernel, you end up in a bootloop. (An example: flash Franco kernel –> flash Faux kernel on top = bootloop.) To solve this you need to reset the ramdisk by flashing a stock reset kernel with the stock ramdisk[6] .



1 Comment »

  1. You actually make it seem so easy with your presentation but I
    find this matter to be actually something which I think I would never understand.

    It seems too complicated and very broad for me. I’m looking forward for your next post, I will try to get the hang of it!

    Comment by Jeannie — April 21, 2013 @ 00:42

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Create a free website or blog at

%d bloggers like this: