I flashed KT747 a two or three days ago. I just noticed that I am back to the stock kernel. I didn't flash back to stock kernel. The only thing I can think of is that I tried flashing the 10.1 12/10 preview build but CWM aborted right away due to bad download. So nothing should have been flashed. I have also made two nandroid backups since flashing KT747.
I didn't notice any big difference between stock kernel and KT747. I'm not sure if I'll relfash or not. I really just want to know what the heck happened
Turns out flashing nighties also flashes back to CM kernel.
cavolt said:
Turns out flashing nighties also flashes back to CM kernel.
Click to expand...
Click to collapse
Yes, flashing any ROM will over-write the kernel
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've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
fuhrl said:
I've been trying out multiple ICS ROMS for my R800x (FXP, AOKP, CM9, PlAyOPS and maybe something else, I've lost track) and I can only get the WiFi to turn on with PlAyOPS ROM. It's not a connection issue, I cannot actually get the WiFi to switch on, the slider is grayed out and it won't even slide over to the on position. I've tried the WiFi fix zips that are brought up on the ROM specific threads to no avail. I think I've tried every kernal/ROM/WiFi fix combination that I've come across. I'm currently using Keiran's 2.6.32.9 Darkforest kernal but I have also tried the FXP kernal and the LuPus v3 kernal.
The reason I'm not just sticking to the PlAy OPS ROM is that I use the bluetooth audio feature quite frequently in both my cars and it doesn't work correctly on PlAyOPS. I was able to get the bluetooth audio to work on FXP and, if I remember correctly CM9. I haven't tried bluetooth audio on AOKP yet. If I could get the WiFi to work on either of these ROMS I would be extremely happy.
I've been searching the internet and scouring this forum for a fix for my issue for nearly a month but I cannot find a solution for my specific problem. I greatly appreciate any assistance!
Click to expand...
Click to collapse
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Xperia Player said:
Back up data, flash back to stock rom, install kernel, wipe data, cache &dalvic cache in recovery mode, re-install CM9 with the included FXP kernel and that should be it.
Click to expand...
Click to collapse
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
fuhrl said:
when you say install kernel, which kernel am i installing? the stock kernel or the FXP? when i re-install CM9 don't I have to install the FXP kernel first or will it automatically do it for me when i re-install CM9?
Click to expand...
Click to collapse
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
DubleJayJ said:
Install FXP kernel first, then flash CM9.
Sent from my unlocked R800x using XDA Premium
Click to expand...
Click to collapse
ok. thanks. Just as a clarification to the first part of the original response, I am installing the original stock kernel after i flash back to the stock ROM?
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
fuhrl said:
well, i went back to stock, flashed the kernal, wiped all my data, flashed the FXP kernal then re-installed FXP with no luck. I tried flashing the wifi zips after than without success. i guess i'm stuck with what i have unless there's something else i could try.
Click to expand...
Click to collapse
What version of FXP are you using, and what are the wifi zips called that you're using?
lightningdude said:
What version of FXP are you using, and what are the wifi zips called that you're using?
Click to expand...
Click to collapse
i used FXP 132. I know it's not the latest but I'm sure that it was when I downloaded it a month ago. The zips were cleverly named wififix2, WiFi_FiX_LuPuSv3 and the other was CDMA_mega_fix_v2_by_Leraeniesh. The last one had a WiFi fix in it by Atarii or someone like that.
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
nyvang101 said:
had the same problem on my play (GSM version) here is what i did. and im sure it will work for you. flash the latest FTF for your device (Baseband).
when done Put the CM 9 Kernal on the phone. Boot in to recovery. do a factory reset. flash the CM 9 reboot and you are good to go.
Click to expand...
Click to collapse
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Xperia Player said:
Speaking of wifi problem I cant get wifi to work on GB tweaked running doomkernel V2.....odd.
Click to expand...
Click to collapse
i think you have to flash doomlords wifi modules in recovery. it's what worked for me when i was using that rom.
http://forum.xda-developers.com/showthread.php?t=1579388
fuhrl said:
i've done that twice now. this has been extremely frustrating. i don't know why the wifi will work without fail on one ROM but not work at all on others.
just to make sure i'm doing this correctly. After I flash the original FTF am I flashing the CM9 kernel directly after that? Do I have to restore the original kernel at all?
Click to expand...
Click to collapse
The ftf has the stock kernel in it.
Sent from my SCH-I500
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
nyvang101 said:
here is what i did step by step.
1 Flashed Everything back to original. using R800i_4.0.2.A.0.62_Generic Baseband. (stock kernel too) using flashtool form here http://forum.xda-developers.com/showthread.php?t=1351299
2 booted the phone.
3 shut down the phone
4 Flahs kernel provided with the rom.
5 Went to recovery. Ran a reset factory. clear cache, clear Dalvik, reset battery stats.
6 Flashed the rom. in this case FXP 135.
Click to expand...
Click to collapse
did this work? i have the latest PACman JB rom for the r800x and im using the lupus v5 kernel that came with it. for some reason all the other roms have working wifi except cyanogenmod based roms....... why is this?
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
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.