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!
Related
So I've been flashing various roms, kernels, and radios onto my Nexus S since the release. I've never read to deeply into the exact procedure for flashing these items.
I know you are suppose to wipe device, cache, davik, ect. But then are you suppose to flash the rom, reboot the device, and then flash the kernel and radio?
What if you wiped the device and just flashed a rom without a kernel? Does the kernel you have previously take into effect or is it built into the rom?
No, Roms come with a kernel. If you don't flash a kernel you will have whatever kernel the developer uses in his/her Rom.
Sent from my Nexus S 4G using XDA Premium App
housry23 said:
No, Roms come with a kernel. If you don't flash a kernel you will have whatever kernel the developer uses in his/her Rom.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Wha? Not all ROM's come with kernels... if you flash one that does not have a kernel then you will be left with what you had before (stock).
I just learned about the kernels for the XL and was interested in having the s2w feature. Can anyone advise the most stable build I can use with stable CM10 on the phone? I am new to kernel flashing and in a few threads, it appears the kernels are either CM10 nightly enabled (past the stable -- incompatible) or for Sense ROMs (also incompatible).
the kernels in the android development are sense only. since you want sleep2wake the only real option for you is rohan's kernel, its meant for aosp roms like cm10, and is the only kernel for jb roms that has s2w.
And for future references, if I am running on Rohan's kernel and flash a Sense ROM over it what would happen? Are you suppose to flash the kernel with a Sense kernel before going back to a Sense rom?
an_xda said:
And for future references, if I am running on Rohan's kernel and flash a Sense ROM over it what would happen? Are you suppose to flash the kernel with a Sense kernel before going back to a Sense rom?
Click to expand...
Click to collapse
Yes, non sense kernels will not work with sense roms. Reinstall stock or one of the other sense kernels when you switch roms.
Sent from my HTC One X using xda premium
Skeeterdrums said:
Yes, non sense kernels will not work with sense roms. Reinstall stock or one of the other sense kernels when you switch roms.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I should be more clear. If I had Rohan on my phone and went to a Sense ROM before flashing a Sense kernel, would I brick my device or would the kernel just 'not work/disable itself'?
an_xda said:
I should be more clear. If I had Rohan on my phone and went to a Sense ROM before flashing a Sense kernel, would I brick my device or would the kernel just 'not work/disable itself'?
Click to expand...
Click to collapse
You would just soft brick and the phone would be stuck in boot loop. Why would you even try?
Sent from my One X using xda premium
ChefAnt said:
You would just soft brick and the phone would be stuck in boot loop. Why would you even try?
Sent from my One X using xda premium
Click to expand...
Click to collapse
So if you are on CM10, how would you flash the Sense kernel and a Sense ROM? What would the order be?
an_xda said:
So if you are on CM10, how would you flash the Sense kernel and a Sense ROM? What would the order be?
Click to expand...
Click to collapse
First make a full wipe (factory reset, all that), then flash your rom using the typical procedures, then flash a sense kernel. Same goes for AOSP, make a full wipe if coming from another rom, flash the rom, then the kernel.
utkaar099 said:
First make a full wipe (factory reset, all that), then flash your rom using the typical procedures, then flash a sense kernel. Same goes for AOSP, make a full wipe if coming from another rom, flash the rom, then the kernel.
Click to expand...
Click to collapse
No this could be wrong. I am assuming OP is on 1.14 hboot. Older hboots allow you to flash kernels. With 1.14, kernels will not flash in recovery. Either use fastboot to flash kernels or use flash image GUI app found in the themes and apps section. After kernel is flashed then flash your ROM in recovery as normal.
Sent from my One X using xda premium
Thanks folks. Just what I needed to know for future references.
What the other guy said is true, but that was actually what I was hinting at when I said "typical procedure." I'll be more specific next time... Also, your very welcome!
Sent from my HTC One XL using xda app-developers app
ChefAnt said:
No this could be wrong. I am assuming OP is on 1.14 hboot. Older hboots allow you to flash kernels. With 1.14, kernels will not flash in recovery. Either use fastboot to flash kernels or use flash image GUI app found in the themes and apps section. After kernel is flashed then flash your ROM in recovery as normal.
Sent from my One X using xda premium
Click to expand...
Click to collapse
in this process, when should you do the full wipe? before or after flashing the new kernel using the fastboot method?
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
Atm i have elementalx kernel installed and thinking about switching to franco when i install a new rom. I am on stock rom and will probably flash to Slimkat, will i just have to flash Rom + google apps and then elementalx/franco?
Read the op for slim. If it says to flash gapps then you'll need to do that. Then flash the kernel
Sent from my Nexus 5 using XDA Free mobile app
flashdx said:
Atm i have elementalx kernel installed and thinking about switching to franco when i install a new rom. I am on stock rom and will probably flash to Slimkat, will i just have to flash Rom + google apps and then elementalx/franco?
Click to expand...
Click to collapse
Why elementalx again? You want franco, flash that!
Sent from my Nexus 5 using Tapatalk
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.