Database Users

[Q] Flashing gets stuck at Cyanogen boot screen, Still able to recover.

Hey folks. I'm trying to flash Cyanogenmod to my Nexus 7 running 4.2.1. I am rooted and unlocked. I downloaded the nightly 10.1 as well as the stable 10.0 along with Gapps. Flashing both with Clockworkmod recovery gets me stuck in a bootloop with both options, forcing me to restore to my backup.
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup. I'm wondering if I should restore to factory on my current first? Am I missing any steps in this process? I'd like to be able to just tap and install if possible. I had bad experiences with flashing when I had my Galaxy Captivate.
I appreciate any help with this. I have gone through several forums and threads, but none seem to be device or situation specific so I thought I would bring up this specific situation. Thanks for any help.

JavaMac said:
This is my first time flashing a rom on this device, but I didn't wipe it or anything. Just flashed from my current setup..
Click to expand...
Click to collapse
You left out the "how you flashed" part. If you were using something such as ROM Manager, it may have wiped for you. But typically, for manual flashing from the recovery you need to do a "factory reset" procedure prior to installing a new rom. (A wipe which erases everything in /data except what is /data/media)
I've used a CM10.1 nightly and sequentially flashing the gapps, no troubles. Perhaps different versions though, the devil is always in the details.

I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.

JavaMac said:
I flashed using Clockwork Recovery, both manually and from the app itself. Neither provided a solution.
Click to expand...
Click to collapse
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?

JavaMac said:
I'd also like to point out that I'm confused about why a factory reset would help this situation. If the new install is just writing over the boot, why should it matter?
Click to expand...
Click to collapse
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD

Pirateghost said:
It doesn't just write over the boot.
/data is where all your downloaded apps, settings, and databases are...
Do a factory reset in cwm and cm will boot. It's that simple
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Success! TY.

[Q] doing something wrong?

Ok I clearly must be doing something wrong when it comes to flashing ROMs as the only I used to be able to install them was through Odin on my old gs2 and so far have been unable to install one via recovery on my new s4.
I follow the instructions exactly but yet find my self either bootloop(rarely) or most of the time stuck at the screen with white text of "Samsung Galaxys4 gt-i9505" on screen.
I have waited up to 30 mins on this screen as I have read first boot can take some time but 30mins should be enough?
Eventually I have to flash stock via odin to have my phone back working.
Loosely step by step this has been my process.
1)flash a recovery with odin(whichever recovery rom author recommends)
2)boot into recovery
3)full wipe
4)install zip from ext card
5)select rom
6)wait till installed it then asked me to install root, have tried both install and not install root
7)phone reboots, stuck on Samsung Galaxys4 gt-i9505 screen.
This is the same with omega,foxhound and wanamlite, clearly I am missing something here for it not to install correctly.
If it matters I am on t-mobile UK.
I have tried rooting the stock rom first before installing anything still no difference.
Thanks for reading

sometimes mine gets stuck on that screen as well after flashing something... i just hold the power button to restart the phone and then generally it boots up fine...
also I'm assuming you have an i9505?
Sent from my GT-I9505 using Tapatalk 4 Beta

Yes i9505, I have tried long holding power button but just goes back to that screen. Just finding it quite frustrating now it must be something simple I'm missing.

igrieve said:
Ok I clearly must be doing something wrong when it comes to flashing ROMs as the only I used to be able to install them was through Odin on my old gs2 and so far have been unable to install one via recovery on my new s4.
I follow the instructions exactly but yet find my self either bootloop(rarely) or most of the time stuck at the screen with white text of "Samsung Galaxys4 gt-i9505" on screen.
I have waited up to 30 mins on this screen as I have read first boot can take some time but 30mins should be enough?
Eventually I have to flash stock via odin to have my phone back working.
Loosely step by step this has been my process.
1)flash a recovery with odin(whichever recovery rom author recommends)
2)boot into recovery
3)full wipe
4)install zip from ext card
5)select rom
6)wait till installed it then asked me to install root, have tried both install and not install root
7)phone reboots, stuck on Samsung Galaxys4 gt-i9505 screen.
This is the same with omega,foxhound and wanamlite, clearly I am missing something here for it not to install correctly.
If it matters I am on t-mobile UK.
I have tried rooting the stock rom first before installing anything still no difference.
Thanks for reading
Click to expand...
Click to collapse
After flashing the ROm from recovery did u wipe cache & dalvik from recovery and reboot ?
If not pls try once and see it should work

123hiten said:
After flashing the ROm from recovery did u wipe cache & dalvik from recovery and reboot ?
If not pls try once and see it should work
Click to expand...
Click to collapse
just tried for omega and foxhound and no difference just going to try the last one now.

just download a pre-rooted stock, flash via odin, then flash a recovery via odin, wipe everything, format /system and then install a custon first boot takes around 3 minutes...

Have now managed to get wanamlite up and running using the wipe cache & dalvik after installing rom, I am still none the wiser as to why the other two wouldn't install.

igrieve said:
Have now managed to get wanamlite up and running using the wipe cache & dalvik after installing rom, I am still none the wiser as to why the other two wouldn't install.
Click to expand...
Click to collapse
It should work my friend give it a try again and which recovery are you using? Name
Sent from my GT-I9500 using xda premium

