Database Info

After flashing new kernel device don't boot

Hey guys
I'm running SlimBean 2.8.0 ROM and when I try flash a new kernel, device not boot. Logo Google pass and there isn't nothing more. Only backlight of hardware keys is on. SlimRom's boot animation is not show. I tried a lot of kernels (Matr1x, Air, vta2...) but no one was work. I tried wipe data and then flash a new kernel - no effect. Wiped dalvik cache - no effect. I tried to make clean install of SlimRom's (without Gapps) then flash new kernel - no effect again. Before flashing each of that kernels I make a clean install of SlimRom (with its stock kernel). Now I'm using stock kernel.
I need a custom kernel for USB host mode.
Any ideas?

Make sure you are flashing a cm kernel
Sent from my Nexus S 4G using xda app-developers app

n2d551 said:
Make sure you are flashing a cm kernel
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
+1 for that. At 2.8 SlimBean merged CM kernel code meaning you have to now flash the CM kernel and not the All Others.

I'll try this. Thanks
Edit: It works! Thanks again!

[Q] Updating Kernel

Sup, so I'm still quite the noob at all the rooted stuff, like flashing etc... I have franco kernel and im running cm, when i update my kernel am I supposed to flash the kernel again or will it actually be updated?

For which phone n its not necessary to flash again n again unless u flash with custom rom
Sent from my GT-I9082 using xda premium

(But CM has really good kernel)

When flashing a custom ROM the kernel is flashed as well. Most of the time that kernel is an adapted kernel of a widely used one (e.g. Semaphore or DerTeufel), so that it can be verified in conjunction with the ROM. So yes, when flashing the custom ROM, immediately after that flash the kernel of choice. With the right app, you can even configure the kernel and play around with strings and scripts
Jopejt

Can't boot custom kernels

I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Caspertje19 said:
I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Make sure all the partitions are the correct size as well as make sure the Kernel supports the ROM. If you read the individual kernel threads and do a search, the information should be available. Its been discussed that many ROMs have switched some code in the nightlies to not being supported by some kernels while others work (such as Chaos kernel working on CM ROM while Franco kernel works stock). Depends on your preference then once you find which are supported and which are not. There is also a thread (I believe in Original Development or the other development thread) that bridges the kernel support of some to work on the newer CM based nightlies based on the CAF/nonCAF system codes that are being worked on.

Caspertje19 said:
I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Because you flashed a kernel that is not compatible with the rom. Re-flash the rom and then find a kernel that is compatible with AOKP.

I was coming from the nexus 4 running AOKP and they have had a poll about caf or non-caf. They decided non-caf, that's why I thought Franco kernel should work (worked on nexus 4).
But I see I have to do some searching.
I thought the decision was already made by the AOKP to use aosp kernel.
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] flash new rom from another

I'm using catacylsm rom+franco kernel
If I want to flash another rom, do I need to flash back to catacylsm's kernel and flash the new rom?
Thanks!

Hi,
No, no need to flash back the stock kernel before (or the one from Cataclysm rom). Since you'll flash another rom you do a full wipe (clean flash), it will be enough.
Sent from my Nexus 5 using xda premium

Why doesn't other kernels work in SlimROM?

I have some kernels for example AK and Boeffla,but them doesn't work in Slimrom.why?I think slim is development on asop that it support these kernel.Who can tell me why?
Sent from my Oneplus One using XDA Free mobile app

I have used ak kernel on Robbie's latest build no problem.

I've never had any problems flashing other kernels
Sent from my Nexus 5 using XDA Free mobile app

if use other language for example chinese,flash AK kernel on slimrom,it will reboot again....

I am having difficulty getting Franco Kernel to work, I just get a constant boot loading screen and have to force shut down, anyone know of any issues?
Cleared cache and dalvik before and after install and am using the right version for my device.

Same here
Flashing Franco's Kernel R24 and R42 for OPO resulted in hanging boot on logo. Reflash full rom and apps fixed it. But unable to flash Franco Kernel.