Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
nothing, it should work fine
Sent from my Nexus 5 using XDA Free mobile app
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
As jd1639 said... Yes, flashing the stock boot.img should be just fine.
Probably easier though, you can also just dirty flash the ROM that your currently running on your N5 without wiping anything and then while still in recovery, just flash the custom kernel that you want to switch too and done.
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
As far as I know, just flashing the stock boot.img is usually fine, but if you take a look at franco's thread, the process to uninstall includes flashing system.img as well, since a couple of system files are modified. I don't think elementalx does though, so what you suggested will work ok.
simonarturo said:
As far as I know, just flashing the stock boot.img is usually fine, but if you take a look at franco's thread, the process to uninstall includes flashing system.img as well, since a couple of system files are modified. I don't think elementalx does though, so what you suggested will work ok.
Click to expand...
Click to collapse
Very true... Some kernels do modify the system and that's why I find it easier to just dirty flash the ROM that I'm currently using, since it wipes the system partition and then you don't run into issues.
Thank you.
So I'll better dirty flash to avoid unnecessary problems with a new kernel.
All user data should be save with a dirty flash, am I right?
maroc84 said:
Thank you.
So I'll better dirty flash to avoid unnecessary problems with a new kernel.
All user data should be save with a dirty flash, am I right?
Click to expand...
Click to collapse
Yeap.. Nothing will be erased.
What about if I am on stock? Should flashing the flash-base.sh (from factory image) have the same effect like a dirty flash of a custom recovery with a zip of a custom Rom? So all use data be save.
maroc84 said:
What about if I am on stock? Should flashing the flash-base.sh (from factory image) have the same effect like a dirty flash of a custom recovery with a zip of a custom Rom? So all use data be save.
Click to expand...
Click to collapse
If you mean the flash-all.bat, it will erase all data! Just flash the /system and /boot images and then flash the custom kernel..
Or, you can dirty flash the stock 4.4.4 rom and then flash the custom kernel.
Edit: no. I mean the batch as I named it. It's not flash-all. But I think it only flashes radio and bootloader.
Side fact: *.bat = Windows DOS and *.sh = Linux shell
maroc84 said:
Edit: no. I mean the batch as I named it. It's not flash-all. But I think it only flashes radio and bootloader.
Side fact: *.bat = Windows DOS and *.sh = Linux shell
Click to expand...
Click to collapse
No need to flash radio as well. Flashing boot.img and system.img will do the job is you're on stock and you're guaranteed to not lose your data. I think that will only happen if you flash userdata.img
Just flash the rooted stock zip ROM.
Sent from my Nexus 5 using Tapatalk
Related
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy
ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.
ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.
downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.
ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.
Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?
strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.
DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.
well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0
So I have installed franco Kernel on final lollipop on my Nexus 5 and I want to flash another Kernel but it says I have to do a clean flash with stock kernel. I didnt find a .zip stock kernel for stock LRX210 and I want to know how to go back to kernel. I can flash .img but if its going to erase my data I would prefer a .zip to flash in recovery, thanks!
Flash stock ROM.zip
i need flashable stock kernel zip too..
amir7777 said:
So I have installed franco Kernel on final lollipop on my Nexus 5 and I want to flash another Kernel but it says I have to do a clean flash with stock kernel. I didnt find a .zip stock kernel for stock LRX210 and I want to know how to go back to kernel. I can flash .img but if its going to erase my data I would prefer a .zip to flash in recovery, thanks!
Click to expand...
Click to collapse
get wugfresh's root toolkit , specify what OS you are running, got advaced utilities on the bottom left click launch, then under retore stock kernel click stock kernel .. and voila
get wugfreshes rootkit here http://www.wugfresh.com/nrt/
rootSU said:
Flash stock ROM.zip
Click to expand...
Click to collapse
but thats gonna wipe all his data yeah ?
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Preston2291 said:
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Click to expand...
Click to collapse
Most kernels r flashed in recovery.
Tigerstown said:
Most kernels r flashed in recovery.
Click to expand...
Click to collapse
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Preston2291 said:
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Click to expand...
Click to collapse
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Tigerstown said:
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Click to expand...
Click to collapse
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick because I can't write to the system with a new rom
Preston2291 said:
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick
Click to expand...
Click to collapse
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Tigerstown said:
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Click to expand...
Click to collapse
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Preston2291 said:
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Click to expand...
Click to collapse
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Tigerstown said:
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Click to expand...
Click to collapse
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Preston2291 said:
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Click to expand...
Click to collapse
You should be able to just flash pretty much any sense based rom and have what you want. Write protection is removed in all of them, or, at least in all the ones I've tried.
That said, if you've already flashed a kernel that has write protection removed, you should be able to check it by just copying any file to the system folder. A text file, picture, anything. Then reboot the phone and check to see if the file you copied to the system folder is still there. If so, you're good to go. If not, write protection is still being enforced.
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!