A few questions as this is all new to me.
Do all ROMS require you to flash a new kernal?
Do you flash a kernal the same way as you flash a radio? (PD98IMG File and Hboot?)
I appreciate the input...
ROMS should and typically will come with the recommended kernel, however, some kernels do work that aren't the packaged one. Always be careful when flashing a new one (backup, backup, backup!) because sometime they don't always get along with the ROM you have running.
Also, most of them should be flashable .zips that can be ran through CWM.
At least in my experience with various kernels
Hope this helped!
Kernels are included with every rom I have ever tried, and if you want to use a different kernel than the one in the rom, you have to make sure that is compatible. A good rule of thumb is if it a sense based rom (custom user interface that comes stock on the inspire) you have to use a sense based kernel. If it is a ASOP rom (Android Open Source Project, like Cyanogenmod 7, or MUIU) you must use a ASOP kernel. They will specify in the OP. And I have never heard of flashing them through HBOOT, or FASTBOOT. In my experience it is always through CWM recovery, and you flash them just as you would a rom, theme, or anything else. Move the .zip file to the root of your SD, choose install zip from sd card, scroll down to choose zip from sdcard, then choose the file. When it is done hit back and then reboot. Easy Peezy.
Tmullins23 said:
A few questions as this is all new to me.
Do all ROMS require you to flash a new kernal?
Do you flash a kernal the same way as you flash a radio? (PD98IMG File and Hboot?)
I appreciate the input...
Click to expand...
Click to collapse
Read.
Reread.
Search.
Research.
Try.
Retry.
Then ask.
kernal == kernel
Most users will flash kernels through clockwork like a rom. I flash them through fastboot, you can fastboot flash zimage(or boot), or fastboot boot zimage , which lets you boot the kernel before actually writing it, fastboot flashing requires eng s-off, which you probably don't have or need
Related
So, I am going to do a lot more research prior to rooting, but I had a couple of general questions that I was wondering about, before I begin the steps leading up to rooting.
1) I presume the easiest way for me to root my Thunderbolt is the Revolutionary Root? This will take be through rooting and installing the CW recovery that I need, correct?
2) Right after I root, If I want to install roms/kernels? than I can just get Rom Manager from the android market?
3) Once I install Rom Manager, can I just flash a rom that is compatible with my Thunderbolt? Can I just flash a kernel that is compatible with the Rom?
I suppose where I get a lil lost is the flashing compatibility part. What kernels work with what roms, what roms I can flash... I have read a number of articles, so I suppose what I'm asking is...
Will the process more or less be: Revolutionary Root, Install Rom Manager from market, flash a rom (just the most popular one). Is the Kernel flashing piece important? Do I need to flash a different kernel? Is it easy to tell in Rom Manager which kernel/rom I can use?
Yes use revolutionary to root and install custom recovery (cwr). You can use ROM manager to download custom roms if you want, only roms for your device will show up. Or you can download custom roms from forums, this is the method I prefer.
Just use kernel that comes with the Rom for the time being some developers include a custom kernel and others make modifications to the HTC kernel itself. Kernels are seperated in development section having to do with sense and aosp that is the first way to seperate them. Second would be leak the kernel was based on such as imo test 3.8 was based on newest leak so it works for just about if not all newest sense roms. When in doubt fire up a question in the Rom thread itself and ask what kernels those people are using, find a Rom like BAMF or thunderstick or synergy where the developers or support staff are very active.
Also you will need to flash a new radio right after rooting if you are still using froyo, I am using newest leak but different phone work differently. Once you install the radio VIA Hboot. Reboot phone and remove zip file from root of SD card now place your Rom image on SD card and reboot to recovery and install your new Rom.
Sent from my Thunderbolt using XDA App
This is good info.. thanks.
Well, I am upgraded to Gingerbread as of VZW's last update and still unrooted and stock.
So, if I were to root (using revolutionary) and install Rom Manager... could I just install something like Cyanogenmod or BAMF right through Rom Manager?
What do you mean by kernel that comes with the Rom? The kernel that is listed to use with the Rom? Or do you mean if I flash BAMF or something popular, just leave whatever kernel I have as is?
Bwangster12 said:
This is good info.. thanks.
Well, I am upgraded to Gingerbread as of VZW's last update and still unrooted and stock.
So, if I were to root (using revolutionary) and install Rom Manager... could I just install something like Cyanogenmod or BAMF right through Rom Manager?
What do you mean by kernel that comes with the Rom? The kernel that is listed to use with the Rom? Or do you mean if I flash BAMF or something popular, just leave whatever kernel I have as is?
Click to expand...
Click to collapse
When you flash a rom it flashes the kernel too with whatever one the devs packed with it.
Sent from my HTC ThunderBolt using Tapatalk
Okay, clear enough.
So, for someone like myself, just use revolutionary root, install rom manager and play around a lil with flashing roms using rom manager for awhile. I understand that I can install roms from my SD card, but it sounds like at least initially installing roms right from rom manager would be the simplest. I can also not worry about installing a different kernel during this "honeymoon" phase. Just pick the latest version of whatever Rom I want and flash the rom?
After you root you need to install superuser so CWM can function. I have read that some people flash their CWM via hboot after s-off and then go right to recovery to flash the root gaining RUU, then enjoy your root.
Do not flash ROMs right from CWM reboot to recovery clear data/cache and under advanced davlik cache and then install Rom from install from SD and choose zip file and I always store mine in downloads since I download all my roms right to my phone and download md5 checker from market and always check the md5 if it does not match don't think its a mistake redownload and try again.
Sent from my Thunderbolt using XDA App
Agreed, it is better to install the ROM through recovery instead of installing through ROM manager as sometimes it doesn't work right.
Don't forget to use thank you for all you great answers.
Sent from my Thunderbolt using XDA App
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
Yes there is a sense kernel and one for non-sense roms (aosp)
Usually the dev will have a kernel link posted on their page
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
redpoint73 said:
If you are hboot 1.14 or higher, and S-on, to be perfectly safe you should extract the boot.img for the ROM zip you are trying to flash, and flash it manually.
Also, be careful installing ROMs with GooManager (or similar apps, like ROM Manager). Not sure if it properly differentiates between the dual and quad core versions of the One X/XL.
Click to expand...
Click to collapse
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file. So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
If you can point me to a how-to on this, I'd appreciate it - I hate filling boards with asinine questions.
originalseven said:
I've searched up and down for this and have yet to find a solid answer, so here I am. I have an AT&T One X (Evita), unlocked, rooted and flashed. Currently running TWRP & GooManager for recovery and ROMs and I'm on Viper 3.2.6.
Initially, my choice was to flash CM10, this failed and went into boot loop. So I recovered and tried Viper. No problems....everything installed just fine. However, I'd like a more lightweight OS - Viper is a little too heavy for my tastes. I saw in GooManager yesterday a new ROM, Liquidsmooth (4.2.2) - decided to flash it and the same thing happened as with CM10 - everything went fine through install and then black.....second install attempt resulted in another bootloop.
I recovered back to Viper without issue, but I can't help but wonder why both CM10 and Liquidsmooth fail to install, but suspect I'm missing a certain boot img? Am I correct here?
(I'd post this to the specific ROM forum but don't have enough posts to submit to developer forums - apologies)
Click to expand...
Click to collapse
viper doesn't require you to flash the boot image, it does it for your.
For cm10 or liquidsmooth you need to, an easy way is using Flash GUI. its available on the market and xda. you don't need to hook up to a computer to flash boot image, makes things much easier and faster.
originalseven said:
Is it better to just boot into recovery (TWRP) and go that route, instead of having Goo flash it?
Click to expand...
Click to collapse
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
originalseven said:
I checked the page where the ROM exists but I'm not seeing a link to any specific kernel. However, I downloaded to ROM again to my desktop just now, unarchived it and now see a 'boot.img" file.
Click to expand...
Click to collapse
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
originalseven said:
So this file.....this gets placed on my sd card, I boot into TWRP and flash it?
Click to expand...
Click to collapse
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Awesome - thank you so much. Cleared that up completely.
redpoint73 said:
For flashing the actual ROM, I don't think it matters. I think Goo Manager is still using TWRP, just automating the process.
The boot.img has the kernel in it. They are usually not posted separately in ROM threads. ROMs always contain a kernel, which normally just flashes with the rest of the ROM zip. But hboot 1.14 and above (if you are S-on) prevents the kernel from being flashed in recovery (TWRP). So you need to extract it from the ROM zip manually.
Again, you can't flash boot.img from TWRP, which is the whole point. Couple methods:
1) Leave the boot.img on your PC, and flash using fastboot. See here: http://forum.xda-developers.com/showthread.php?t=1952076
2) Alternately, you can use the app "Flash Image GUI" on the Play Market. With this app, you place boot.img in the top directory of your SD card, then use the app to flash it.
Or you can S-off, and not have to mess with flashing boot.img seperately every time you flash a ROM.
Click to expand...
Click to collapse
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
originalseven said:
Ok, so I looked at this Flash Image GUI on G-Play and the OneX isn't listed as a supported device - is it simply not listed, but is actually supported? For instance, I see this in the reviews...
"I own the AT&T model of the HTC One X (the Evita with a Snapdragon 4 processor) and unfortunately I got it on the 2.20 version. This means that I need to run the "fastboot flash boot boot.img" from my computer if I want to flash a Rom or kernel. It was a pain, I just wanted to be able to download a new Rom whenever and where ever I wanted (I have a very large data cap) and flash it on the go. I can actually do that now it's worked with both AOSP and Sense based Roms, so I'm happy. Great job to the dev "
Failing that, I'll run it from terminal (im on a mac) and assume those same commands apply (but with -mac after bootloader).
Click to expand...
Click to collapse
flashimagegui is perfectly supported. got support awhile back. [APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Hello.
I currently have my pico with stock rom, with sense 3.5. and i'm tryin to flash a new rom, but every time i try to flash one from this thread ( http://forum.xda-developers.com/showthread.php?t=1754876 ) i got stuck on htc logo screen. and i cant get passed it... i've wiped everything, reflashed kernel, reflashed stock, but still cant get it to work. maybe these kernels arent for stock roms, if they're not, can you point some kernels that work on stock?
thanks in advance.
Stock rom should have stock kernel too.
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Red Devil said:
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Click to expand...
Click to collapse
where can i find those gingerbread kernels? so if they're inside the "rom.zip" is it possible to "extract" them to a flashable zip? only the kernel withouth the rom itself...?
Gingerbread kernels are in the Index of all kernels..
From the ROM.zip if you want to extract them then just extract the boot.img normally and also extract the modules from the zip .. in /system/lib..
In fastboot mode flash boot.img via :
Code:
fastboot flash boot boot.img
and
then via adb push the modules. I suggest you search a bit and find some answers yourself . Its easier that way cause these questions have been answered millions and millions of times. So use the search function
i've searched, and believe me when i say that i havnt found anything about this... all the kernels i go for, on the thread only talks about the kernel itself and not the roms compatible... and i've tried that method and got stuck on htc green logo... thanks for answering
these kernels work on stock rom:
1- cranium kernel
2- ateeq kernel
3- garuda's kernel
search them in the development thread I hope you'll find them.
i've tried all those kernels... one by one and never got passed the htc green logo... always get stuck there... i tried flashing trough fastboot and trough recovery... nothing works... any other suggetions?
try to flash ateeq rom then ateeq kernel..it works for me.
but i dont want to have ateeq rom, i want to stay with my stock rom, but change the kernel... only that. but thats for answering. i'm getting used to the idea that i cant be changed (the stock kernel).
thanks
Need urgent help
i had rooted my pico months back and was on different custom roms......now i want 2 get back to the stock rom which i have downloaded Odexed Stock ROM Flashable Zip (With Link2SD Support)(Revision 3)(http://forum.xda-developers.com/showpost.php?p=40385554&postcount=76) and i have flashed this rom 5 - 10 times and everytime i reboot after flashing the rom.....i am stuck on htc boot logo.....can u plssssss help
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
thrgk said:
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
Click to expand...
Click to collapse
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
cntryby429 said:
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
Click to expand...
Click to collapse
Thanks for all the info. So if I am on 4.4.3 and want to flash a 4.4.2 rom just flash the 4.4.2 firmware just to be safe before flashing the 4.4.2 rom?
Also where are the kernels located ? Are they carrier dependent as I didn't see any yet browsing but didn't look hard either.
So I can do flash boot through flashify and be ok? Now all roms and kernels are flashed through twrp tho right ?
EDIT: actually fastboot can flash rom and kernels so no real need for custom recovery other then for convenience?
Btw do you have a kernel recommendation for aosp, sense, ? I already saw your recommendation for sense above.
Thanks !!
Sent from my SM-N900V using XDA Free mobile app
I have a feeling that it's simply not necessary to downgrade your firmware in order to run a 4.4.2 rom but you should find a more reputable source than myself. I'm just trying to answer these easy questions to save time for the guys who really know what they're doing. Once you do start flashing things, always make sure 1) they are for your device (and carrier, unless unified for all carriers) and 2) the md5 of the downloaded file matches that provided by the hosting website or the OP.
I'm not a fan of flashing utilities simply because I've heard of instances where they don't work correctly. For example, I keep hearing how the TWRP manager app flashes TWRP to the system partition on Verizon devices and sends the phone into a sort of recovery loop. I would suggest gaining knowledge about the fastboot flash command "fastboot flash <partition name> <filename.extension>" and how to enter and flash within RUU mode.
My experience is that ROMS and kernels are easiest flashed through a custom recovery especially when the developer packages it with an Aroma installer script.
A few Sense/GPE custom kernels exist for verizon. There's MassStashed and Checkm8 (no longer maintained?) for 4.4.2 roms. Also, for 4.4.3 roms I only know of the EliteLunar kernel which isn't on XDA although you can find a few links to it in the forums if you search. Last I knew, there weren't any AOSP kernels which work with verizon but that might not be true anymore. The general HTC One m8 forum may have some kernels which aren't represented in the verizon-specific forum. Just make sure and find out if they're compatible with verizon devices. I'm pretty happy with sense so I haven't wondered off to AOSP like I usually do.
so do you recommend to use flashify or no?
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
Its the easiest way
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
I'm not saying you shouldn't use flashify, it's awfully convenient. Just make sure you're using it for the convenience and not because you don't know how to accomplish the same tasks in recovery/fastboot.
I am about to flash my nexus 5 device.
I was wondering.. if i unlock the bootloader and install a custom recovery plus create a backup.. that means ill have basicly a backup on my phone of a factory ROM and kernel right ?
So If i play around with custom roms and Kernels does that mean if I want to go back to stock kernel or/and ROM I can just recover my backup files from ,for example, CWM ?
And also if anyone here knows... how big difference can a kernel for battery life extension make ?
Then..
If I want to flash both.. Custom ROM and Kernel.. Rom comes first ? And if after that .. lets say I have flashed Cyanogenmod , and I have decided to change ROMs , Do I have to flash factory ROM ? Or I can just factory reset and Flash ir over the Cyanogenmod ?
For example.. for elementalX kernel I read this line... "You should only flash ElementalX over the kernel that came with your ROM!!!" I assume that means I do flash the ROM first... and what if I want to change Kernels later on? I re-flash the factory kernel ? And how do I do that?
For now that would be it
Thanks
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
audit13 said:
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
Click to expand...
Click to collapse
Thanks!
What advantages does TWRP has over CWM ? And also does it recover other files as well or just the system ones ?
And I guess its safer to just extract the original ROMs kernel.. Just how do i do that ?
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help: https://www.youtube.com/watch?v=rLhprnOF6-U
audit13 said:
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help:
Click to expand...
Click to collapse
Thanks!
So.. If, lets say, I flash cyanogenmod. Then Flash custom kernel. In order to change other kernel which is also custom , I should first flash the factory ROM which will have kernel on it ? And then reflash the ROM and then flash the new kernel ?
Im sorry , I also read a lot about this and somewhere on the way got really confused , haha.
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
audit13 said:
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
Click to expand...
Click to collapse
Thank you. Made things much clearer. Dirty flash means just flashing over the existing custom ROM and Kernel right?
And also.. What about if i have CM and Kernel B ... But i want to go change to ParanoidAndroid and still keep the Kernel B? This ROM would remove the Kernel and I would have to re flash ir right?
And also if I am just switching around ROMs only.. I can just flash them one over another? Perhaps a factory reset is healthy in between though.
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
audit13 said:
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
Click to expand...
Click to collapse
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
rihz said:
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
Click to expand...
Click to collapse
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
wangdaning said:
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
Click to expand...
Click to collapse
Okay, thanks!
And Happy New year to you all!