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!
Related
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
I'd like to remove the trinity Kernel for JellyBean. I enjoy it's overclock but I hate it when my phone just randomly reboots. Is there a way to remove it. I have created a backup before I flashed it, but I'd like to remove it without having to restore to that backup.
Thanks
flash your rom without wiping, then flash gapps
ej8989 said:
flash your rom without wiping, then flash gapps
Click to expand...
Click to collapse
I should have mentioned, I'm running stock. No custom rom installed
Just flash a different custom kernel or the stock kernel. If you want a different custom kernel, and you want something stockish, you wan try SimpleKernel or thalamus kernel. As for the stock, I think you can find a flashable zip somewhere here in the NS forum.
Sorry if this has already been asked before. If you already have a custom ROM with stock kernel, and now you want to install a custom kernel, would you just boot into custom recovery then flash it on top of the existing ROM just like flashing Gapps? or do you have to wipe the ROM first, flash the kernel then ROM after that? Here's another question. Custom ROMs come with their own kernels, would my custom kernel get overwritten when I upgrade my ROM to a newer version (for example from cm10.1-20130226 to cm10.1-20130309?
k20- said:
Sorry if this has already been asked before. If you already have a custom ROM with stock kernel, and now you want to install a custom kernel, would you just boot into custom recovery then flash it on top of the existing ROM just like flashing Gapps? or do you have to wipe the ROM first, flash the kernel then ROM after that? Here's another question. Custom ROMs come with their own kernels, would my custom kernel get overwritten when I upgrade my ROM to a newer version (for example from cm10.1-20130226 to cm10.1-20130309?
Click to expand...
Click to collapse
Correct just copy the kernel to your sdcard clear cache in recovery and flash away.
I tried your ROM and rebooted twice and still looking good. Hope it'll still survive after the 3rd reboot. However, I notice some delay before the first ring back, probably due to weak signal in my area. I'll try more at different locations in the next few days to see how it goes. I really appreciate your contribution and all coders with TeamChopsticks who have nailed down the root cause of audio loss in the cm10.1 nightlies for skyrocket.
I'm having problem with Carbon ROM. My video doesn't playback I only see purple screen. However taking pictures is fine but both the qualities are low. I already set to HD. I flashed AOKP from toyes and REVOLT they had no problems with the video.
sent from Skyrocket
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
Sorry if this is a dumb question, but it's not something I've tried before so I don't want to waste my time or hose something.
Basically, I'm trying to troubleshoot an issue and I want to know if it's my ROM or also happens w/ stock. I currently have the TWRP bootloader installed and Resurrection Remix (5.8.5). If I do a full ROM backup in TWRP, can I flash a stock-based ROM to test, then use TWRP to flash RR back?
Yep you can, just make sure you tick everything in the backup, and save it externally. Some flash methods might wipe the default TWRP backup location.
The bootloader and modem aren't included in the TWRP backup, but that'll only really matter if you're going between different android versions i.e. the nougat bootloader does not play nice with marshmallow. But it still runs.
Thanks. I do back up (from TWRP) to the external SD card so I've already got that covered.
So RR 5.8.5 is Android 7.1.2. If I download an Android 7.0 stock from from sammobile.com then I should be good, yes?
I believe those need to be flashed via ODIN and can't be flashed from TWRP, correct? Will flashing this ROM from ODIN obliterate TWRP or anything? Or should I be ok to boot recovery and restore RR back later?
if u flash stock,then twrp will be gone and u will return to ur stock recovery. Then if u want to restore ur old backup then u should root ur phone like it was from the beginning and install twrp manually and all.... anyway stock or stock based roms are better than aosp. Since the camera is much better than aosp.?
amalantony said:
if u flash stock,then twrp will be gone and u will return to ur stock recovery. Then if u want to restore ur old backup then u should root ur phone like it was from the beginning and install twrp manually and all.... anyway stock or stock based roms are better than aosp. Since the camera is much better than aosp.
Click to expand...
Click to collapse
Hmm does this also apply to a stock-based custom ROM? That might be sufficient for my testing and I'd rather simplify things for myself.
All the stock-based ROMs I've seen so far appear to just be for the 930F but I assume there must be at least one out there that'd work with the 930W8