So, i have pure stock as my internal rom, as id just like to have it there, but i dont use it, and i've been trying to flash glitch kernel on the 10/6 build of AOKP and 10/08 pacman, and no matter what i do it refuses to flash, everything'll work, but ill boot into the rom, and the kernel will be the stock one that came with the rom. I've made sure i'm flashing the version for the latest CM because the other gives me a blue screen.
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
So I cut my Android flashing teeth on the original HTC Magic, then to a Desire and Galaxy Tabs on the tablet front. Even cooked a few roms back in the Magic days (although was little more than mashing bits into an update.zip if I'm honest)
Anyway, I'm used to the scenario where, once you've got a viable recovery, you can thenceforth flash and backup/restore whatever you want without any need to plug the thing into a computer and do any messy fastboot stuff. I can't find a clear indication, but the vibe I'm getting is that in Sonyland one must always flash the boot.img of a new rom before going into recovery to install a new update.zip. is this right, or am I taking instructions designed for first timers too literally?
When you flash your first rom, let's say CM9, you will need to install FXP's CM9 boot.img(AKA kernel). Then if you wanna update your CM9 rom(IE. From Nightly 1 to nightly 2), you can use the same boot.img. BUT, if you want to flash stock based rom, like Arconium ICS, you will need stock kernel(Sony stock kernel, DoomKernel), if you want to flash stock based GB rom, you'll need stock based Gingerbread kernel(DoomKernel for GB f.ex).
When you go to the rom's thread, the developer always tells what kernel to use. If you have one of the listed kernels, you're good to go, just flash the rom itself, and no need to flash kernel again.
I hope I was clear enough
No, that's a valid question. I don't recall the explanation (if any) but recovery on Sony's phones can't modify the kernel for some reason.
While on other phones like your old htc, and even most samsung phones, it is possible to update the kernel from recovery.
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.
ive installed the multi rom manager for the sprintm8 ..after reading up on everything..its the latest test version pose to help with hanging up when booting secondary roms..i still freeze up bout everyother time trying to boot from the manager app to secondary rom..i tried flashing updated firmware from hboot ..the updated firmware was the one updated in aug..hope that was the latest..still have issiue..i have bad boyz sense as base rom with elementalx as kernal with patch..have pacman as secondary..everytime ive attempted to make changes like the kitkat sd card fix..or install xposed framwork..ive had to wipe data and start over cause after rebooting would just go black screen..thinking i bricked it..also tried flashing liquid smooth as third rom..did fine..but no mobile data or wifi worked..im sticking to aosp roms cause ive read they all mostly work although id love to have another sence based rom as well..but the ones i tried never booted..read how its possible to alter the zip then repack..but sounds to advanced for me..question is do i need to flash anotherr kernal in my aosp roms to get it all working..i know the base rom gets the elementalx kernal with patch....but do i need another kernal for other roms to get everything working..and why am i freezeing dureing booting up from multirom manager into the aosp secondary roms?
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.