I have looked all over and there have been some people that have said how to flash a new kernel, and how it is basically exactly like flashing a rom and don't go into it any further.
Plus it seems like the only people i can find that even mention flashing a new kernel are also making a guide to flash a new rom, so keep the settings form an old rom aren't an issue for them or the people reading those guides.
I have found a rom that I like and want to stick with it, but what I am wondering, is if I want to test out different kernels for potential battery saving abilities, will I have to go through the same process in CWM of wiping the cache/dalvick cach/format system and stuff like that, or can I just flash the new kernel the same way I can flash a baseband, without changing any settings or worry about it deleting anything I have done?
I just don't want to go around *assuming* anything because last time I did that I had to spend 50 bucks on a JTAG
Thanks!
I only use KTkernel and.....
wipe cache
wipe dalvik
install kernel from ext sd or sd
wipe cache
wipe dalvik
fix permissions
rebooot
And just make sure they are TW if you are running a TW rom and AOSP if you are on that type of rom. And have a backup in case something goes wrong.
I have been flashing kernels on two different phones and have never had a problem. Just read and make sure you are doing it right.
Some people say you should wipe cache + dalvik before flashing a kernel, but that's questionable if you really have to. I simply flash and reboot, never experience problems. And definitely make sure it's meant for TW or AOSP, depending on which you are running.
Sent from my SCH-I535 using Tapatalk 2
Related
This is a flashable zip that simply returns your kernel and wireless.ko to stock GB 2.3.3 as delivered by LG in the update. This is for people who have played around with custom kernels and wish to go back to stock for whatever reason. Caveat: I have not tried the zip myself but one user has reported he has used it with success. This is a simple flash that simply replaces the boot.img and wireless.ko with the files from stock, so you should have no problems with it.
Disclaimer: I am not responsible if you brick your phone, void your warranty, or any other pain or suffering you may experience as the result of flashing this kernel.
Note: Always wipe the Dalvik Cache when flashing a new kernel. If you don't unintended consequences (i.e., boot stuck on LG logo or boot loop) may result. The first boot after flashing will take around five minutes or so. Please be patient and don't report your phone is bricked while it is still booting and rebuilding the Dalvik Cache, which takes several minutes depending on how many apps are installed.
Please report back any success or failures here.
Enjoy!
Attachments:
P999-GB-Kernel-Stock.zip (4.26 MB)
MD5: 52b1f38ff846082aed99bf8ac7fdb756
Reserved for future use by the OP.
This has been needed for a while. Thanks!
Thanks
Sent from my LG-P999 using xda premium
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
mojorisin7178 said:
I was wondering if there was away to revert back. Thanks alot. Hey i got a question I am still a noob and I just stsarted changing kernels but Have been flashing for a while. I asked whast needs to be done before I flash and was told to wipe cache but nothing else is needed. I am haveing a problem with the new EB 2.1 and trinity kernels. When I do a hard boot to fix data it reboots twice the second one being a normal boot so I still dont have data. Should I try to wipoe dalvik and cache would that fix it if no do you have any suggestions?
Charlie
Click to expand...
Click to collapse
This thread is for the stock kernel. Please post your question in the EB 2.1 and Trinity Kernel threads.
This is useful thanks, wish we had one for cm7.....
ONLY the D. Cache should be cleared right?
SyntekSystems said:
ONLY the D. Cache should be cleared right?
Click to expand...
Click to collapse
Yes. The Dalvik Cache is the crucial thing you need to clear when you flash any system file, kernel, etc. If you don't a bootloop or stuck boot is a likely result. If you flash a different rom then you should wipe the system also to be safe.
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
SyntekSystems said:
reason is because I've been clearing the Cache partition as well, I'm not sure if I was suppose to do that, lol.
Click to expand...
Click to collapse
No reason to clear normal cache. In fact, if you use Rom Manager, that will delete the recovery it flashed as that is where it keeps it.
i looked through the forum and didn't find this exact question so i'm sorry if it's been posted before.
basically what i'm wondering is if i have a ROM installed, let's just say one of the new ICS ones, and a new release of that ROM comes out, is there a way to upgrade to the newer version without having to install all my apps and stuff again through titanium backup? i hope that makes sense. in other words, is installing a new version of a ROM that you are already using going to be the same process as flashing a new ROM entirely? that could get annoying with newer versions of ICS seemingly coming out twice a week.
thanks in advance!
It's recommended to wipe and reflash, but I just flash over top and if there's problems I resort to wiping. Clear cache and dalvik and just flash over top, your apps will still be there. But if you do it this way, you should not report any problems
Sent from my Inspire 4G using Xparent Blue Tapatalk
Probably could have used search to find this. But typically, unless the dev say to full wipe, when an update comes out for the rom you are using you can flash the update over the older version without a full wipe. You are still required to clear cache/dalvik to do this. If anything that was working before does not work anymore after you have flashed the update over the older version, then you should go back and do a full wipe and flash the new version. I personally always full wipe when flashing a newer version.
Sent from my Inspire 4G using xda premium
It all depends on the ROM and what is updated. Seriously you have to go by what the DEV says in his thread. Some you can update without wiping and some you have to wipe. Others will automatically wipe for you. Best advice is to read the DEV's thread. They should all give you this info. And if you looked over the first few posts of his thread you really wouldn't be asking this question here.
Some mods have the cache/dalvik wipe built in, so just make sure you read through the thread for whatever mod you're trying. Wiping it twice won't hurt, but just wastes a little time.
RunnyDrOiD
I know that we have different method for rom installation but do you have any idea about RunnyDrOiD
Thanks
lgluna20 said:
I know that we have different method for rom installation but do you have any idea about RunnyDrOiD
Thanks
Click to expand...
Click to collapse
really? man. I'll make this very simple for you.
1. put rom on root of sdcard
2. boot into recovery
3. wipe data, cache, dalvik cache
4. install from sdcard the zip file
5. reboot.
almost all ROMs except for the PD98IMG.zip stock ROMs are flashed with the above method. Not all ROMs require a full wipe (data, cache, dalvik cahce) when upgrading within the same ROM but it is recommended to do so to avoid any issues. If you're switching between different ROMs, it is required to do a full wipe. Search my good man.
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
tomalrocks said:
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
Click to expand...
Click to collapse
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
tomalrocks said:
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
Click to expand...
Click to collapse
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
aypeeootrek said:
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Click to expand...
Click to collapse
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
tomalrocks said:
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
Click to expand...
Click to collapse
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
thnx123
yhnk you for
Zalithian said:
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
Click to expand...
Click to collapse
hehehe I already got that scare after flashing new rom and it was taking a long time to boot during first boot.
Thanks anyways
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Smeghead_ said:
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Click to expand...
Click to collapse
Well since I really only have experience with a tablet and older cell phone I can only speak of my experiences with those. My tablet runs 4.2.2 and the phone 2.2. With both devices I have never had to flash them back to stock to flash an update. Usually a data and cache wipe was sufficient although I will wipe the whole system when flashing a huge update on the tablet.....like from GB to JB.
What helpful people told me when I asked the same question was...
When going to a very different (including the same ROM going to a new android version, ie 4.1 => 4.2) ROM (as in, not just doing a small update on the current one) :
Wipe both caches, wipe /system, wipe /data, and wipe internal sd card and factory reset.
Then flash what you want - ROM => Kernel (if desired) => GAPPs
Wipe caches again.
Done!
I don't know about your particular phone and those ROMs. Is AOKP 2 to 3 a big change ? If so, simply writing 3 over 2 could cause some major problems. I totally messed up and did something like that once and while it wasn't a huge deal I had to start over and do it again because it wasn't usable.
In regards to your description of what you did, you didn't wipe /system, so you didn't wipe your system and so it was still installed like you saw. You'll need to "start over" and wipe everything again. Since the N 4 doesn't have an external SD, I'm guessing you guys wipe /system and like, push the ROM to be flashed to the internal storage ? Maybe ? I have no idea - I've always had an external SD, but since it's a Nexus device I'm sure the procedure is well-covered !
My Kindle Fire tablet also does not actually have an SD card either.....the 8GB memory has been partitioned and originally I would have 5GB available out of 8 which would act as the SD card and 1.09GB for internal or "phone" memory. I have mine even more scrapped down as this one has the ability to either boot into CM7(GB) or the newest CM10.1(JB).
Say for example I went from Android 4.1.2 to 4.2.2.....that's a pretty big update......I would do a full wipe meaning doing it in this order: factory reset, wipe cache, wipe dalvik, and wipe system.
If I wanted to flash a little update of my current 4.2.2 where only some slight tweaks were applied I would just wipe cache and dalvik only. There are times when this simple flash wipe technique WON'T work and you'll probably realize it real quick. There could be any one of a million bugs that could occur and usually they are pretty noticeable. If that happens (sometimes it will, sometimes it won't) the worst case scenario is just going ahead and doing the full wipe.
I'm not knowledgeable on AOKP ROMs so I don't want to venture there. Boot loops are a whole different story and you might want to educate yourself as much as possible because they can happen. I had a couple occurances with a boot loop not too long ago as I was messing with a system font editor and it caused a boot loop. I didn't panic.....I already researched how to handle them so getting it back online was quite easy.
Hope my rambling has helped even a little bit.....
As long as you are just updating the same Rom, you can usually just flash it over (unless the Rom-maker says different).
If there are some fundamental changes in the Rom update, or you are switching to another Rom, then you should wipe it all.
To make it all a bit easier, you can use the Megawipe script:
http://forum.xda-developers.com/showthread.php?t=1832326
Along with the Aroma installer, it's just a few clicks to clean it all up, and ready for a fresh install
What exactly does this do? Every time I'm flashing a new ROM and I wipe/fix permissons I seem to hang at the boot screen. Am I hurting myself not doing this?
Sent from my SCH-I535 using xda app-developers app
You shouldn't have to fix permissions on a new ROM flash. In fact, running the fix permissions command is rarely needed. I would never make it a routine thing to do.
hallstevenson said:
You shouldn't have to fix permissions on a new ROM flash. In fact, running the fix permissions command is rarely needed. I would never make it a routine thing to do.
Click to expand...
Click to collapse
Agreed
Some more info would be much appreciated here; I realize there is info out there but I'm still not 100% sure *what* I'm actually doing besides following instructions when doing wipes to flash anything. Not hijacking the thread but I'll rephrase the Q and hopefully someone can help clear things up:
When I read thru various guides for flashing various updates including ROMs, Gapps, kernels, system MODs etc, it seems that the order of the wipe and the extent of the wipe differ even between the same ROM (different model phone, ports, etc).
Is there a "standard" wipe procedure/ order of steps for;
(a) flashing a ROM update (assuming same kernel, and gapps flash needed ontop)
(b) flashing a new ROM (from a different build and/or kernel)
(c) flashing a system MOD (ex: crossbreeder)
(d) flashing a kernel (update or new)
I know there are those who feel that OCD urge to wipe wipe rinse repeat for every little thing but I'm hoping someone can clear us n00bs up on *why* we are doing what we are doing. The *essential* wipes and the order of each, and what files/partitions is that wipe effecting.
One more to expand on OP's question;
When then *should* we fix permissions?
Thanks a ton
MichPRich said:
Some more info would be much appreciated here; I realize there is info out there but I'm still not 100% sure *what* I'm actually doing besides following instructions when doing wipes to flash anything. Not hijacking the thread but I'll rephrase the Q and hopefully someone can help clear things up:
When I read thru various guides for flashing various updates including ROMs, Gapps, kernels, system MODs etc, it seems that the order of the wipe and the extent of the wipe differ even between the same ROM (different model phone, ports, etc).
Is there a "standard" wipe procedure/ order of steps for;
(a) flashing a ROM update (assuming same kernel, and gapps flash needed ontop)
(b) flashing a new ROM (from a different build and/or kernel)
(c) flashing a system MOD (ex: crossbreeder)
(d) flashing a kernel (update or new)
I know there are those who feel that OCD urge to wipe wipe rinse repeat for every little thing but I'm hoping someone can clear us n00bs up on *why* we are doing what we are doing. The *essential* wipes and the order of each, and what files/partitions is that wipe effecting.
One more to expand on OP's question;
When then *should* we fix permissions?
Thanks a ton
Click to expand...
Click to collapse
There is no standard wiping procedure. At the bare minimum you should factory reset, wipe cache, and wipe dalvik cache for a ROM. In some instances a dirty flash may be recommended for an update, but not always. Others like to add steps to the reset, such as formatting system. I always clean flash for any rom by factory reset, wipe cache, wipe dalvik cache, format system, then flash rom. I usually flash a kernel without wiping anything.
Different developers have different opinions on what you should do and how efficiently it works. In my opinion, I think a lot of the multiple wiping procedures some developers recommend is unnecessary. However, if I'm running their ROM I will follow the instructions exactly so I can accurately report bugs to them if something comes up.
Fixing permissions is usually unnecessary, it has to do with rewriting app permissions to the kernel and will often fix issues involved with force closing. I really don't think it helps too much, but some devs like to recommend it. The reason it takes a long time to boot is because after you fix permissions, every app has to ask the kernel to run again. Which can take a while depending on how many you have installed.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
There is no standard wiping procedure. At the bare minimum you should factory reset, wipe cache, and wipe dalvik cache for a ROM. In some instances a dirty flash may be recommended for an update, but not always. Others like to add steps to the reset, such as formatting system. I always clean flash for any rom by factory reset, wipe cache, wipe dalvik cache, format system, then flash rom. I usually flash a kernel without wiping anything.
Different developers have different opinions on what you should do and how efficiently it works. In my opinion, I think a lot of the multiple wiping procedures some developers recommend is unnecessary. However, if I'm running their ROM I will follow the instructions exactly so I can accurately report bugs to them if something comes up.
Fixing permissions is usually unnecessary, it has to do with rewriting app permissions to the kernel and will often fix issues involved with force closing. I really don't think it helps too much, but some devs like to recommend it. The reason it takes a long time to boot is because after you fix permissions, every app has to ask the kernel to run again. Which can take a while depending on how many you have installed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Very good info, thanks.
I was unsure why my ROM (Dark Rootbox Nightly builds on usc) have us wipe/reset, wipe cache, and the final step in wiping dalvik comes *after* flashng ROM/gapps. But your response helps a lot ty again.
MichPRich said:
Very good info, thanks.
I was unsure why my ROM (Dark Rootbox Nightly builds on usc) have us wipe/reset, wipe cache, and the final step in wiping dalvik comes *after* flashng ROM/gapps. But your response helps a lot ty again.
Click to expand...
Click to collapse
It's simply personal preference on what the developer thinks is most efficient.
Sent from my SCH-I535 using Tapatalk 2
A lot of good info, thanks. What is stored in dalvik cache
Sent from my SCH-I535 using xda app-developers app
camf3xu said:
A lot of good info, thanks. What is stored in dalvik cache
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Dalvik cache is what actually runs an app. It stores a specific file after an app is installed to allow the app to run.
Sent from my SCH-I535 using Tapatalk 2