Related
AnyKernel zips will only replace the kernel in your boot.img.
To define a boot.img:
Kernel(zImage) + ramdisk(root file system + init scripts) = boot.img
Where AnyKernel came from:
While searching for different kernels for my Motorola Droid I stumbled on a great idea implemented by Koush. Basically it will split the boot.img from recovery while your phone is running then replace the kernel and make a new boot.img and flash it along with the correct modules for the kernel.
I figured I would implement it on the CDMA Hero and it worked out.
This will work on any rooted rom with a custom recovery running Sense UI including the stock rom.
------------------------------------------------------------------------------------------------------------------------------------------------------------
Here are the undervolted and overclocked kernels for Sense ROMS
These kernels are built from the HTC heroc-2.6.29-bc0d2ccf source with toasts overclock patch modified by darchstar/Decad3nce to include undervolt.
The git repo for this is @ http://github.com/zenulator/htc-heroc-2.6.29-bc0d2cff
The GPL license can be read @ http://www.gnu.org/licenses/gpl.html
ZenKernel-HTC-08122010 no perf lock
It has perf lock disabled to allow full overclocking with out the need use setcpu to disable perf lock. The clock speeds will stay at what ever the target rom uses unless you running a rom with no overclock built in. If so it will scale from 19mhz to 768mhz.
Download
ZenKernel-HTC-08122010 perf lock
Same as above but with perf lock enabled. It will run at stock values on any sense Rom until you use setcpu. To overclock it you will need to set setcpu to autodetect and then disable perf lock inside setcpu.
Download
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
StockVoltage Overclocked Kernel:
This kernel is built from the same source as the rest except the voltages were changed to stock values. It will max out at 691 and the governor is set to performance.
Download
Setcpu is free for xda memebers and can be found here:
http://forum.xda-developers.com/showpost.php?p=3638937&postcount=1
Instructions:
Download the update and copy it to the root of your sdcard.
Reboot into recovery.
Nandroid (just in case you want to go back)
Flash the update
Reboot
Check Settings > About phone > Software information > Kernel version
_____________________________________________________________________________
If you wish to modify this with another kernel just extract the update and replace the zImage in the kernel directory with the one you want and replace the corresponding modules. Then rezip and resign and flash. It will work on any 2.1 sense rom regardless of boot.img.
Damn good work zenulator I am downloading it now and will test thoroughly tomorrow and see how it go's.
Thanks for the hard work.
Works great, using it with your beta ROM. Lock screen lag is gone
I got used to it so I barely noticed it... but now it seems a lot faster
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
thatguythatdid said:
I know you just started this and it says for sense. But I gotta ask is there anyway that this will work with froyo? I'm not a fan of overclock roms because of the lag when you push the menu key till when you screen is actually ready to go. And this gives me hope
of having a kernel that doesn't do that
Click to expand...
Click to collapse
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
zenulator said:
Yes it will work for froyo if you modify it and put in the correct zImage (kernel). It won't work with the update I posted since it's made for Sense roms and uses HTC's Synaptics driver which isn't compatible with AOSP 2.2 Froyo/Cyanogenmod.
If you want a AOSP kernel with no overclock and no ability to overclock at all then I can do that but not for a couple days. If you ask darch he might be able to do it quicker since he already has everything set up and most likely only two files will need to be changed before a compile.
Click to expand...
Click to collapse
Thanks for the reply I'm gonna give the new kernel a chance to see how it does
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Thanks for this zen works great
this is undervolted correct? does this really help the battery life?
c00ller said:
Excuse my ignorance but how is this different from Standard DarchKernel vUV2 691 MHz found here http://forum.xda-developers.com/showthread.php?t=705074 ?
That's what I'm using and it already says
Kernel version
2.6.29-cyanogenmod
[email protected] #6
Click to expand...
Click to collapse
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Decad3nce said:
Uhh. I'm going to give a brief explanation.
AnyKernel is a tool created by Koushik Dutta found here on github.
The beauty of it is that it can flash/add a kernel to any boot.img regardless of ramdisk. It literally does the unpacking of the boot.img, extracting of the ramdisk, deletion of the original kernel and repacking of the boot.img together with the kernel of your choice.
The difference with this is probably changes in base address/cmd line and possible how it's extracted(haven't looked at it). Very awesome tool nonetheless, and is a lot more efficient that going through the process of coupling the kernel with each specific ramdisk before releasing a boot.img.
That's how it's different from your quoted "kernel".
Click to expand...
Click to collapse
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Now with the HTC Synaptics driver included, the swipe action once the screen is on is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Well just an update but it has been very smooth so far, 8 hours as still smooth . Great job. Screen rotation and scroll seem quicker also .
Sent from my HERO200 using XDA App
Papa Smurf151 said:
I understand the explanation but have to ask what rge different change. I know this will just change the kernal from the boot imiage which is great and it has the HTC synaptic drivers in the kernal but that kernal with the HTC drivers has already been implemented into the latest boot.imgs. its a cool concept and would make it easier to change just the kernal for a one shot stop when a newer kernal comes out but as of right now that's the same kernal most of the sense based roms have already implemented into them at this time. If im wrong I'm sorry.
Click to expand...
Click to collapse
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
zer0vette said:
Now with the HTC Synaptics driver included, the swipe action once the screen is one is no longer lagged. However, I notice that there is still lag from the time the power button is hit to the time the screen comes on as compared to stock where there is almost no lag. Is there some other driver or something that causes this?
Click to expand...
Click to collapse
I've always wondered about this delay with the OC kernels as well.
Sent from my HERO200 using XDA App
zenulator said:
This will just make it a lot easier instead of having multiple boot.img for different roms like in the other thread. Plus this will work on other roms not supported in the other thread. I know the kernel brings nothing new but for instance if someone wants to overclock my old ZenHero they can now do that. Or if someone just rooted their phone and installed RA or some other recovery this is all they need to over clock and still keep their stock system.
So when someone makes a new kernel they can use this and have it work on any Rom instead of just a specific Rom.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Papa Smurf151 said:
Makes sense. I thought about it actually and it will make things easier. I used it earlier today on a boot.img I flashed first that had the ramdisk mod for battery tweak but I think was missing the HTC synaptic driver. Lag is all gone and it worked great.
Click to expand...
Click to collapse
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
zenulator said:
It's definitely going to make it easier for me at least since I plan on doing a bunch of new kernels based on toasts and darchstars work. As well as the official HTC kernel with toasts overclock.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Now this is what I'm talking about
I was looking for something like this. Darchstar is one helluva dev, but it seems like the only kernels in use these days are Toasts (base) then modded toast kerenels by Darchstar (which are great as well). But I'd like to see a couple of tweaks fixed in the most recent Kernel #6 such as the typo that Uroshiol mentioned that is located in the actual zImage in the DArchstar uv2 kernel 710 with freememkiller
Nice nice work ya'llz and great stuff Zen... makes the addition of new kernels a breeeeze
Wait...so there is an under volted, oc kernel available for nfinite's .6 stock rom that eliminates the menu button wake lag?? i dont like the lag but deal with it. although if there is a way to eliminate the lag, please share!!
Zen, you're definitely an unsung hero (no pun intended I swear) around these parts and I for one definitely appreciate your work. Cheers!
I was just wondering that if I am going to update my kernel is it necessary to re-install the rom or do I just install the zip with clockwork and away i go? I've searched the forum and couldn't find anything regarding it, I would appreciate the help! Thanks.
you can just use CWM to installed the kernels without installing the rom but there might be some compatibility issues, so check before doing it.
Ok because the reason I'm asking is because I have SupeAosp with the Trinity kernel but I'm thinking on either upgrading for Trinity 12 to 14 or trying out James Bond Kernel and I thought that there might be some prep work involved.
xmatrix13 said:
Ok because the reason I'm asking is because I have SupeAosp with the Trinity kernel but I'm thinking on either upgrading for Trinity 12 to 14 or trying out James Bond Kernel and I thought that there might be some prep work involved.
Click to expand...
Click to collapse
just flash the newer kernel on top. be sure its compatable with the rom. if you do have issues, just reflash the rom(that will bring you back to the roms "stock" kernel).
In this case you can test out different kernels but make sure you have the trinity kernel file in the root folder in case which ever kernel you do flash doesn't work out.
In such a case you would just boot into CWM and re-flash the morfic kernel.
Sent from my Nexus S using XDA Premium App
Thanks for the insight, I look forward to testing out many kernels!
hey everyone,
does anybody know if these two are compatible to work together or is it something where it's either or? i've been looking through the threads but haven't manage to find any answer for it. i appreciate any answers.
THANKS!
All reports say there is no reason for Pauls patch on custom roms.
oh alright. thanks for responding
jcbofkc said:
All reports say there is no reason for Pauls patch on custom roms.
Click to expand...
Click to collapse
Faux kernel is not a ROM. He is using it on that ROM - so the question was not specifically answered.
I had Paul's patch on stock kernel when I first flashed faux kernel, but don't know for sure if it is needed (ie - is the patch of the kernel or something else?).
gaww said:
Faux kernel is not a ROM. He is using it on that ROM - so the question was not specifically answered.
I had Paul's patch on stock kernel when I first flashed faux kernel, but don't know for sure if it is needed (ie - is the patch of the kernel or something else?).
Click to expand...
Click to collapse
Let me be more specific in case the OP did not get it. No, you do not need Pauls patch for custom kernels or roms. It is strictly designed for the stock rom to fix a mistake by LG.
jcbofkc said:
Let me be more specific in case the OP did not get it. No, you do not need Pauls patch for custom kernels or roms. It is strictly designed for the stock rom to fix a mistake by LG.
Click to expand...
Click to collapse
The patch was an updated services.jar messed up by lg in the stock ROM. Do kernels also include a services.jar?
If so, then no need when kernels are flashed either, as it would be overwritten. This would be the clarification he (and I) was looking for. If not ??
Note - when I look in a whole ROM zip file - I can find it. Cannot when I open a kernel zip file.
gaww said:
Faux kernel is not a ROM. He is using it on that ROM
Click to expand...
Click to collapse
What does that mean.so is the kernel baked into the rom: when we install faux's rom, we automatically get the kernel .
Sent from my LG-P999 using XDA App
ashman3000 said:
What does that mean.so is the kernel baked into the rom: when we install faux's rom, we automatically get the kernel .
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes - if you flash faux ROM - you get his kernel as part of it.
But the OP was about using faux (with) stock kernel on the stock froyo ROM. The stock ROM had some messed-up up stuff by LG in the (I have read) services.jar file in the stock ROM.
He asked if he could (should) use the paul patch with this combination. Since the services.jar is (I also believe) not changed by the kernel only, it appears that it should be flashed on top of the stock ROM once (unless you wipe and it is then gone), and then flash the kernel (I did that).
For ALL CM ROMs - different services.jar - no problem. But for EB and other stock based froyp ROM's - I am not sure. If the Dev's built paul's fix into the services.jar -then they are OK. If not, they might be able to use the fix also.
Would REALLY like to hear from one of the Dev's on this. Been all over the forums, and with respect to the kernel only and other than stock froyo ROM's - it has not been clearly spelled out.
its for STOCK roms not custom kernels dont matter in this pauls patch fixes a problem with lg stock rom all custom roms should have this fixed
So, if you think this is a stupid question, please closed this MOD
I was wondering, if there any ICS kernel. Have searched and found nothing.....
Using MIUI rom v4 by Erikmm
doc_v15 said:
So, if you think this is a stupid question, please closed this MOD
I was wondering, if there any ICS kernel. Have searched and found nothing.....
Using MIUI rom v4 by Erikmm
Click to expand...
Click to collapse
Nope, all of our ICS roms use the same kernel
Nope, all of our ICS roms use the same kernel
Click to expand...
Click to collapse
Well then...Next questions, how can we get additional CPU governor like SmartassV2 on our ICS kernel?
doc_v15 said:
How can we get additional CPU governor like SmartassV2 on our ICS kernel?
Click to expand...
Click to collapse
Patch the kernel and compile from source.
No, I'm not joking.
I believe the kernel devs are working on getting something a lot better than a governor on a 2.6 kernel, but I'll leave that to them to reveal at the proper time.
brandonc0526 said:
Nope, all of our ICS roms use the same kernel
Click to expand...
Click to collapse
jeffsf said:
Patch the kernel and compile from source.
No, I'm not joking.
I believe the kernel devs are working on getting something a lot better than a governor on a 2.6 kernel, but I'll leave that to them to reveal at the proper time.
Click to expand...
Click to collapse
I wish I could compiled it
Hopefully the kernel devs are not givin up
Since this is a GB kernel, it should be simple, assuming you know how to recompile a kernel from source, just to grab the OC etc routines out of one of AntonX's or bhundven's kernels and then just stick them in and recompile. Since everyone is using the same kernel so far this would only need to be done once. This erzatz ICS is slow and sure could use OC, more governors etc.
I added smartassv2 last night, but want to get a "clean" build off the AOKP tree and have a few days running it before I release it to the wilds.
Standard statement: "OMG, I'm seeing incredible battery life, smooth as butter, WiFi signal strength is better, TVout works,..."
nazcalito said:
Since this is a GB kernel, it should be simple, assuming you know how to recompile a kernel from source, just to grab the OC etc routines out of one of AntonX's or bhundven's kernels and then just stick them in and recompile. Since everyone is using the same kernel so far this would only need to be done once. This erzatz ICS is slow and sure could use OC, more governors etc.
Click to expand...
Click to collapse
Well...i dont know a single thing about kernel and its related
Sent from my Nexus S using XDA App
Try my latest GummyMutt build. I injected lightning zap into it. You can also try using just the kernel and see how it works...
jeffsf said:
I added smartassv2 last night, but want to get a "clean" build off the AOKP tree and have a few days running it before I release it to the wilds.
Standard statement: "OMG, I'm seeing incredible battery life, smooth as butter, WiFi signal strength is better, TVout works,..."
Click to expand...
Click to collapse
Oh man!!! cant wait for yours!
Thanks!
Sent from my Nexus S using XDA App
thomas.raines said:
Try my latest GummyMutt build. I injected lightning zap into it. You can also try using just the kernel and see how it works...
Click to expand...
Click to collapse
Thomas - any chance you could provide quick instructions on how to extract and flash your kernel?
Sent from my SGH-T959V using xda app-developers app
Im downloading the rom Ill poke around and see if I can get it pulled out.
Manumission said:
Thomas - any chance you could provide quick instructions on how to extract and flash your kernel?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Download his rom unzip it grab the boot.img and flash it with heimdall. Then grab the wifi module(bcm4329 I think is the name lol) and push it to the same place u got it from (/system/lib/modules/)
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
DISCLAIMER: I'm not responsible neither is thomasraines or xda if you brick your device you are doing this on your own free will. The only thing you can say is how awesome thomas is for creating this and how awesome I am for uploading and writing directions. Any blame will result in me pointing and laughing uncontrollably.
Files removed thomsasraines posted the kernel in the dev section it can be found there. Please visit his thread and follow what he posted so you can get the full effect ok? If not tough I aint re upping the files .
Click the statement above for direct route to the kernel thread.
Unzip the bcm4329.ko, xda wouldnt let me upload a .ko file .
Put the bcm4329.ko file on your sdcard. Then using something like root explorer copy it to /system/lib/modules folder.
I suggest renaming the old one to bcm4329.ko.bak just in case.
Using heimdall you can flash the kernel using the following command.
Code:
heimdall flash --kernel boot.img
This is from terminal in ubuntu or cmd in windows. Make sure you are running the commands from the folder you put the boot.img in.
Once the phone reboots pull the battery and put it back in. Boot into recovery and run fix permissions. Then reboot.
so what will this do again? Is this for a kernel different than the kj6 one?
If you are unsure of what it is for then dont attempt the steps.
Do some more reading.
Edit nm
Sent from my SGH-T959V using xda premium
doc_v15 said:
So, if you think this is a stupid question, please closed this MOD
I was wondering, if there any ICS kernel. Have searched and found nothing.....
Using MIUI rom v4 by Erikmm
Click to expand...
Click to collapse
I have multiple kernels in progress. The common problem on all of them seems to be sd/mmc.
Patience will bring enlightenment.
Sent from my SAMSUNG-SGH-I717 using xda premium
bhundven said:
I have multiple kernels in progress. The common problem on all of them seems to be sd/mmc.
Patience will bring enlightenment.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yeah man! Will be waiting, patiently
eollie said:
DISCLAIMER: I'm not responsible neither is thomasraines or xda if you brick your device you are doing this on your own free will. The only thing you can say is how awesome thomas is for creating this and how awesome I am for uploading and writing directions. Any blame will result in me pointing and laughing uncontrollably.
Unzip the bcm4329.ko, xda wouldnt let me upload a .ko file .
Put the bcm4329.ko file on your sdcard. Then using something like root explorer copy it to /system/lib/modules folder.
I suggest renaming the old one to bcm4329.ko.bak just in case.
Using heimdall you can flash the kernel using the following command.
Code:
heimdall flash --kernel boot.img
This is from terminal in ubuntu or cmd in windows. Make sure you are running the commands from the folder you put the boot.img in.
Once the phone reboots pull the battery and put it back in. Boot into recovery and run fix permissions. Then reboot.
Click to expand...
Click to collapse
Dude, can you make it CWM flashable??
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
alexm231 said:
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
Click to expand...
Click to collapse
1st option
Primokorn said:
1st option
Click to expand...
Click to collapse
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
alexm231 said:
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
Click to expand...
Click to collapse
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
Great. Thanks so much for the detailed answer, it clears up my confusion!
Now off to try Franco's kernel
Alex
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
I actually have an additional question: do we need the same process even if we're talking about the newer version of the same kernel? Like going from an older version of Franco's to the newest
Alex
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
kufikugel said:
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
alexm231 said:
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
Click to expand...
Click to collapse
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
rootSU said:
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
Click to expand...
Click to collapse
Yes, I consider your guideline (on your signature) very good advice indeed.
Thanks again to all
Alex
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
I know I had to do that when I flashed elemental. Otherwise some apps won't open. But now I want to find out was the the full correct way? Or was it the lazy way
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
Flash the stock boot.img and system.img and then flash the kernel you want to change to..
I have also tried just flashing the stock boot.img and then the custom kernel.. Sometimes it works, sometimes it doesn't. So I would reccomend flashing both! (boot and system)
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
simms22 said:
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
Click to expand...
Click to collapse
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
akmsr said:
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
Click to expand...
Click to collapse
yes. they arent located in either of those locations, so my advice applies, and is the only reason why i posted this. they are located in /etc/init.d/. you either dont have that location (best option), have it but an empty folder, or have an init.d folder with files in it. if there are files there, delete them.
Flashing a system.img will overwrite init.d scripts. /etc is a symbolic link to /system/etc so when you replace /system/etc with whatever is in a ROM.zip or a system.img, these changes apply to /etc too.
If you look in any ROM.zip or kernel.zip, they all flash their scripts to /system/etc/init.d
Sent from my Nexus 5 using Tapatalk