Whats the diffrence between dirty and clean flash?
azoga said:
Whats the diffrence between dirty and clean flash?
Click to expand...
Click to collapse
A clean flash is when you wipe every thing clean. A dirty flash typically is when you don't wipe /data and update to a newer version of the same rom and same android version.
There are plenty of variables that people will do differently:
A normal clean flash will entail wiping/formatting system(often done automatically in the rom installer-script), data, cache, and dalvik/art cache. You can also wipe internal storage(internal sd card/sd card 0), android secure, preload for an ultra-clean flash(not usually needed). Obviously the downside is you will need to install and set up all the apps you want from scratch. Using backup tools like Titanium Backup can help here, but also can lead to problems.....
A dirty flash is normally just rebooting to recovery and flashing the newer nightly and rebooting again with no wipes. A lot of people wipe cache and dalvik/art cache before rebooting. This(dirty flashing) is only advisable if the rom you are flashing is of the same android version and an update that is fairly close to the existing rom. There can potentially be all sorts of issues when you dirty flash due to major changes in the code. The rule of thumb is if you dirty flash and start getting strange issues, then a clean flash will normally solve them.
BTW: If you leave a brief description of your question in the thread title you may get more responses and help others who have similar questions
Related
Is it only necessary when coming from ICS to JB or is it necessary to do when coming from a JB ROM to another JB ROM? In my SGS2 days it was factory data wipe, wipe cache, wipe delvik cache, and maybe a kernel cleaning script for good measure, but never touched my SD user content( PDFs, music, etc.).
Super wipe will erase everything( as indicated by the warning in CWM), if you don't think it did cuz you still see the files, try and open them, its a shell only, no content (still lists correct file sizes though???)
I found this out by trying to flash some alternate ROM firmware or kernels I had but couldn't get them to work.
Don't use those stupid superwipe .zip's.
They're running the same scripts as your recovery runs...potentially multiple times for the "LULZOMGCLEAN" factor. [Uh...not needed]
Even installing a rom wipes /system...but %90 of people say "lul wipe /system/ /data/ /cache/ /dalvik/ and then flash superwipe..."
(Yes, I realize a script has to be run for the .zip to wipe system...and the Rom dev MAY leave it out. Personally, if the developer of my rom doesn't even make a "wipe system" script in the .zip I would not use that rom.)
NOT necessary.
If you don't trust your recovery to do it's job...wipe everything with one wipe...
Maybe you should get a new one.
Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.
jesusice said:
Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.
Click to expand...
Click to collapse
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!
Jubakuba said:
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!
Click to expand...
Click to collapse
Right. Many ROMs like CM are supposed to have a script to preserve Gapps and they say that you don't need to flash Gapps after, say, updating to a new nightly but I've learned the hard way not to depend on it.
I want to update my Unofficial CM10 +3.x Kernel to the latest update from Hashcode.
UNOFFICIAL CM10 + 3.x Kernel for Kindle Fire [09/16 CHARGING+]
When you do an update like this, do you wipe everything like I did when I first flashed the ROM? I mean, when I installed, I wiped system, factory reset, cache and dalvik cache. Then I flashed the ROM and then I flashed gapps.
So now I just want to update the OS, what do I need to wipe? And will I need to flash gapps again?
CAn't ask this in the development thread 'cause my n00b hat it still too shiney.
Thanks!
A question like this doesn't belong in the development thread because it isn't development related.
If you're going from one ROM to a different one, you need to wipe System and Factory Reset (data and cache).
If the ROM is simply an update of an existing ROM, generally all you need to wipe is data and cache. There are always exceptions to this so it's always a good idea to make a backup in case things turn sour.
After installation of the ROM you have the option to wipe cache and dalvik. It isn't required but not wiping them has been known to cause some bugginess.
soupmagnet said:
A question like this doesn't belong in the development thread because it isn't development related.
If you're going from one ROM to a different one, you need to wipe System and Factory Reset (data and cache).
If the ROM is simply an update of an existing ROM, generally all you need to wipe is data and cache. There are always exceptions to this so it's always a good idea to make a backup in case things turn sour.
After installation of the ROM you have the option to wipe cache and dalvik. It isn't required but not wiping them has been known to cause some bugginess.
Click to expand...
Click to collapse
Thank you once again, soupmagnet. Yeah this is just an update to my current ROM. So .... I won't need to flash gapps again?
I'm slowly figuring this stuff out. hehehe... When I was 30 I picked this stuff up quick. Turning 60 on Thursday and stuff tends to need a little more pondering lately. hahaha
Anywho.... thanks
Oh, yeah. You need to flash Gapps if you wipe system.
soupmagnet said:
Oh, yeah. You need to flash Gapps if you wipe system.
Click to expand...
Click to collapse
OK, see, now you're messin' with the old man here... hehehe
On one hand I'm hearing if I am only updating my current ROM, I just wipe data and cache.
Then you tell me I have to flash gapps if I wipe System.
But prior you said I only need to wipe system if I'm going from one ROM to a different ROM.
So.... I'm just updating my current ROM. I wipe data and cache, flash the updated ROM, wipe dalvik.... done...
no flash gapps, right?
I need to look at TWRP again to see exactly how it presents the choices. Don't be hatin' on the old guy for bein' dumb now.
OK, booted to TWRP. When I select Wipe my choices are : Cache, Dalvik Cache, Factory Reset, System and then External Storage. So... in your first answer to me when you said to go to a different ROM I should wipe "System and Factory Reset (data and cache)" it appears you are telling me that "System and Factory Reset" is another way of referring to "data and cache". Is that correct?
Gapps go in the /system/app folder so if you wipe the system partition, Gapps will go along with it.
soupmagnet said:
Gapps go in the /system/app folder so if you wipe the system partition, Gapps will go along with it.
Click to expand...
Click to collapse
GAaaahhh..... I just wiped System and watched as it processed /system
and then I wiped Factory Reset and watched as it processed /data and /cache
So I guess that answers my confusion.
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Zepius said:
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Click to expand...
Click to collapse
Guess I might as well wipe the cache and dalvik even on a dirty flash?
Thanks
I upgraded from CM10 M1 to M2 with only a wipe of Dalvik cache. Works fine.
I finished installing M2 after wiping both the cache and dalvik cache (figured I would do the cache just in case).
Worked great!
Thanks all
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
***what Nexus version do you have?*** i've used the below instructions with GSM GNex***
If you're coming from an AOSP CM9 rom, Do the following :
Download Maguro (or your models ROM+Gappsl).
- boot into recovery.
- Preform NANDroid Backup.
- Wipe Dalvik cache.
- Wipe Factory reset.
- Wipe Cache.
- install zip from SDcard>choose zip from SDcard>ROM.zip (your ROM)
- Flash Gapps.zip
- Flash kernel.zip (if you have one)
- go to Advanced> Fix Permissions
- Reboot system now !
- Enjoy.
***I've used this method for a trillion flashes !***
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
bk201doesntexist said:
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
Click to expand...
Click to collapse
+1
Right now I am running jb build 5, and I want to update it to jb milestone 1.
My question is simple, can you dirty flash it? I know that people who ask about dirty flash should be "killed", but I'm new to this Android and flashing ROM.
h7779 said:
Right now I am running jb build 5, and I want to update it to jb milestone 1.
My question is simple, can you dirty flash it? I know that people who ask about dirty flash should be "killed", but I'm new to this Android and flashing ROM.
Click to expand...
Click to collapse
U can dirty flash it. But if it bricks your phone don't get mad. If I was you I would wipe wipe and wipe some more ...
But like you said, your new to android. Do what you think is right for your phone.
Good luck
Sent from my SGH-T959 using Tapatalk 2
People who ask about dirty flash should be killed.
If it bricks your phone, don't get mad?
Click to expand...
Click to collapse
Seriously?
Dirty flash it. People who clean flash every nightly like wasting their time. I've outlined my feelings on this issue more than once. Wipe Dalvik and be done with it.
I have always dirty flashed AOKP between builds on my previous phone with only wiping cache/dalvik cache. Only time I full wipe is when there are significant changes or Android version jump. Never had any problems. Here's my recommendation for dirty flashing:
If you have Google Wallet installed on /system partition, reset it first.
1. Boot into recovery
2. Wipe cache and dalvik cache
3. Run a nandroid backup. Always do this.
4. Copy the nandroid backup to your PC or somewhere safe
5. Flash the new build
6. Flash gapps
7. Flash custom kernel (optional)
8. Reboot and profit
Dirty flash or full wipe flash, there always are possibilities for problems. Sometimes you could have a bad flash, just reflash or restore the nandroid and reflash.
S-Beamed from my GS3 via xda premium
[email protected] said:
I have always dirty flashed AOKP between builds on my previous phone with only wiping cache/dalvik cache. Only time I full wipe is when there are significant changes or Android version jump. Never had any problems. Here's my recommendation for dirty flashing:
If you have Google Wallet installed on /system partition, reset it first.
1. Boot into recovery
2. Wipe cache and dalvik cache
3. Run a nandroid backup. Always do this.
4. Copy the nandroid backup to your PC or somewhere safe
5. Flash the new build
6. Flash gapps
7. Flash custom kernel (optional)
8. Reboot and profit
Dirty flash or full wipe flash, there always are possibilities for problems. Sometimes you could have a bad flash, just reflash or restore the nandroid and reflash.
S-Beamed from my GS3 via xda premium
Click to expand...
Click to collapse
Thanks for all of the responses, I'll just dirty flash it. Also I have brick my phone twice now and was able to unbrick it, so I'm not really worry about bricking it again.
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
geokilla said:
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
Click to expand...
Click to collapse
wipe dalvik art cache, cache and system
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
geokilla said:
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
Click to expand...
Click to collapse
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
OhioYJ said:
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
Click to expand...
Click to collapse
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
geokilla said:
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
Click to expand...
Click to collapse
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
OhioYJ said:
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
Click to expand...
Click to collapse
I've asked in the Havoc OS thread but the instructions to clean and dirty flash are the same as when I first played with custom ROMs back in the Samsung Galaxy S days. Wipe system, wipe data, wipe the two caches, etc etc.
If you're using a Substratum theme, make sure to disable all overlays before flashing.
Sorry for digging this post, but with android 10 there is no way to decrypt the data partition.
So how do you dirty flash android 10 "properly" ?