A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Brian Gove said:
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Click to expand...
Click to collapse
If I switch ROM's I factory reset then wipe cache and dalvik cache. If it's a theme for example I only wipe cache and dalvik cache since the theme is suppose to be made for your ROM right?....don't see the reason to reflash the ROM as well.
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Il throw a vote to whichever works.. I usually dirty wipe.. If I have issues then clean it and try again.. With nightlies I tend to be fine dirty a lot, but even still I will do a clean every couple weeks just because..
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Dirty wipe
Sent from a SYNERGIZED GalaxySIII
When I dirty flash, I wipe data cache n dalvik cache. Once I flash what I wanted, I wipe those two once again n select "fix permissions" just in case
Sent from my SCH-I535 using Tapatalk 2
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Click to expand...
Click to collapse
I disagree. I believe a dirty flash also wipes system. If you are 100% certain that your ROM build effectively wipes system as part of it's install routine, then you could skip this step, however I always wipe system to be safe. This works for me and I rarely need to wipe data or sd card(s).
---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that?
Click to expand...
Click to collapse
When changing Kernels but not the ROM in a separate recovery session than a ROM flash, you don't need to "dirty wipe." Just wipe cache and dalvik. Dalvik wipe is key so that the dalvik virtual machine can be rebuilt by the new kernel.
Thanks for the info guys.
I usually dirty on nightlies until I have issues. Always clean when switching roms.
Sent from my SGH-I535 using xda app-developers app
It is always good to complete wipe when switching roms.
Sent from my SCH-I535 using xda premium
What if im just switching between stock rom nandroid backups? Can I just restore from one to one? I only have two backups anyways both for stock. Never flashed a rom before
Tap'n
grin0048 said:
This isn't meant to be rude or anything, I'm just honestly wondering if there's any logical reason to think this is substantively different than just not wiping data?
Click to expand...
Click to collapse
I find that this method works better than just wiping cache and dalvik, since im advance restoring data over a clean flash. both ways are considered dirty flashing tho.
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
coldhardtruth said:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
Click to expand...
Click to collapse
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
droidstyle said:
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
Click to expand...
Click to collapse
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is what I meant as a dirty flash when I made the thread yes...
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Usually when I flash a new kernel, or a different kernel, I just wipe the davlik cache and I am fine. There was some reboots after the first boot on the AOSP ROMs but afterwards it ran fine.
SlimSnoopOS said:
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoop is correct. According to one of the developers of a very prominent ROM the IMEI issue was because our phones got confused sometimes(Randomly phone to phone) and tried to reset during a flash. The data it tried to reset was bogus, therefor losing IMEI. He is also correct far as the wiping battery stats. It's only usefull when you have really strange results with battery. Google for the real reason to use them.
Far as backing up your IMEI so you will never run into the problem of losing it.... go into your terminal (almost every ROM has a Terminal emulator)
Type this:
su
then hit enter. Grant permissions
then type:
reboot nvbackup
then hit enter. This will make your phone do some shyt and reboot, but you really shouldn't need to worry about your IMEI after this. Regardless of how many ROMs you flash or what you do or who you date or who you kiss, etc... blah blah....
This really should be the end all for the IMEI...
annoyngduck said:
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
New rom only when their bases are different , like going from ics to jb, or the dev says to do it (Even then Ill try it without a wipe because im lazy).
Themes I never wipe anything
Nightlies never wipe anything.
Edit: If I do have issues I then go back and wipe delvik and cache . That usually straightens out any issues and allows me to keep my setup.
tonu42 said:
Hey but you know I'm right
Click to expand...
Click to collapse
Actually you're not right.
Sent from my SCH-I535 using Tapatalk 2
Ok, I did a system wipe, cleared the dalvik and cache, rebooted to fastboot flashed the stable cm10 rom, went back into recovery and flashed rom and flashed gapps. cleared cache and dalvik and rebooted. Everything works fine but i keep getting a warning that states "Unfortunately Android(AOSP) keyboard has stopped. Would Gapps have anything to do with this?
RC196 said:
Ok, I did a system wipe, cleared the dalvik and cache, rebooted to fastboot flashed the stable cm10 rom, went back into recovery and flashed rom and flashed gapps. cleared cache and dalvik and rebooted. Everything works fine but i keep getting a warning that states "Unfortunately Android(AOSP) keyboard has stopped. Would Gapps have anything to do with this?
Click to expand...
Click to collapse
What hboot are you on bro? If its the latest, you need to flash the boot img FIRST. Then go and wipe all cache types, system and factory reset. Then flash CM.
Sent from my One X using xda premium
ToxicWaste said:
What hboot are you on bro? If its the latest, you need to flash the boot img FIRST. Then go and wipe all cache types, system and factory reset. Then flash CM.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I did all that. Sorry didn't provide all of it in details. I guess its becaue of Gapps 4.2. I'm flashing an older version of gapps.
Yep that was the problem. I wiped everything and reflashed rom and older version of Gapps and problem solved.
do we also wipe system before installing roms?
or just cache and dlv
bstylz911 said:
do we also wipe system before installing roms?
or just cache and dlv
Click to expand...
Click to collapse
If you want the new rom to run without any issue wipe everything. I always do wipe cache, dalvik, data, system. Do it a few times, even reboot recovery between. I always do and never have any issue.
Sent from my HTC One S using xda app-developers app
I do factory reset then wipe system then flash rom and has work every time.
When changing type roms, Like sense to aosp . wipe evrything.
When flashing update or newer version of same ROM , you can dirty flash. Saves you setting up the whole device over again. Just wipe cache and dalvik.
Always check advice if wipe is needed.
Wiping the same things multiple times over is just for your own mindset. Once is normaly enough.
Verstuurd van mijn One S met Tapatalk
I wipe everything 3X. I don't like dirty flashing because if you encounter a bug you won't know if it's due to the rom or you dirty flashing.
dcaples002 said:
I wipe everything 3X. I don't like dirty flashing because if you encounter a bug you won't know if it's due to the rom or you dirty flashing.
Click to expand...
Click to collapse
Thank you for this!
I only wipe system and both cache partitions when flashing an updated version of a ROM. If I am flashing a completely different ROM, I wipe data as well. There is no point is wiping anything multiple times.
So just to make things clear here. It is safe to wipe everythinggggg? Also when backing up before rooting or flashing a new ROM where exactly does the back stores? I tried restoring it and i couldn't find its location :fingers-crossed:
So I flashed a custom ROM and did the usual steps. Install, wipe caches, etc., and the ROM itself loads. It's a custom 4.4.2 ROM for GT-P31XX and I used CWM 6.0.4.5 recovery to flash it. Problem is that when I boot, I get to the lock screen but System UI, Settings, and AOSP Keyboard always fail. I can't seem to boot into recovery any more but I want to install a different ROM or reinstall stock JB and start over. How would I go about fixing this situation?
Okay, I can boot into recovery actually.
KingMotion said:
Okay, I can boot into recovery actually.
Click to expand...
Click to collapse
Did you wipe everything first then install? Because you want to wipe, install, boot. Cache, dalvik, data, system are the main ones, always wipe these when flashing a new ROM.
Sent from my GT-P5110 using XDA Premium 4 mobile app
anyone gonna help? (lenovo vibe k5 note)
ThunderSquall said:
anyone gonna help? (lenovo vibe k5 note)
Click to expand...
Click to collapse
Did you factory reset, wipe cache and dalvik when you flashed the ROM? If not, boot to recovery and factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try reflashing the ROM. You might need to post your issue in the thread where you got the ROM so that the developer can fix it.
If that doesn't work, try another ROM.
If that doesn't work, go back to stock.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Did you factory reset, wipe cache and dalvik when you flashed the ROM? If not, boot to recovery and factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try reflashing the ROM. You might need to post your issue in the thread where you got the ROM so that the developer can fix it.
If that doesn't work, try another ROM.
If that doesn't work, go back to stock.
Click to expand...
Click to collapse
thank you for helping, i realize i flash A7020a48 but my device is A7020a40. when i flash the A7020a40 stock rom my issue got fix. ty and sorry for my bad englisky.