Database Users

[Q] CM7 Nightlies Not Flashing

There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.

hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.

Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.

Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.

Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk

ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA

ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA

Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239

hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.

janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery

Problems with CM9 on Red lens Defy

-Solved btw-
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash Gapps and CM7 Kernel
7:Clear Cache and Dalvik Cache
Click to expand...
Click to collapse
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
FAQ:
Q: I installed 08/12 build(or newer), but it gets stuck at the CM boot logo. What do I do?
07/12 contains the required 2.3 kernel. 08/12 and newer do not. If you have installed 08/12 or newer, enter recovery and flash the 2.3 kernel, then reboot. This applies only to Defy owners; Defy+ owners already have 2.3 stock ROM and kernel, so they do not need to apply the kernel.
In fact, the kernel zip for Defy owners is the kernel from Defy+.
Click to expand...
Click to collapse
I've tried everything I can think of. Can anyone help?
Thanks.

pk92 said:
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
I've tried everything I can think of. Can anyone help?
Thanks.
Click to expand...
Click to collapse
Hi,
Can you also provide the following info:
Which ROM did you have as stock?(Was it a froyo kernel or GB kernel as stock)
If you already had GB ROM in your phone you don't need the kernels to be installed!

It was a Froyo kernel

He's right. U don't have to flash a kernel if u were on froyo (2.6.32.9-gb08c3c8). Just make a wipe after installing the cm9 rom.
U only have to pick the right version. There are froyo-cm9 builds and GB-cm9 builds (so if u are on GB-kernel right now, take a GB-Build).
Or try the "codename android 1.5.5"... (froyo-kernel!) it's ported from the nexus
I'm testing this rom right now and for me it's working much better than cm9 builds.
Greetz

I recieved a pm suggesting installing cm7 then cm9 over, but more bootloop..
Sent from my Huawei_8100-9 using XDA

Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA

pk92 said:
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
Click to expand...
Click to collapse
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.

I have no idea if it's Quark or Epsy :S

hboy1337 said:
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
Click to expand...
Click to collapse
pk92 said:
I have no idea if it's Quark or Epsy :S
Click to expand...
Click to collapse
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....

pranks1989 said:
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
Click to expand...
Click to collapse
What I usually do when installing roms is this:
-Enter Stable Recovery
-Factory reset & clear data
-Install Zip from SD Card (Defy CM9.zip)
-Wipe cache
-Wipe dalvik cache.
So I need to do a Factory reset & data wipe in stock before flashing CM9?

I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)

pk92 said:
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
Click to expand...
Click to collapse
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!

pranks1989 said:
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
Click to expand...
Click to collapse
I eventually decided to flash a froyo SBF (2.2.2), and flashed CM9 Defy from here. Suggested to me by Pottkopp.
I didn't flash any kernel and it worked fine.
Also installed Pottkopp's AIO.
So, all solved

Can someone help me?
Ok!
So i have green lensed defy. I already had CM9 installed( installed it using normal procedure). So i decided i will return to stock, by recovering backup. So i did. After a while on stock, i decided to go back to CM9. I forgot to do factory reset, and after install wipe chache and dalvik.I booted phone, and entered requesting data. I after that got back to recovery and did factory reset via custom recovery, and installed it again using correct method. My phone seems a bit slower than before, and did i damaged my phone?

CM9 nightly on Vibrant

I am writing to see if I can get some help, I have tried to install CM9 nightly on my vibrant and I get an error before it installs. My phone has been setup for use on both TMobile and AT&T could that the reason? It seems to be a verifaction problem.

Have you tried to install cm7 then try cm9??
Sent from my SGH-T959 using xda premium

I have not tried that. I was coming from ICS Passion and did a data;system;cache wipe then factory reset. I will try to install CM7 doing another wipe and then try again. Thank you for your reply.

If I remember I think it is a kernal related thing but not sure I'm at work so I can't really look
Sent from my SGH-T959 using xda premium

I recommend Odin to jfd. Here what I did.
First make sure you back up your files and make sure you remove sim card and memory card too
1.Odin to JFD
2.Dail *2767*3855# (to format it because there still old file there)
3.Install GB bootloader
4.Install Update.zip (that have CWR with the update)
5.In recovery Perform a factory reset, wipe data/cache,clean cache partition
,wipe dalvic cache and format system( in Advance setting)
6.Flash CM9 ( you might have to flash twice)
7.Perform a factory reset,wipe date/cache
8.Install Gapp
9.Reboot
I dont have to flash CM7 first. I just flash straight to CM9 but I do recommend intsall GB bootloader

