I was going to flash CM9, but while reading through the page in the general section I came across this at the bottom:
Don't expect help if...
are not running stock cm-kernel
I searched for a CM kernel and didn't find anything. Doing my search, I noticed some mentioned that the kernel is built into the flash.
A: is that correct? If so, why would the specify you need to be running a CM-Kernel (Unless CM means Clockwork Mod?)
B: If not, where can I download this kernel at?
Thanks!
stalked_r/t said:
I was going to flash CM9, but while reading through the page in the general section I came across this at the bottom:
Don't expect help if...
are not running stock cm-kernel
I searched for a CM kernel and didn't find anything. Doing my search, I noticed some mentioned that the kernel is built into the flash.
A: is that correct? If so, why would the specify you need to be running a CM-Kernel (Unless CM means Clockwork Mod?)
B: If not, where can I download this kernel at?
Thanks!
Click to expand...
Click to collapse
Because there are other kernels out there that's why. They'll only give you support if you're running the kernel that comes with the rom
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Nick281051 said:
Because there are other kernels out there that's why. They'll only give you support if you're running the kernel that comes with the rom
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Ok. so option "A" is correct then. Since I'm running Entropy's daily, by flashing the zip, it will automatically replace the kernel I'm running. They just don't want people going in behind their install and throwin in their kernel of choice. Correct?
stalked_r/t said:
Ok. so option "A" is correct then. Since I'm running Entropy's daily, by flashing the zip, it will automatically replace the kernel I'm running. They just don't want people going in behind their install and throwin in their kernel of choice. Correct?
Click to expand...
Click to collapse
No they just won't support it if someone flashes another kernel afterwards because that can create other problems that they can't troubleshoot if you aren't running their kernel. This is because the kernel might have caused said issue
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Think about what yer asking. If a ROM didn't come with a kernel built into it could it run? No. What kind of kernel would a CM (cyanogenmod) ROM come with? Ehhh? A....CM kernel perhaps? Is this not common sense?
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
Think about what yer asking. If a ROM didn't come with a kernel built into it could it run? No. What kind of kernel would a CM (cyanogenmod) ROM come with? Ehhh? A....CM kernel perhaps? Is this not common sense?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm not sure what you're saying is true. When installing UnNamed Rom, I needed to first install a kernel with CWM in it (Entropy's). I'm not sure why the install instructions for the ROM would say "Install the Kernel" unless it needed it. Would be kind of redundant don't you think?
That's why when I read the warning about running a different kernel, I wanted to make sure that there wasn't a step I was missing before installing it.
stalked_r/t said:
I'm not sure what you're saying is true. When installing UnNamed Rom, I needed to first install a kernel with CWM in it (Entropy's).
Click to expand...
Click to collapse
You're completely wrong. This only when you're rooting. UnNamed already comes with a kernel
Sent from my SGH-I777 using Tapatalk 2 Beta-5
stalked_r/t said:
I'm not sure what you're saying is true. When installing UnNamed Rom, I needed to first install a kernel with CWM in it (Entropy's). I'm not sure why the install instructions for the ROM would say "Install the Kernel" unless it needed it. Would be kind of redundant don't you think?
That's why when I read the warning about running a different kernel, I wanted to make sure that there wasn't a step I was missing before installing it.
Click to expand...
Click to collapse
Asked, discussed but don't say such "I'm not sure what you're saying is true", it is an insult. Phalanx is right and I think you maybe still confuse about the process.
Q: why would I (we) need to install custom kernel such Entropy DD before flashing custom ROM?
That question leads to another question
Q1: how do I flash custom ROM, what is the requirement?
A: In order to flash ROM, you MUST have CwMR installed
Then next question Q2: how do I get CwMR installed on my device?
That lead to the answer for the first question, you get CwMR by installing custom kernel.
Still confuse?
Now back to your discussion, yes, every ROM (I should say every firmware image) MUST contain the kernel (along with the OS).
In your first post, CM9 ROM will have CM9 kernel called "CM stock kernel"
Why don't they support anything else but their own kernel?
Put it this way, you sell me a PC, running Windows 7, I bring it home, rip it apart, install Linux on it, when I have issue, I call you and say "I bought the PC from you, I decide to install my own OS, and now something doesn't work right". Do you think you will provide me any kind of support?
Another note from your post, CM9 is ICS, make sure you get Entropy's ICS kernel called FAQUD (spelling), not his Daily Driver for GB.
votinh said:
Asked, discussed but don't say such "I'm not sure what you're saying is true", it is an insult. Phalanx is right and I think you maybe still confuse about the process.
Q: why would I (we) need to install custom kernel such Entropy DD before flashing custom ROM?
That question leads to another question
Q1: how do I flash custom ROM, what is the requirement?
A: In order to flash ROM, you MUST have CwMR installed
Then next question Q2: how do I get CwMR installed on my device?
That lead to the answer for the first question, you get CwMR by installing custom kernel.
Still confuse?
Now back to your discussion, yes, every ROM (I should say every firmware image) MUST contain the kernel (along with the OS).
In your first post, CM9 ROM will have CM9 kernel called "CM stock kernel"
Why don't they support anything else but their own kernel?
Put it this way, you sell me a PC, running Windows 7, I bring it home, rip it apart, install Linux on it, when I have issue, I call you and say "I bought the PC from you, I decide to install my own OS, and now something doesn't work right". Do you think you will provide me any kind of support?
Another note from your post, CM9 is ICS, make sure you get Entropy's ICS kernel called FAQUD (spelling), not his Daily Driver for GB.
Click to expand...
Click to collapse
Thanks. I wasn't insulting anyone. I was saying that I don't know, but I didn't think it was true. Not saying YOU'RE WRONG!
Related
Hey guys, I'm not gonna ask the dreaded question "Which Kernal is best?", but I am currently rooted and want to overclock to 1.5, but besides that, what else should I be looking for in a kernal?
What about modems (or is that embedded in the kernal)?
We only have 2 options, Entropy or Siyah and they do not include a modem.
Check the dev section for kernels & modems.
butikofer08 said:
Hey guys, I'm not gonna ask the dreaded question "Which Kernal is best?", but I am currently rooted and want to overclock to 1.5, but besides that, what else should I be looking for in a kernal?
What about modems (or is that embedded in the kernal)?
Click to expand...
Click to collapse
Both kernels we have offer oc abilities.
Personally I would look at stability and battery life but that is just me. Try both and see which suits your needs.
Modems are not associated with kernel and depend on your area. Whichever works the best where you are.
We have two choices here and both are incredibly stable and allow overclocking. You can't go wrong. Basically the biggest difference as far as I can see is the recovery that comes with it which is almost entirely preference.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
So if I find a ROM I like but want to experiment with the other available Kernal, is it as simple as flashing my ROM first, then once booted up go into Odin and flash the other kernal i want to experiment with?
Or is the kernal that comes with a ROM the one your stuck with?
butikofer08 said:
So if I find a ROM I like but want to experiment with the other available Kernal, is it as simple as flashing my ROM first, then once booted up go into Odin and flash the other kernal i want to experiment with?
Or is the kernal that comes with a ROM the one your stuck with?
Click to expand...
Click to collapse
Just use CWM to flash the zips provided or Mobile Odin if you prefer it that way.
No need to use a computer to change the Kernel.
LiLChris06 said:
Just use CWM to flash the zips provided or Mobile Odin if you prefer it that way.
No need to use a computer to change the Kernel.
Click to expand...
Click to collapse
Thanks for the quick response chris,
I guess what I'm asking is if I have a rom with the Syiah kernal, is it possible to keep that same ROM but swap kernals, sorry, I just wasn't clear on what your answer meant.
I'm guessing your saying it is indeed possible and just flash the .zip for a different Kernal on top of an already installed ROM.
Sorry, I'm tired...
Changing the Kernel on 2.3.4 & 2.3.6 roms will not break anything.
For CM7, CM9, MIUI etc you have to stick with what is included or see what works with it.
AntwanL said:
We have two choices here and both are incredibly stable and allow overclocking. You can't go wrong. Basically the biggest difference as far as I can see is the recovery that comes with it which is almost entirely preference.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
For example, latest Siyah with touch recovery. Awesome for flashaholics.
Your talking of version .14 I assume, if so, doesn't it say in .13 description that .13 would be the last for Gingerbread?
Obviously it works if your using it, so i'm gonna download now...
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
aspen1135 said:
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
Click to expand...
Click to collapse
I would use Heimdall to flash if possable also i would flash Siyah's new kernel also check the md5 to verify the rom you are trying to flash sometimes during download things get goofed after that make sure you wipe everything data/cache/dalvik and then try flashing your rom
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
This link explains how to edit build prop to get rid of status errors.
http://forum.xda-developers.com/showpost.php?p=24266658&postcount=471
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Phalanx7621 said:
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
Click to expand...
Click to collapse
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
aspen1135 said:
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
Click to expand...
Click to collapse
Cause I'm trying right now. Wish me luck I'll report after I'm done with excessive flashing
RatusNatus said:
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
MotoMudder77 said:
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
Click to expand...
Click to collapse
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
gregsarg said:
Unsupported CWM image ...
Your CWM or TWRP is not compatible with your rom...
Flash the CWM from the "everything " thread ...
Then try again ....it seems this version is the most stable ....IMHO
Edit :
It's non touch ...but it's rock solid ...g
Click to expand...
Click to collapse
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
RatusNatus said:
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
Click to expand...
Click to collapse
This problem has been occurring for a long time now. And has nothing to do with your version of cwm. It has to do with the script IN THE ROM YOU ARE FLASHING. If it has the script in the rom to check what phone model u have, and it detects something other than what it should, it basically says "hey! This guy doesn't have our phone! Stopppp!" And won't let u flash. Status 7 error. To fix this, either manually remove the script that checks for this in the rom yer flashing, modify the build.prop in the rom yer currently ON to reflect the model number of the rom u want to flash, or flash another rom that already has this script checking removed to get your build.prop to reflect the new model number u want it to show. Either way none of it has to do with your version of cwm.
Sent from my SGH-I777 using Tapatalk 2
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...and thanks for unresume my resume.
Sent from my SGH-I777 using xda app-developers app
RatusNatus said:
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
You had a different issue then. most likely just a corrupt recovery. as there are NO problems flashing from one version of CWM to the next.
The common status 7 error, is caused by the updater.script searching the build.prop. as stated a million times in almost every thread.
Hi, I'm sure there is a thread, but I didn't find one using google or the forum search. I want to make sure that I don't screw the pooch with my phone, I rooted using Busybox and I have the superuser app now installed, but I didn't change the kernel at all. I was wondering if I can still load custom roms on the phone now that I have rooted it, even though the stock kernel is on my phone.
Also, it seems as though many of the posts I've found refer to using a windows machine, I'm using ubuntu, and I only have one other machine that runs something other than that, and its osx. If I wanted to flash the kernel, is there a good post somewhere that describes how to do this in linux, preferably a debian based linux?
I have a Galaxy S2, i777 (which I guess the entire board is dedicated to, so that should be obvious). I'm posting because I want to be super careful and not brick my phone. I'll make a nand backup before doing anything, but now that I've rooted, can I just install any custom rom that works with the i777, or am I limited to certain ones because I have the stock kernel. Does the galaxy phone custom rom (I think thats what its called) work with the stock kernel on the i777?
Thanks for any answers anyone has, and if I just get a post reference, that's fine, I just couldn't find it after hours of sifting.
First. Read the stickies.
Second. After reading the stickies you will find that you can't flash any ROM until you flash a kernel with cwm cooked in.
Third. After you have read the above you should know exactly what tools you can use to get there.
Sent from my Galaxy Nexus
To add to what Pirate said, or rather further elaborate , our phones have recovery in the kernel. So with ours you don't flash recovery separately. PM me if u have questions and I'll answer them there rather than in the thread.
Phalanx7621 said:
To add to what Pirate said, or rather further elaborate , our phones have recovery in the kernel. So with ours you don't flash recovery separately. PM me if u have questions and I'll answer them there rather than in the thread.
Click to expand...
Click to collapse
Thank you! I will look for the stickies, and I may take you up on that PM.
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes
So I've tried a bunch of different ROMs (CleanROM, Alliance, Beans, CM, OMNI, "Stock", probably more), but I've never really understood kernels. It seems some custom ROMs have a kernel built in (or several to choose from via Aroma), while others do not. Right now I'm running AOKP (4.4.2) with the kernel from OMNI (3.0.64-OMNI-g5f47648), presumably because that was the previous ROM I flashed with a kernel. I'm not too concerned with customization, more with stability.
I've been having a few minor bugs and crashes and I'd like to try perhaps the stock kernel to see if that might help, but I have some questions:
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
2) Are there multiple versions of kernels that correspond with the Android version of the ROM?
3) What's the best/easiest way to flash a kernel, presumably through the custom recovery like a ROM?
4) Where can I find the stock kernel? I found this thread (http://forum.xda-developers.com/showthread.php?t=2610870) with the stock MJ9 kernel, but going back to my first two questions I'm not sure if it would work with my current ROM.
Thanks ahead of time for any insight anyone can provide.
michaellasalle said:
So I've tried a bunch of different ROMs (CleanROM, Alliance, Beans, CM, OMNI, "Stock", probably more), but I've never really understood kernels. It seems some custom ROMs have a kernel built in (or several to choose from via Aroma), while others do not. Right now I'm running AOKP (4.4.2) with the kernel from OMNI (3.0.64-OMNI-g5f47648), presumably because that was the previous ROM I flashed with a kernel. I'm not too concerned with customization, more with stability.
I've been having a few minor bugs and crashes and I'd like to try perhaps the stock kernel to see if that might help, but I have some questions:
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
2) Are there multiple versions of kernels that correspond with the Android version of the ROM?
3) What's the best/easiest way to flash a kernel, presumably through the custom recovery like a ROM?
4) Where can I find the stock kernel? I found this thread (http://forum.xda-developers.com/showthread.php?t=2610870) with the stock MJ9 kernel, but going back to my first two questions I'm not sure if it would work with my current ROM.
Thanks ahead of time for any insight anyone can provide.
Click to expand...
Click to collapse
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
Yes. TW and AOSP kernels are different.. The only one, that I believe, that can be used with both is Devil kernel for Dual Booting
2) Are there multiple versions of kernels that correspond with the Android version of the ROM?
Yes. Usually every version of android that gets updated.. the kernel does as well
3) What's the best/easiest way to flash a kernel, presumably through the custom recovery like a ROM?
Yes you can flash kernels through a custom recovery. Most of the time they are included with the Rom that you flash. A lot of the custom ones out have flashable zip for you to flash them through a recovery.
4) Where can I find the stock kernel? I found this thread (http://forum.xda-developers.com/showthread.php?t=2610870) with the stock MJ9 kernel, but going back to my first two questions I'm not sure if it would work with my current ROM.
No this will NOT work with a AOSP rom.. The kernel will be specific to that ROM and every other TW 4.3 ROM, but NOT AOSP
lacoursiere18 said:
1) Does it matter when flashing a kernel whether the ROM is TW or AOSP?
Yes. TW and AOSP kernels are different.. The only one, that I believe, that can be used with both is Devil kernel for Dual Booting
Click to expand...
Click to collapse
Thanks for the explanations, that helps tremendously. I'm confused now, however, because several people on the AOKP thread (http://forum.xda-developers.com/showthread.php?t=2453566) claim to be on "stock kernel". Is there a stock kernel for AOSP that I'm missing?
michaellasalle said:
Thanks for the explanations, that helps tremendously. I'm confused now, however, because several people on the AOKP thread (http://forum.xda-developers.com/showthread.php?t=2453566) claim to be on "stock kernel". Is there a stock kernel for AOSP that I'm missing?
Click to expand...
Click to collapse
Yea the one that flashes with AOKP.. loll
lacoursiere18 said:
Yea the one that flashes with AOKP.. loll
Click to expand...
Click to collapse
Well that's what I thought, but why then would I be using an OMNI kernel (3.0.64-OMNI-g5f47648) when I have flashed the last three AOKP nightly ROMs that have come out? Or am I missing something here?
michaellasalle said:
Well that's what I thought, but why then would I be using an OMNI kernel (3.0.64-OMNI-g5f47648) when I have flashed the last three AOKP nightly ROMs that have come out? Or am I missing something here?
Click to expand...
Click to collapse
Maybe he uses that kernel.. AOSP kernels, I believe are pretty similar.. I may be wrong, I am by NO MEANS a kernel guru..I would open you zip of your ROM (AOKP) and take a peak.. if there is a boot.img than it flashes a kernel.. and if your says OMNI then thats the kernel the dev has used..
Stock
If I'm on the stock rom and want to go back to the original kernel can I just restore the boot img in recovery?
nealman said:
If I'm on the stock rom and want to go back to the original kernel can I just restore the boot img in recovery?
Click to expand...
Click to collapse
Should be able to if you back it up previously.. but make sure it is same rom.. TouchWiz for TouchWiz.. AOSP for AOSP
lacoursiere18 said:
Should be able to if you back it up previously.. but make sure it is same rom.. TouchWiz for TouchWiz.. AOSP for AOSP
Click to expand...
Click to collapse
Thank you sir. It worked just fine.
I have a noob question, I'm currently using n3bula 3.9 custom rom and it's been running fine for a while. I noticed that users chose the agni kernel whereas I chose the stock one. So my question is, is it possible to flash just the kernel from recovery without losing my data? I've spent so much time and effort customizing my phone, therefore, I just want to change the kernel. Any help will be appreciated. Thanks.
yazalsaidi said:
I have a noob question, I'm currently using n3bula 3.9 custom rom and it's been running fine for a while. I noticed that users chose the agni kernel whereas I chose the stock one. So my question is, is it possible to flash just the kernel from recovery without losing my data? I've spent so much time and effort customizing my phone, therefore, I just want to change the kernel. Any help will be appreciated. Thanks.
Click to expand...
Click to collapse
I would think that as long as it doesn't break anything you should be fine. Probably do a backup first if you're worried about it.
Thanks for the response Michael, however, that was the response I was dreading! I'm actually worried I'll lose my WhatsApp and Viber accounts because even if I backed up my data, I'd still have to register my old WhatsApp and Viber numbers all over again which I don't have anymore.. ??