Kernel Wiping script - Nexus 10 General
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
FredC94 said:
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
Click to expand...
Click to collapse
Necessary? No. I have switched kernels without using the script for the n10. (It is around somewhere on here, in the Apps section I think) But it does FEEL better when you do.
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
But if its the same kernel (updated) then flash without wiping anything because they will use the same ram disk (if they use one anyway).
iKarido said:
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
Click to expand...
Click to collapse
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
---------- Post added at 07:56 AM ---------- Previous post was at 07:44 AM ----------
Memp2Atl85 said:
Do I simply flash the zip file in clockwork mod or what? Currently using Franco and want to give Trinity a try
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Straight from the Trinity Ten Thread.
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had.
Click to expand...
Click to collapse
I know... Thats what I had just said.
iKarido said:
So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Click to expand...
Click to collapse
In my experience bootloop problems from kernel incompatibility with flashing over each other is pretty rare. I actually used to use a combo on Franco's ramdisk with the glados kernel on my phone and it worked perfectly fine. Even Morfic (the maker of Trinity kernel) said you can flash his kernel on top of Franco's and it will give you a sort of hybrid of them both. See here:
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
The governors and such arent part of the ramdisk, thats why. It would be nice to be able to load up the specific governors you want in any kernel, but sadly thats not possible. Those are part of the actual kernel itself and the ramdisk stuff is usually performance tweaks and mods to the system.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
FredC94 said:
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
Click to expand...
Click to collapse
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
iKarido said:
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
Click to expand...
Click to collapse
I am not worried. I have never bricked because I know what I am doing. The lucky part was sarcasm.
EniGmA1987 said:
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
Click to expand...
Click to collapse
That's clear, thanks a lot :good:
Another thing I just thought of is you can make a Nandroid backup of just the boot image as soon as you flash a ROM, give it a name of whatever ROM you are on "-kernel" and then you can restore that boot image whenever you want to restore back to your stock kernel + ramdisk. Alternatively, you can save a backup of your kernel in Trickster MOD and restore it that way at a later point. But both of these methods first require that you still be running your stock kernel and ramdisk that came with the ROM you are on. If you already flashed something else, you will have to re-flash the ROM again to get back to the stock files first
You could just grab the kernel from the rom and throw it into a flashable zip if you don't have a backup, instead of flashing the entire ROM again.
Related
[Q] ROM with netarchy kernel, OCed, and optimized?
I know this is a little indulgent but, does anyone know of a fast (optimized) rom with netarchy kernel and OC built in? I am very busy so if anyone knows the answer that would be great. If not, no problem, i'll look when I have free time. TIA
flash kush roms in teamwin recovery, without reboot flash, flash netarchys kernel. thats what i'm using.
2fastkuztoms said: flash kush roms in teamwin recovery, without reboot flash, flash netarchys kernel. thats what i'm using. Click to expand... Click to collapse Seems like netarchy's allows OC in every ROM. THat's awesome
I am using it on SupraRom with netarchy kernal...Love it http://forum.xda-developers.com/showthread.php?t=1194137
[Q] How kernel change works on different roms ?
I've been doing this whole "reading" thing about flashing and all that, but some confusion is still there. I have rooted my newly got SGS2 (i9100, UK). Now what ? I'm looking at Darky's rom, but there are two files to flash separately: kernel (darkcore1.7) and ROM itself. 1. I was just wondering what is kernel in this situation ? Can i keep my current kernel, which was flashed by superoneclick(2.1.1) or do i absolutely need to flash darkcore ? 2. Same question applies to any other rom out there - can i use different kernel to the rom i may want to flash ? A lot of them come in sets (rom+kernel) 3. Another question - if i mess up kernel flash somehow, does that kill "download mode" of the phone (voldn+pwr)? I have SGS1 flashed just another day, due to it being "expendable" now that i have SGS2, so jumped in and flashed it following instructions, but without solid understanding. Either stuff gets too complicated or i'm getting too old for this **** (I do have a background of messing with PCs, videogame consoles (ps1 era to ps3/360), winmo6 phones, gadgetry in general...engineer at heart )
You can use any kernel with any ROM. And no I don't think your Download Mode will be gone if you mess up a Kernel. Kernel don't come in sets. You can choose your favorite there. See Dev section for more details. Regards.
Correction: SuperCore, not darkcore... Can i use cwm app (v2.0)to flash any kernels ? Or does it have to be odin ?
sliex said: Correction: SuperCore, not darkcore... Can i use cwm app (v2.0)to flash any kernels ? Or does it have to be odin ? Click to expand... Click to collapse Rom>>That depends upon the instructions as always in the rom you choose for a custom rom . Kernel is flashed via Odin Via CWM app or via CWM recovery . Kernel is the core of the system between hardware and operating . jje
Ok, so saying that, What stock Kernel can I use for Cyanogenmod7 ROM? I was using "XWKE7" previously. The ZIP file that i downloaded actually replaced my kernel with its own. I'm asking this as I wanna use Tegrak overclock which is only compatible with stock kernels.
Rjmcgauley said: Ok, so saying that, What stock Kernel can I use for Cyanogenmod7 ROM? I was using "XWKE7" previously. The ZIP file that i downloaded actually replaced my kernel with its own. I'm asking this as I wanna use Tegrak overclock which is only compatible with stock kernels. Click to expand... Click to collapse Stock kernels will not work with cyanogenmod. There are no overclockable kernels available for it yet. Sent from my GT-I9100M
Kernel stock cm7
Flashed 1. 3 faux kernel but I want to go back to stock kernel for cm7 do i have to restore or do i flash the stock GB kernel from att? I don't know wat under bolting really does that's why I'm going back. I'm just don't know which faux kernel to flash from that thread thanks Sent from the phone I have sex with
twayneo said: Flashed 1. 3 faux kernel but I want to go back to stock kernel for cm7 do i have to restore or do i flash the stock GB kernel from att? I don't know wat under bolting really does that's why I'm going back. I'm just don't know which faux kernel to flash from that thread thanks Sent from the phone I have sex with Click to expand... Click to collapse If you want the stock CM7 kernel then just reflash the Ba2tF zip. I'm sure there's a way to extract it, but if you're not sure about undervolting I doubt that's something you want to try. Faux used to have a 'stock' CM7 kernel for download, but I'm assuming with 3 different betas (and nightlies and weeklies) he removed the link to avoid people downloading something that wouldn't match the CM7 beta version they were on.
This one goes out to the Experts :)
Hi. I have managed to put RR 3.03 ROM into my SGII At first I read all pages I could here about rooting. And found a page that let me root without using Odin. I went to recovery on my phone. Put CWM.zip and SU-busybox.zip on my Sdcard. Installed them both. Then put RR 3.03 ROM on SDcard I installed and chose Default. Installation seemed ok , but after clearing cache and all that . Fixing permissions. The phone rebooted and screen went black. Waited over ten minutes. So I tried again with custom this time and chose CM kernel.. This didnt work either. But when I chose Dream kernel I made it work. What have I done wrong or not ? Phone is running with RR 3.03 And I love the ROM. Phone is workin 100 % But what are they Kernels ? I noticed CWMod updated from 5.5.0 something to ver. 6. and something, by itself I started with an ICS 4.03 XWLPG And now I have 4.1.1 XXLPS Please fill me in on these kernels, what to do. Pros and Cons for choosing SIYAH , CM and DREAM . What do they do different and so on. If someone will bother. Rgrds MrCaligula
Well you can google about the kernel part but for sammy phones the recovery is part of the kernel that is why when you flashed the rom with a kernel the recovery version increased. I personally recommend Siyah kernel (in the original development forum) or Dorimanx kernel (in the development forum)
-Grift- said: Well you can google about the kernel part but for sammy phones the recovery is part of the kernel that is why when you flashed the rom with a kernel the recovery version increased. I personally recommend Siyah kernel (in the original development forum) or Dorimanx kernel (in the development forum) Click to expand... Click to collapse Ok, any clue why my RR 3.03 didnt install properly with SIYAH kernel ? I guess that one was default in that ROM. Screen just stayed black for ages. I described how I did it in first post
mrcaligula said: I noticed CWMod updated from 5.5.0 something to ver. 6. and something, by itself Click to expand... Click to collapse Some ROM zips like CyanogenMod come with a recovery (zImage). So if you install such a ROM via recovery, it will replace your current recovery with what is embedded in the ROM installation zip file. mrcaligula said: But what are they Kernels ? Click to expand... Click to collapse For different kernels, they support various features, for example, ROOT (Samsung kernels don't support root access by default) Overclocking for performance gain(changing max frequency of CPU above Samsung specified values) Underclocking for battery saving (changing min frequency of CPU below Samsung specified values) Undervolting for battery saving (allowing to change voltages associated with each frequency value of phone) Any visual mods (for UI customization - like theming, changing boot animations etc) Changing country code of your phone so that you can access some apps/features that are only available in certain countries/regions. And many more.
Thanks for "flashing" me that info
mrcaligula said: Thanks for "flashing" me that info Click to expand... Click to collapse U could have asked that in the rom thread but u decided to spam the general section. "Flash" this info without a wipe.
[Q] Changing ROM changes recovery as well?
Hi! I am new to this phone an I am confused about one thing. With my previous phone, I installed any ROM that I wanted, and the cwm recovery would be the same, and will not be affected at all. But, I changed my ROM to PACman ROM and I noticed that the cwm recovery version changed as well. So, I have three questions: - Firstly, How does this work? I opened up a ROM zip package, but I only found the regular android files, but I didn't find any recovery.img. So, how does replacing the ROM replace the recovery work when a ROM is flashed? - Secondly, does changing only the kernel also change the cwm recovery? For example, if I flash Dorimanx kernel, will it also change the cwm recovery? If yes, then how does this work? - Lastly, if I build a ROM, is it necessary to add a recovery with the ROM as well? Or, if I build a ROM without recovery, will it affect the recovery when it is flashed? I know that these questions might have long answers, but I am keen to know the answers, no matter how long they are. Please try to answer all three of the questions. Or, answer as many as you can, because those questions regarding the changing of cwm recovery is very confusing. Thank You.
Hello, congrats on your new phone Unfortunately, i can't give you lenghty information about this because i don't think i know that much, but here are some facts for you: -When you flash a new ROM, it will overwrite kernel too, so you will have a new kernel, -When you flash a new kernel, it will overwrite the recovery, so you will have a new recovery,for example if A kernel has cwm as recovery, if you flash A kernel you will have cwm, and if B kernel has TWRP as recovery, when you flash B kernel you will have TWRP recovery, -Since you have to have a kernel for your ROM, if you build a ROM, you must have a kernel=recovery, you can build the kernel yourself or use someone's kernel, but recovery must be embedded in the kernel (As far as i know) When you start building your own ROM, i think you will find out the "how"s yourself though
Dakura said: Hello, congrats on your new phone Unfortunately, i can't give you lenghty information about this because i don't think i know that much, but here are some facts for you: -When you flash a new ROM, it will overwrite kernel too, so you will have a new kernel, -When you flash a new kernel, it will overwrite the recovery, so you will have a new recovery,for example if A kernel has cwm as recovery, if you flash A kernel you will have cwm, and if B kernel has TWRP as recovery, when you flash B kernel you will have TWRP recovery, -Since you have to have a kernel for your ROM, if you build a ROM, you must have a kernel=recovery, you can build the kernel yourself or use someone's kernel, but recovery must be embedded in the kernel (As far as i know) When you start building your own ROM, i think you will find out the "how"s yourself though Click to expand... Click to collapse That was short, but it does kind of make sense. Since I am using CM kernel right now, I guess the recovery will already be in there. But, If I want to create my own kernel from scratch, then are there any guides or information pages that give me an idea on how to do it? Thanks.
All that stuff is in the development sections (where the devs live), Q&A is the wrong place for stuff like this (Q&A is for n00bs with busted phones). Google/XDA search for specifics or maybe ask a few devs in the threads devoted to their kernels/roms.
Yep, the recovery will be embedded to kernel. Here is the index of guides: http://forum.xda-developers.com/showthread.php?t=1826497 (thanks to pelpa87) Index of kernels: http://forum.xda-developers.com/showthread.php?t=1702166 (thanks to GaboWinter) I use G variant and there is a nice tutorial for us, you can read and see if there is anything you want to learn from there : http://forum.xda-developers.com/showthread.php?t=2495727 (thanks to Black_Prince)
MistahBungle said: All that stuff is in the development sections (where the devs live), Q&A is the wrong place for stuff like this (Q&A is for n00bs with busted phones). Google/XDA search for specifics or maybe ask a few devs in the threads devoted to their kernels/roms. Click to expand... Click to collapse I don't believe you. Dakura said: Yep, the recovery will be embedded to kernel. Here is the index of guides: http://forum.xda-developers.com/showthread.php?t=1826497 (thanks to pelpa87) Index of kernels: http://forum.xda-developers.com/showthread.php?t=1702166 (thanks to GaboWinter) I use G variant and there is a nice tutorial for us, you can read and see if there is anything you want to learn from there : http://forum.xda-developers.com/showthread.php?t=2495727 (thanks to Black_Prince) Click to expand... Click to collapse Thanks for your time.
Dakura said: Yep, the recovery will be embedded to kernel. Click to expand... Click to collapse But, if, for example, I install dorimanx kernel, then the recovery embedded in dorimanx kernel will be installed. So, if I dualboot a second ROM from dorimanx recovery, then the recovery from the second ROM would be installed. That would mean that I won't be able to dualboot again?
Hmm, i think dualbooting has some different mechanisms, since you dual boot you have to have ONE kernel that supports dual boot, recovery will be the same since kernel is the same. So basically, you have A rom which has A kernel, then you flash B rom which has B kernel to dualboot, but there can't be two kernels at the same time so you must choose between A kernel or B kernel (both has to support dualboot ofc), and since recovery is embedded in kernel, you will have A recovery or B recovery, not both.