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.
Related
well i am a little lost... i tried to update the kernel to the newest version of savaged zen. But got stuck on the white screen, so i went back and wiped both catches again, then i got to the boot animation and now thats looping.. okay so i made a backup before starting but now after wiping everything and restoring the backup is boot looping too. Any suggestions?
Try another kernel. I am using the BCblend kernel from november, it's awesome and very stable. Once you get it booted, go into your advanced wifi settings and set your sleep policy to never.
well... my backup boot loops too... wouldnt the backup have the old kernel?
It's possible your phone doesn't like that kernel either, mine didn't. How long were you running it before flashing the new kernel? I would try at least a couple more kernels and if you still can't get it booted then wipe and start over. What version of MIUI are you running?
In my opinion...if you have a good working kernel do not change it. From what ive seen every custom rom is based off a stock rom that comes with a kernel. Usually only custom kernels that match the rom version work well. So it could be the rom and the kernel dont work well together. One thing is nobody seems to list which kernel version is from which rom. So its hard to tell. Also I think your pri version will mess with compatability also. Basically newest rom versions should work with newest kernels. But if your on an older rom...the older kernels will probably work better. And usually kernels come out (it seems) before rom versions. Like new miui kernel supports 4g, but the rom does not support it yet. Also nandroid? backups should have the kernel also. Not sure bout miui backup. But wiping and installing it fresh usually works well. If not you know the deal..wipe everything..then flash the rom..and start over So.....find a good one...keep it=no issues
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Il_Tene said:
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Click to expand...
Click to collapse
Try using AK's kernel revert (back to stock kernel.)
It works for some people and for others, it doesn't though. I also had reboot problems with AK so I don't use it anymore, and also it sucks that I had to revert to stock when it happens. Hope it works for you, goodluck man.
4.2.2 - http://d-h.st/R7y
4.2.1 - http://d-h.st/2w6
From AK's thread
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Il_Tene said:
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Click to expand...
Click to collapse
Yes. The kernel id's overwritten whenever you flash a rom.
Sent from my Nexus 7 using Tapatalk HD
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.
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.
After a lot of searching, downloading, and failed attempts I finally found a CM ROM that works on my Galaxy S2 D710(VMUB) phone.
It is currently running a 3.0.x kernel, 4.2.1 JB/CM 10.1, and 6.0.2.7 CWM Recovery.
Every time I attempt to update to the CM11 nightly builds it fails with Error 7. I tried to edit the update-script to bypass the model number check but that doesn't help.
Any ideas?
(Solved?)Edit: After even more searching I found out I needed a newer kernel. I started over with a clean slate and used the latest blasphemy kernel and I was able to flash the latest nightly and gapps.