Maybe your base rom wasen't the same as the rom you tried to flash?
Sent from my GT-I9505 using xda premium

My friend has the exact same issue on his i9505 using twrp, he tried to flash various ROMs but not getting past boot screen, fortunately his back up worked but still no luck in getting a ROM to flash...very odd
Edit: he is running a 3 network supplied phone if that make any difference
Sent from my Nexus 4 using xda premium

I have exactly the same!
Formatted, factory reset, wipe cache/dalvik, stock firmware using Odin, Nothing is working so far..
$%^$%
Now trying to instal FoxHound 0.5.

Well still having problems lol no idea why but I can only install two ROMS but I am happy with the one I'm currently using but your always curious to see what the others are like.

If you guys are using twrp as your recovery and you format internal sd this will happen. It is a know issue with that recovery. It messes with the partition and you need to flash a different recovery. You may need to Odin back to stock to get the partition right and go from there. Hope this helps.
Sent from my GT-I9505 using xda app-developers app

Im currentl;y using philz_touch recovery, I have been having to go back to odin and flash stock rom just to get the phone running again after trying these roms. I havent tried any roms from the original android development forum so might see if I get any joy with them, I know it must be something silly I'm missing

It happens if the base ROM you are currently on isn't the same or similar to the ROM you're trying to flash. Maybe changelog of the ROM you're trying to flash is a lot higher tan your current ROM and things get mixed up. I have always had success by performing a factory reset after flashing the ROM.
I had the exact same problem going from MDE firmware to Omega V7. After flashing Omega again I did a factory reset and it was sweet
Sent from my GT-I9505 using XDA Premium HD app

Need help - freezes and restarts

I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?

Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.

jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.

RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.

PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.

Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.

jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)

jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.

jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"

jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?

jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?

jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.

jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.

jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.

jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692

jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.

jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....

Sg4 splash screen

Ok I'm having a lot of problem with my new samsung sg4. It came with the MDL firmware. I followed qbking direction on how to root with cf auto root. I have done the root and I installed TWRP for my recovery. I tried flashing sacs and also triforce and I get the sg4 splash screen nothing else. Though when I flash sacs of triforce inside TWRP it come up and says that supersu is not installed and I need to install it to have root but superuser is installed. The only the one to fix it is to use odin and go back to stock.MDL firmware. Any suggestions. Thanks

kronik420 said:
Ok I'm having a lot of problem with my new samsung sg4. It came with the MDL firmware. I followed qbking direction on how to root with cf auto root. I have done the root and I installed TWRP for my recovery. I tried flashing sacs and also triforce and I get the sg4 splash screen nothing else. Though when I flash sacs of triforce inside TWRP it come up and says that supersu is not installed and I need to install it to have root but superuser is installed. The only the one to fix it is to use odin and go back to stock.MDL firmware. Any suggestions. Thanks
Click to expand...
Click to collapse
Sounds like you were bricked at one point, if you were stuck at the S4 boot. Play it safe. Do a full factory reset & use odin. Also, use the new stock image (MF9: http://samsung-updates.com/device/?id=SPH-L720 or http://www.sammobile.com/firmwares/1/?model=SPH-L720&pcode=0#firmware). When you do, make sure it's set to PDA. Always clear cache & wipe calvik (Advanced > Wipe Dalvik) before installing a new rom

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I would flash the selected rom again, flash a verizon kernel, wipe dalvik and cache, it will boot.
thanks

TheAxman said:
I would flash the selected rom again, flash a verizon kernel, wipe dalvik and cache, it will boot.
thanks
Click to expand...
Click to collapse
Dont flash a verizon kernel, it will totally brick your phone, flash a sprint kernel.
Sent from my SPH-L720 using xda app-developers app

P1NK13P13 said:
Sounds like you were bricked at one point, if you were stuck at the S4 boot. Play it safe. Do a full factory reset & use odin. Also, use the new stock image (MF9: http://samsung-updates.com/device/?id=SPH-L720 or http://www.sammobile.com/firmwares/1/?model=SPH-L720&pcode=0#firmware). When you do, make sure it's set to PDA. Always clear cache & wipe calvik (Advanced > Wipe Dalvik) before installing a new rom
Click to expand...
Click to collapse
used odin, but still stuck at splash screen. what can i do now?

s.lee1993 said:
used odin, but still stuck at splash screen. what can i do now?
Click to expand...
Click to collapse
Go to recovery, format data, wipe dalvik cache and cache reboot
Sent from my SPH-L720 using xda app-developers app

ROMANTiC KiD said:
Dont flash a verizon kernel, it will totally brick your phone, flash a sprint kernel.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
From what i know a Verizon kernel would not brick. Back on gs2 and gs3 sprint users would flash Verizon kernels.
One thing that would be funky was screen rotation was inverted.
Sent from my SPH-L720 using Tapatalk 4

daniel4653 said:
From what i know a Verizon kernel would not brick. Back on gs2 and gs3 sprint users would flash Verizon kernels.
One thing that would be funky was screen rotation was inverted.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
No, I'm pretty sure they only flashed Verizon PRL's so they could force roam. I've never seen any talk of flashing Verizon kernels in gs2 forum.
Sent from my SPH-D710 using Tapatalk 2

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.