I am currently using cm11 nightly, however i cant find any kernel that works......
i tried franco, faux, elemental, bulletproof.
at first i thought it was my recovery being outdated, so i updated twrp, didnt work, tried cwm, didnt work.
so i was like, maybe it was my bootloader? I updated it to 402, repeated previous steps, didnt work.
I thought it might be corrupted file, nope, redownloaded it, did sumcheck on some of the files with key provided.
after i flash these kernels, on first boot i'll see a scrambled screen and just hang there.
Is it just me or is anyone suffering from the same problem as well?
You need a caf based kernel for CM. You have been trying AOSP based kernels which will not work with CM.
Related
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.
First off, a little background info:
Rom: CM 10.1 (5/22)
Kernel: stock cm
Recovery: twrp 2.5.5.0
Anyway.. I've noticed this issue for probably two months now. Whenever I try to flash ANY kernel on my device, I don't get past the initial boot screen. I do make sure that I'm flashing the correct kernel (that is, one that's compatible with the rom that I'm using) and no matter what, I can't get past the startup screen. Even if I flash the stock kernel, it won't boot.
Conclusion (that will help troubleshoot):
-It can't be recovery, unless an update caused a fluke. I've flashed kernels using twrp before.
-I would suggest that it's the rom, but even if I go back to the roms (RootBox to be more specific) that were over clocked, it won't get past the boot screen with third party kernel. It will boot with just rom however.
-it can't be incorrect flashing methods.. I've done this for years without (many) issues.
I'm beginning to think ill have to Odin stock 4.x.x, but I would like to take another route if at all possible. Any suggestions?
Gfrt94yn said:
First off, a little background info:
Rom: CM 10.1 (5/22)
Kernel: stock cm
Recovery: twrp 2.5.5.0
Anyway.. I've noticed this issue for probably two months now. Whenever I try to flash ANY kernel on my device, I don't get past the initial boot screen. I do make sure that I'm flashing the correct kernel (that is, one that's compatible with the rom that I'm using) and no matter what, I can't get past the startup screen. Even if I flash the stock kernel, it won't boot.
Conclusion (that will help troubleshoot):
-It can't be recovery, unless an update caused a fluke. I've flashed kernels using twrp before.
-I would suggest that it's the rom, but even if I go back to the roms (RootBox to be more specific) that were over clocked, it won't get past the boot screen with third party kernel. It will boot with just rom however.
-it can't be incorrect flashing methods.. I've done this for years without (many) issues.
I'm beginning to think ill have to Odin stock 4.x.x, but I would like to take another route if at all possible. Any suggestions?
Click to expand...
Click to collapse
What kernel are you trying to flash?
ROOTBOXED!
roughneckboren said:
What kernel are you trying to flash?
ROOTBOXED!
Click to expand...
Click to collapse
I've tried many kernels (again, with various ROMs)
Kernels:
King Kanger's
SOAP
some AOSP kernel (don't think there was a specific name)
And something else by ManelScout
I've tried using ROMs:
PA
PACMAN
RootBox
CM 10.1
LiquidSmooth (with its 2.16ghz kernel, still unsuccessful)
Jedi
And DevientXone
.. Mixing and matching, but using the correct kernel with its base; no luck whatsoever. If you haven't noticed, I stay away from stock-based roms, as I like the more streamlined, slicker software that AOSP has to offer. I can't say that I've tried reverting to stock I317 TW based roms. Though, I wouldn't see that AOSP is the issue.. It's almost like a piece is missing since it just happened out-of-the-blue and I can't seem to remedy the problem no matter how many different combinations I try and how many times I download it.
You may have a corrupted device...
I suggest a full wipe...then a fresh install of a rooted stock rom via odin...
then push a fresh recovery via odin...use the UCAMA4 build from mr. Robinson's thread...(development section)
Then attempt the rom of choice..
but first verify the stock build will boot properly...
many devices get corruption within the partitions...especially with the large amount of flashing you have done...
my .02....g
I was afraid of that.. Oh well, it was worth asking. Can I use mobile Odin to flash all of these things or would you suggest using a computer? I've never used Mobile Odin, but I'm familiar with how all of that stuff works (on pc), so I assume it's similar.
PC....
Mobile Odin is a fine program ...but why risk flashing the device, with a possible corruption issue ??
Eliminate the risk ...IMHO ...g
AOKP 2013-11-14 build, 's been working fine for the past two weeks or so. Since the default kernel doesn't seem to work I tried flashing other kernels but after flashing, the device doesn't boot. Tried franco.Kernel, LeanKernel, Stock 4.3 kernel, none works. What could be the cause of this?
Maguro
AOKP 2013-11-14 build (4.3.1)
TWRP 2.6.3.1
No kernels seem to work.
Update
I restored a working backup. It didn't work. It's stuck on the X logo.
Any things I can do? Flash clean ROM?
I had the same issue on another rom (carbon). They had changed something, so the kernel had to get a special fix to work. Try asking on the aokp thread or forum (can't remember if they got one)
It seems you flashed wrong kernel or it is not compatible with your current rom.
Sent from my Galaxy Nexus using Tapatalk 4.
What am I missing? Every time I flash CM it just bootloops at the LG screen. I've flashed before so I'm very familiar with the usual stuff. I downloaded CM from CMs website, the most recent nightly, for my ls980. I'm running TWRP 2.7.0.0 for ls980.
I've heard of things being "lokified". I tried flashing through flashify which I heard "lokifies' files if needed. I'm not sure though.
Only thing I can see is that maybe my file isn't lokified? Anything I am missing?
JamesChilds said:
What am I missing? Every time I flash CM it just bootloops at the LG screen. I've flashed before so I'm very familiar with the usual stuff. I downloaded CM from CMs website, the most recent nightly, for my ls980. I'm running TWRP 2.7.0.0 for ls980.
I've heard of things being "lokified". I tried flashing through flashify which I heard "lokifies' files if needed. I'm not sure though.
Only thing I can see is that maybe my file isn't lokified? Anything I am missing?
Click to expand...
Click to collapse
Never mind, I figured it out. apparently the compatible kernels aren't bundled in the zip? Every other device I have used had the kernel included. If I am wrong please clarify. Also, is there a list of kernels/radios for my device somewhere that say what they support?
Never mind guys it is still not working. I am flashing the Rom, the Gapps, the KK aosp modem and a kernel made for aosp.
JamesChilds said:
Never mind guys it is still not working. I am flashing the Rom, the Gapps, the KK aosp modem and a kernel made for aosp.
Click to expand...
Click to collapse
did you ever solve this i need help flashing roms too.
Are you using the zv8 modem.IMG if not that can cause bootloop also be sure to wipe cache/dalvik
I could never get CM, PA, or PAC to work. I just installed Slimkat rom with no problem. You might need to update your TWRP as well, I think it has been updated since 2.7.0.0 to 2.7.0.2? If I am not mistaken.
Hello, normally I do lots of research and searching in order to figure out problems for myself, but this one I have been stuck on for weeks.
I am on SGH-T999v, here is my issue.
I am trying to use either the latest 1.5 Spirit Rom, or M4 gummy Rom in combination with KTOONSEZ Kernel from here.
If I try to flash the kernel with latest versions of those roms, my baseband says "UNKNOWN" and my IMEI gets zero'd out.
Also it tells me that I have no sim card inserted. I have tried formatting dalvic/cache before and after installation of kernel as well as fixing permissions.
Both Spirit 1.5 and Gummy M4 work no problem without the custom kernel installed.
Also, on only 1.1 Spirit and M3 gummy, am I able to use the custom KT kernel and still have my signal.
Okay now here is the strange part of the problem.
Currently I am using the custom recovery TWRP that lets me use multiboot from here
And after successfully creating a multiboot rom, I go ahead and install Gummy M4 + Gapps + KT Kernel and boot it up, to find out that it actually works perfectly fine.
My baseband shows up, and my signal connects.
Also the version im using of the recovery menu is V2.11
I am just wondering why is it that the rom + custom kernel doesn't work with a regular flash, and that it only seems to work when I multiboot it?
What I want is to not have to create a multiboot rom in order to use this, I want to actually flash these to my phone.
Please help me, anyone who has any idea of what I am talking about..Sorry if I have not been clear enough. Thank you/.
Edit: I also forgot to mention that I have tried flashing the stock modem after the kernel + rom installation through odin, that did nothing.