Well since I don't use Windows I will try this with Heimdall. It seems strange that I can install ICS Passion but not CM9. I also tried installing CM7 nightly with a clean wipe but had no luck there. I was looking for a kernel image to flash but it was late and the site was not responding for the kernel image I was trying to download. The plus is this is my old phone I use around the house like a mini tablet since it's only hooked up to the wifi.

I have been successful in flashing CM9 nightly. What I did was download glitch V14-B6 flashed that rebooted into recovery then flashed CM9 nightly
Now I have it running I would like to thank everyone who replied.
Sent from my MB860 using xda premium

TWRP restore

I restored my phone using TWRP. Everything works ok except if I try to restart the phone it hangs at the Samsung logo. Please someone help me to get my phone back working :crying:

I'm asking you restored a stock backup. Did you wipe before restoring? Have you wiped since?

Yes and yes. My phone works perfect but won't boot up if I restart it. Then I need to wipe, format, restore just to boot up again. Has happened three times in a row so now I cannot restart or turn off my phone without taking 15 minutes to restore again
Sent from my stock rooted i337m

WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.

TheAxman said:
WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.
Click to expand...
Click to collapse
I'm sorry that I neglected to mention which device in particular. I am using a ROGERS SGH-I337m Galaxy S4. It is currently running TW stock (rooted with motochopper). If I understand you correctly, I should turn my phone off, and then boot into recovery, and then flash the stock rogers kernel, (wipe cache, dalvik, fix permissions) and then it should boot? I should note that the last time I tried wiping Dalvik before booting the system, the dalvik wipe failed.....
P.S. I couldnt get wifi working on Omega v7 so I tried google edition 1.3 but found it too vanilla. I really want omega v7

trueking7 said:
I'm sorry that I neglected to mention which device in particular. I am using a ROGERS SGH-I337m Galaxy S4. It is currently running TW stock (rooted with motochopper). If I understand you correctly, I should turn my phone off, and then boot into recovery, and then flash the stock rogers kernel, (wipe cache, dalvik, fix permissions) and then it should boot? I should note that the last time I tried wiping Dalvik before booting the system, the dalvik wipe failed.....
P.S. I couldnt get wifi working on Omega v7 so I tried google edition 1.3 but found it too vanilla. I really want omega v7
Click to expand...
Click to collapse
I'd be more worried of getting my phone working not what rom you want to flash.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Right now I am trying to find out if flashing the stock kernel will enable me to reboot normally? I will copy the kernel to the card just in case my phone powers off. Then I will try flashing it to see if phone will boot. If not then I will restore from nandroid yet again and be unable to reboot.
I will use Odin as a last resort.
Ps. This would be a lot easier if install instructions were carrier specific.
jd1639 said:
I'd be more worried of getting my phone working not what rom you want to flash.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
TheAxman said:
WHAT DEVICE
Sheez, how can someone help if you do not tell us what type of att device you have, I suppose you have a att, or you would not be posting here...we are not Houdini's here...help us help you.
You have a kernel issue with your backup, I bet. get the correct kernel for YOUR device, restore backup, AND BEFORE YOU BOOT, flash the kernel.
Click to expand...
Click to collapse
Sent from my stock rooted i337m

here is your answer..
flash omega
before you boot, flash YOUR CARRIER kernel.
thats it...easy easy easy.
course this after you get the correct kernel flashed so you can even boot.
answer is...
get into recovery, flash YOUR CARRIER kernel, you should boot up with no problem
your welcome

TheAxman said:
here is your answer..
flash omega
before you boot, flash YOUR CARRIER kernel.
thats it...easy easy easy.
course this after you get the correct kernel flashed so you can even boot.
answer is...
get into recovery, flash YOUR CARRIER kernel, you should boot up with no problem
your welcome
Click to expand...
Click to collapse
I got my phone booting properly again. I re-rooted. I installed TMO KTweaker. I can still reboot. I took another nandroid. I will try flashing omega + ktweaker again this time without formating via TWRP which apparently casused my problem.

Usually when you have restore problems, its either a MD5 mismatch, or corrupt micro SD card. You don't have to wipe when restoring, TWRP does it automatically when you restore.

I got Omega v7 working with the TMO KTweaker on my rogers i337m. Thank you all!

everything works perfect now thanks!!

good deal

Can't get passed boot logo..

This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.

Try flashing a different compatible kernel.

ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.

Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app

Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr

ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/

Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app

I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!

Glad it's working out for you.

If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?

Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.