I've been using matrix for awhile and while its good I want to try others but I heard its not safe to flash custom kernels to other custom kernels without going back to stock. Is this true? Also how long does it take to see how well a kernels performs? I flashed franco yesterday and im thinking to flash faux or trinity tomorrow
Cjshino said:
I've been using matrix for awhile and while its good I want to try others but I heard its not safe to flash custom kernels to other custom kernels without going back to stock. Is this true? Also how long does it take to see how well a kernels performs? I flashed franco yesterday and im thinking to flash faux or trinity tomorrow
Click to expand...
Click to collapse
the only kernel that is recommended to flash your rom and new kernel after is the franco kernel. it includes its own tweaked ramdisk(franco tweaks). so to be safe, its best to flash your current rom(and gapps) with the new kernel, dont wipe anything(dirty flash), so that the new kernel can grab your roms ramdisk instead of francos. its safe to flash over francos, but his tweaks might mess with the new kernel tweaks. its safe to flash any other nexus 4 kernel on top of each other.
Yep. Flashing faux on top of Franco screwed my phone up. I flashed a ROM before flashing faux but I didn't boot it up first I think that was my problem. Anyways it was stuck in boot loop forever and going into recovery to delete data and system only froze the phone (first time that ever happened to me). Then after hard resetting my recovery was just stuck on twrp screen when booting up. Kept messing around for 2 hours couldn't get **** to work and tried to adb pull some files off my phone because all I could think of at that time was fast boot flashing stock image. However USB debugging was off and it wouldn't even boot into android so that was a fail. Ended up losing all my data still bummed about that but moral is be safe than sorry flash that reset and boot into android then back to recovery to flash the newer kernel
Sent from my Nexus 4 using xda app-developers app
otariq said:
Yep. Flashing faux on top of Franco screwed my phone up. I flashed a ROM before flashing faux but I didn't boot it up first I think that was my problem. Anyways it was stuck in boot loop forever and going into recovery to delete data and system only froze the phone (first time that ever happened to me). Then after hard resetting my recovery was just stuck on twrp screen when booting up. Kept messing around for 2 hours couldn't get **** to work and tried to adb pull some files off my phone because all I could think of at that time was fast boot flashing stock image. However USB debugging was off and it wouldn't even boot into android so that was a fail. Ended up losing all my data still bummed about that but moral is be safe than sorry flash that reset and boot into android then back to recovery to flash the newer kernel
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
damn thats sucks. so after im done with Franco I should flash stock kernel and stock rom before going over to a new kernel? Also how do I flash by rom? Im using stock rom btw
Well in faux's thread there's a link for a "reset kernel" which is basically a stock kernel flash that then boot up into android and then go back to recovery and flash whatever kernel. Usually this is only needed after using Franco kernel. Faux and Franco are the only kernels I've ever used. I like Franco more seems smoother to me with good battery.
Flashing the ROM wouldn't be necessary if you flash the reset kernel or vice versa. Roms have their own kernel so it would overwrite Franco's (just boot up the ROM once after flashing it which was my mistake) but since you're on stock I would just download that kernel which is ~5mb vs. 350mb rom
Sent from my Nexus 4 using xda app-developers app
otariq said:
Well in faux's thread there's a link for a "reset kernel" which is basically a stock kernel flash that then boot up into android and then go back to recovery and flash whatever kernel. Usually this is only needed after using Franco kernel. Faux and Franco are the only kernels I've ever used. I like Franco more seems smoother to me with good battery.
Flashing the ROM wouldn't be necessary if you flash the reset kernel or vice versa. Roms have their own kernel so it would overwrite Franco's (just boot up the ROM once after flashing it which was my mistake) but since you're on stock I would just download that kernel which is ~5mb vs. 350mb rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What if i go from Franco to Matr1x or Trinity do I still have to reflash stock kernel or is it only from franco to Faux?
Related
Right now I'm running aosp's oICSv43 on my Nexus S 4G and have been trying to flash the Speedy-3 kernel. I'll admit I'm not the most knowledgeable at this, but from what I've gathered, I need to boot into recovery, wipe the cache/dalvik cache, and install from zip, choosing the kernel. This does not work for me at all. The install will finish without error, but when I reboot I get stuck at the Google screen. Here's what I've tried:
Recoveries:
CWM V3
CWM V5
TWRP V2 (what I'm using now)
Kernels:
Matr1x
Speedy-3
Glados
I've even flashed the phone completely back to stock and tried everything again to no avail. I can root the phone and flash roms with no problem. The problem comes when I try to flash a kernel after.
Any suggestions?
cashel said:
Right now I'm running aosp's oICSv43 on my Nexus S 4G and have been trying to flash the Speedy-3 kernel. I'll admit I'm not the most knowledgeable at this, but from what I've gathered, I need to boot into recovery, wipe the cache/dalvik cache, and install from zip, choosing the kernel. This does not work for me at all. The install will finish without error, but when I reboot I get stuck at the Google screen. Here's what I've tried:
Recoveries:
CWM V3
CWM V5
TWRP V2 (what I'm using now)
Kernels:
Matr1x
Speedy-3
Glados
I've even flashed the phone completely back to stock and tried everything again to no avail. I can root the phone and flash roms with no problem. The problem comes when I try to flash a kernel after.
Any suggestions?
Click to expand...
Click to collapse
Dont wipe cache. Only dalvik cache and then flash the kernel.
Sent from my Nexus S using xda premium
Thanks for the tip (and quick reply!), but it doesn't seem to work . Here are the steps I'm going through:
Booting into recovery
Full factory wipe
Flashing oICSv43
Rebooting into OS to setup phone/account (even skipped this step completely with no luck)
Boot back into recovery
Wipe dalvik cache
Install Speedy-3 kernel (or the either of the other two)
Reboot -> Gets stuck at Google logo w/ lit buttons
Just to be sure here - you are flashing those kernels which you downloaded from the Nexus S 4G Development forum right? And you are 100% sure it is a NS4G?
You're doing everything by the book so I don't know what else could be going on, don't take the questions the wrong way
Harbb said:
Just to be sure here - you are flashing those kernels which you downloaded from the Nexus S 4G Development forum right? And you are 100% sure it is a NS4G?
You're doing everything by the book so I don't know what else could be going on, don't take the questions the wrong way
Click to expand...
Click to collapse
No worries . 100% positive I have a NS4G, and I'm 100% positive I downloaded the kernels via the NS4G Dev. forum. I downloaded the kernels from the following three threads to be exact:
Matr1x:
http://forum.xda-developers.com/showthread.php?t=1361478
Speedy-3:
http://forum.xda-developers.com/showthread.php?t=1420912
GlaDOS:
http://forum.xda-developers.com/showthread.php?t=1345032
I've tried both the BFS and CFS versions for each where applicable as well.
Can't think of much else to try besides an alternative ROM to test flashing kernels with. Hopefully someone else could give you a better answer though.
cashel said:
Right now I'm running aosp's oICSv43 on my Nexus S 4G and have been trying to flash the Speedy-3 kernel. I'll admit I'm not the most knowledgeable at this, but from what I've gathered, I need to boot into recovery, wipe the cache/dalvik cache, and install from zip, choosing the kernel. This does not work for me at all. The install will finish without error, but when I reboot I get stuck at the Google screen. Here's what I've tried:
Recoveries:
CWM V3
CWM V5
TWRP V2 (what I'm using now)
Kernels:
Matr1x
Speedy-3
Glados
I've even flashed the phone completely back to stock and tried everything again to no avail. I can root the phone and flash roms with no problem. The problem comes when I try to flash a kernel after.
Any suggestions?
Click to expand...
Click to collapse
Easy fix. Flash it dirty....meaning don't wipe anything. Once it boots up, reboot to recovery then wipe dalik cache and boot up.
Sent from my Nexus S 4G using xda premium
I'm an idiot, wasn't using the latest version of aosp's oICS like I thought. Wiped everything, flashed to the latest version, wiped dalvik cache, flashed speedy-3 kernel and all is well . Thanks guys.
cashel said:
I'm an idiot, wasn't using the latest version of aosp's oICS like I thought. Wiped everything, flashed to the latest version, wiped dalvik cache, flashed speedy-3 kernel and all is well . Thanks guys.
Click to expand...
Click to collapse
So you were flashing 3.0 kernels on a rom built for 2.6. Glad you got it working.
Sent from my Nexus S 4G using xda premium
Is there a way to force Galaxy Y into Recovery mode when we cannot boot into Recovery mode by using the three button combo? I am asking this because everytime we flash a custom kernel that has a permanent custom recovery mode, we need to always flash stock rom via odin to change to some other custom rom or kernel. For example, Merruk kernel has its own custom recovery mode. Now if we want to change back to some other kernel or custom rom that have its own kernel after flashing merruk kernel, we always need to first flash stock rom via odin. If we directly flash another kernel or custom rom that has its own kernel, we got stuck at Galaxy Y screen and after that we won't be able to boot into recovery mode again. Thanks in advance.
Sent from my GT-S5360 using xda premium
I have tried it many times in savies kernel...
By trying that boot recovery option...
But no luck...however in some kernels like kuro kernel...
It is possible as they have temporary cwm...
**rooting is new for me...and i am noob to root...**
Anyone having a solution to this problem?
Sent from my GT-S5360 using xda premium
I don't have any problem... I used merruk 2.0 which has permanent CWM.. Then i flashed Kuro kernel which have stock recovery got no problem...
solution- if u use any kernel which have cwm then flash a kernel which have stock recovery like kuro.
Then flash your rom......
Btw i never got this tupe of problem.
thadoukuki said:
Anyone having a solution to this problem?
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
First of all... you can flash any rom or kernel when you are on kernel with inbuilt cwm...
Otherwise what's the point of making a inbuilt cwm?
Just make sure you have mounted system in mount options before flashing any rom or kernel...
I'm sure it will definitely get installed... make sure you mount system before flash...
--------------------------------------------------------------------------
nitubhaskar-->Deadly.
★Nothing is True... Everything is Permitted★
Muffins..? Yuumy!
No problems for me to switch back and forth between mt and other kernels - in fact i do it often and i don't remember the last time i used odin
My nexus is rooted using the nexus toolkit and I'm running 4.2.1 rooted with motley kernal. How would I go about updating to the latest software whilst keeping the root and upgrading the kernel?
If you use custom recovery with a backup then easy - restore boot (kernel) and system, then install ota update zip file.
http://forum.xda-developers.com/showthread.php?t=2148337
u can use this 4.2.2 factory image, flash via CWM or TWRP. Your data will be preserved.:good:
Kernel
BelzIgoh said:
http://forum.xda-developers.com/showthread.php?t=2148337
u can use this 4.2.2 factory image, flash via CWM or TWRP. Your data will be preserved.:good:
Click to expand...
Click to collapse
Will the kernel still be compatible with the newest update.
Jordydaman said:
Will the kernel still be compatible with the newest update.
Click to expand...
Click to collapse
Flashing a ROM over the top of your existing ROM will replace both the /system partition and also the boot partition.
Meaning - your Motley Kernel will get blown away and replaced with whatever boot image the ROM dev provided (stock kernel and ramdisk, I suppose). But you can certainly just re-install the Moltey kernel anytime thereafter.
If you have market apps that try to perform random kernel tweaks as soon as the ROM boots, you might be in for some surprises up to and including bootloops. The safest thing to do - if they have an "apply at boot" toggle, is to turn that off before you commence flashing.
As always, take a full nandroid backup before you begin. You can always go back that way.
Hi, if you're reading this, thanks for taking the time to help me. I want to flash Cyanogen 10 on to my rooted Nexus 7. Its currently running the stock JB 4.2.2 ROM. A few days ago I flashed the motley kernel (build #249 for Jellybean 4.2.2) to OC the CPU to 1.6 Ghz using ROM Manager to flash and Trickster MOD to OC. I understand how to flash Cyanogen 10 to the Nexus 7, but is this safe? I've heard some users report that they get a boot loop when trying to flash Cyanogen 10 on top of a modified kernel. Has anyone here experienced a problem doing this?
The kernel lives in the boot partition and that is formatted when the new rom installs and it flashes its own boot.img into place. No worries. Just make sure you do a factory reset and wipe system prior to flashing cm10.
Okay. So I should boot into recovery, then do a factory reset. After that, unlock bootloader again and re-root. Then install Rom Manager again, and flash CM 10, then flash motley kernel?
Sent from my Nexus 7 using XDA Premium HD app
pindleton said:
Okay. So I should boot into recovery, then do a factory reset. After that, unlock bootloader again and re-root. Then install Rom Manager again, and flash CM 10, then flash motley kernel?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
A recovery factory reset does not relock or unroot your devices. Pretty much every rom out there will be pre rooted. So what you are going to do is download your rom, boot to recovery, perform a backup, factory reset, format system, then flash rom and gapps package and kernel, then reboot.
Oh awesome. Thanks for the help!!
Sent from my Nexus 7 using XDA Premium HD app
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.