Related
So im wondering, what is the standard practise, or based on your own experiences. What is the best way to flash over an existing rom using CWM? What do you do to prepare the fone for new rom, wipe user data, dalvik cache, before or after flashing. Just trying to get a good idea of how to do it.
Sent from my SAMSUNG-SGH-I897 using XDA App
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Pirateghost said:
going from rom to rom:
put rom.zip on /sdcard/
reboot to recovery
install zip from sdcard
point to rom.zip
flash
reboot
any rom that has been properly done will wipe user data and dalvik cache for you. no need to do it manually
Click to expand...
Click to collapse
+1
Except I do clear the caches manually, but that's just because I have OCD.
CremeFraiche said:
i always flash back to eclair and master clear with odin one click to make sure all files from previous roms are gone then CWM flash new ROM
Click to expand...
Click to collapse
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Thx for info guys, I have flashed a few times and it seemed like now and then my fone must became bogged down and needed to be fully wiped, sound didnt work or lagfix folders bunch of text docs, just seemed cluttered. So if wanted to really clear out junk what would be a good way without having to flash back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just flash. If you have a problem then back to stock Ans a MC. I have flashed hundreds of time back to stock once.
Sent from my SGH-I897 using XDA Premium App
Pirateghost said:
lets look at the master clear function shall we?
when you flash to stock...your entire / is stock (RFS, eclair 2.1, /data /system, etc)
essentially, you have just reformatted your root, think of it like formatting your C drive and your sdcard is like a secondary internal drive that contains storage
master clear at this point will only delete items off your /sdcard
roms dont care about your /sdcard, master clear is worthless when you are stock
there was a time where it was necessary to flash to stock to reset the filesystem and then flash the rom. it has not been needed in months, but it continues to get preached as gospel.
even flashing to stock isnt necessary unless you are trying to come from CM7 or MIUI....or if something goes horribly wrong
Click to expand...
Click to collapse
I would definitely agree. I have also seen people say to disable lagfix before flashing. I have not done that either and never had any problem.
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
modest_mandroid said:
Would just like to amend the advice already given with the following:
Pre-flashing:
1. Titanium Backup of apps and data
2. Nandroid backup in case something goes boom.
Post-flashing (assuming success):
TB restore of user apps/data only. NEVER RESTORE SYSTEM FILES.
They may not apply to some people, but I feel those are necessary steps for anyone that actually uses their phone daily.
Click to expand...
Click to collapse
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Glad to hear the advice about not flashing back to stock, that's been one of the major reasons I haven't flashed quite as many rom's as I want, too time consuming.........not to say that i'm not flashing a couple rom's a week, but there's just so many options to try
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Making "search" a standard practice would be very helpful.
Restoring system is known to mess up ROMs in all cases. Though may not be mandatory, but make it a standard practice to flash stock. Takes hardly 10 mins, and helps save big headaches later.
neophile said:
why not restore system files? Does this apply if coming from flashing back to stock first, or just flashing from one rom to another?
Click to expand...
Click to collapse
Incompatibilities across rom versions, mostly. As the guy above me said, restoring system files tends to mess up a rom because you are overwriting part of it with files from a different rom.
There is one caveat, however. If you're flashing back to a rom you originally performed the backup on, you can safely restore system files. For example, if you were running Cog 4.3 and did a full TB backup, then decided to flash Serendipity 6.3, you would want to restore only your user apps and user data. However, if you decided to flash back to Cog 4.3 at some point, you could do a full TB restore without worrying about incompatibilities.
I agree with everyone else. Flashing over another rom seldom causes issues. I make s nandroid backup of my favorite rom with everything setup the way i like it. then flash away trying different roms. When i am done, i just restore my backup and all is good!
I have done a search, couldn't find the specific answer I needed, hence my asking. Could be I wasn't phrasing the search correctly......but here I am.....
To clarify, what do you dpo to get your system settings back after flashing a new rom? I flashed to serendipty 6.4 last night, as per the advice, I didn't restore system files, just apps and data, but that didn't work so well for me. I lost my data connection, could only use my wifi, and had no contacts, or any sms msgs. I don't know what else was missing, but I then went and restored system files, everything came back as needed, and there seems to be no issue......
How do I get my info setting back, or do I just need to manually re-set everything after flashing? Apart from wireless info, msgs and contacts, what else do you lose by not restoring?
Appreciate your help
havent flashed a new rom in a while and forgot if anything extra was needed when flashing a rom over a rom
thx!
Is there such a rom? I've checked teamhacksung's CM9 Alpha, Doc's Master ICS, Team ICSSGS, Fusion, and WeUI v0.6.6, and they all say to do a full wipe. Performed a search here and Google for any answers, but didn't find any.
I'm currently running Gingerbread 2.3.5 with Corn kernel, and when I upgraded from Froyo, I performed a full wipe. As many of you know, putting everything back on your phone is a major pain if you do not do a proper backup (I thought I backed up everything using Titanium, but apparently I didn't). Anyway, just curious if there is an ICS rom with a non-wipe option (or a super-cool, full of eye-candy Gingerbread rom with non-wipe).
Oh yeah, is Passion v13 Captivate-flashable? Thanks for any info you may have.
aicirt17 said:
Is there such a rom? I've checked teamhacksung's CM9 Alpha, Doc's Master ICS, Team ICSSGS, Fusion, and WeUI v0.6.6, and they all say to do a full wipe. Performed a search here and Google for any answers, but didn't find any.
I'm currently running Gingerbread 2.3.5 with Corn kernel, and when I upgraded from Froyo, I performed a full wipe. As many of you know, putting everything back on your phone is a major pain if you do not do a proper backup (I thought I backed up everything using Titanium, but apparently I didn't). Anyway, just curious if there is an ICS rom with a non-wipe option (or a super-cool, full of eye-candy Gingerbread rom with non-wipe).
Oh yeah, is Passion v13 Captivate-flashable? Thanks for any info you may have.
Click to expand...
Click to collapse
You need to do a full wipe on your phone since you're coming from a Gingerbread ROM. You may not delete what's on your sdcard if you want to retain it but as for apps, it will be deleted and so are your contacts, messages, etc.
Yuck. Okay, I figured as much, I was just hoping So, a Nandroid back-up is best, right? NOT Titanium?
aicirt17 said:
Yuck. Okay, I figured as much, I was just hoping So, a Nandroid back-up is best, right? NOT Titanium?
Click to expand...
Click to collapse
Yes, Nandroid back-up is good. You could do Titanium Backup as well but a fresh install of the apps would be better. I'm not sure it would work if you backed-up the apps from Gingerbread and install it on ICS, but you could try one app and test it.
aicirt17 said:
Yuck. Okay, I figured as much, I was just hoping So, a Nandroid back-up is best, right? NOT Titanium?
Click to expand...
Click to collapse
You can do a A Nandroid, but don't try restoring that on ICS or you will most likely cause a metric ton of problems. Titanium would be the best way to back up and restore your apps and app data. NEVER restore system data.
mrhaley30705 said:
You can do a A Nandroid, but don't try restoring that on ICS or you will most likely cause a metric ton of problems. Titanium would be the best way to back up and restore your apps and app data. NEVER restore system data.
Click to expand...
Click to collapse
Yep, forgot to mention that. Just backup your Apps and not your System Data.
Okay, wow, all the reading that I have done and I did NOT know that. No system data. Got it. Thank you both!
CM9 builds when upgrading from previous CM9 builds don't need a full wipe... I'm sure the others are the same... So won't be so bad unless you go between them all...
If you are so concerned with keeping your data and not wanting to go through the "pain" of resetting all your apps and such, you should stay with what you have. Instead, use a launcher with ICS themes to get the look of the ICS.
If you can take some pain and make the jump though, ICS offers a way more slicker OS for your Cappy.
Do not use Nandroid backup to restore your apps... TIBU is the one to use! As others said, the best way is to do a fresh (from the market) reinstall of all your apps and then use TIBU to restore your data for those specific apps only...
Edit: Concider this though while you are looking to upgrade. Most of these ICS roms are in beta stage... this means some bugs and other inconveniences... mind you they are minor but they exist. As the devs get these bugs and other issues addressed and update their roms, they would often require a fresh install (full wipe) to ensure best performance. This means that you will have to occasionally do a full wipe of your phone. It's fun to see the latest and greatest the devs have to offer but it also means that you have to do some "hard" work to enjoy the fruits of their labor... just something for you to think about...
I did not see it mentioned so I'll add. Every ROM that has a "no wipe" update is such because it is only a minor update to the existing ROM and not the whole. Even trying to do so results is a miss match of files and programs so at best you'll get FCs all over there place, at worst bootloops.
ICS, is a huge set of changes, including things google merged or removed. So the data from an app on an older version of android would be trying to send/receive info from a program that does not exist anymore and upon not getting what it wants would FC.
If you don't like having to restore everything, then wait from ICS until you see a few no wipe updates. Aside from SGSICS (since it is pure ASOP, and least likely to have any major changes) they all have a fair amount of developing yet to be done.
Now to the question of which type of backup . A nandroid backup is meant to restore your phone to it's current state (minus any partition changes). Tibu is designed for something like ROM hoping, so it only saves apps and their data. To illustrate an example of how to use both: 1 make backups, 2 load ICS ROM, 3 Tibu restore user apps (and user data only), 4 toy with ROM (be it a few hours or days), 5 you don't like it and want to go back, 6 Odin/Heimdall back to GB (to fix partition sizes), 7 restore nandroid and it's like your trip to ICS never happened.
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
cvcduty said:
If you are so concerned with keeping your data and not wanting to go through the "pain" of resetting all your apps and such, you should stay with what you have. Instead, use a launcher with ICS themes to get the look of the ICS.
If you can take some pain and make the jump though, ICS offers a way more slicker OS for your Cappy.
Do not use Nandroid backup to restore your apps... TIBU is the one to use! As others said, the best way is to do a fresh (from the market) reinstall of all your apps and then use TIBU to restore your data for those specific apps only...
Edit: Concider this though while you are looking to upgrade. Most of these ICS roms are in beta stage... this means some bugs and other inconveniences... mind you they are minor but they exist. As the devs get these bugs and other issues addressed and update their roms, they would often require a fresh install (full wipe) to ensure best performance. This means that you will have to occasionally do a full wipe of your phone. It's fun to see the latest and greatest the devs have to offer but it also means that you have to do some "hard" work to enjoy the fruits of their labor... just something for you to think about...
Click to expand...
Click to collapse
Cvcduty, you're right about enjoying the fruits of the other devs' labor. If they're willing to put in all that hard work just to keep our Captivates as updated as possible, then the very least I can do is go through 5 minutes of work to flash the roms correctly and in the way the devs intended, and not look for an easier way. I have flashed a couple of times before, I'm just not completely comfortable doing it. But I almost there!
DaNaRkI said:
I did not see it mentioned so I'll add. Every ROM that has a "no wipe" update is such because it is only a minor update to the existing ROM and not the whole. Even trying to do so results is a miss match of files and programs so at best you'll get FCs all over there place, at worst bootloops.
ICS, is a huge set of changes, including things google merged or removed. So the data from an app on an older version of android would be trying to send/receive info from a program that does not exist anymore and upon not getting what it wants would FC.
If you don't like having to restore everything, then wait from ICS until you see a few no wipe updates. Aside from SGSICS (since it is pure ASOP, and least likely to have any major changes) they all have a fair amount of developing yet to be done.
Now to the question of which type of backup . A nandroid backup is meant to restore your phone to it's current state (minus any partition changes). Tibu is designed for something like ROM hoping, so it only saves apps and their data. To illustrate an example of how to use both: 1 make backups, 2 load ICS ROM, 3 Tibu restore user apps (and user data only), 4 toy with ROM (be it a few hours or days), 5 you don't like it and want to go back, 6 Odin/Heimdall back to GB (to fix partition sizes), 7 restore nandroid and it's like your trip to ICS never happened.
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Click to expand...
Click to collapse
DaNaRkI, it's not that I don't like to restore everything (even though that's what I said), it's more like even though I have flashed a couple of times already, I'm still a little uncomfortable doing it. And I have read, I mean read for hours before I took my first step, but it seems like the more I read, I keep finding more new stuff that I probably should have known to start with. Take Nandroid and Tibu for example, I thought they worked exactly the same, but now I know, thanks to you, that there is a BIG difference. AND I learned yesterday (reading somewhere on here) to never ever restore "system data". It's a lot to keep up with if you're a blonde
Thank you for taking the time to explain, it helped a lot!
I'm new to this whole thing, as anyone who saw my last thread I made a really dumb mistake and at that point I've decided to make sure I know 100% what I'm doing before I attempt anything else.
Anyways I have a rooted HTC One, still have custom recovery, I think what I had flashed was a stock ROM but I was looking into trying another ROM. The thing is I don't want to have to redownload and re-install all of my apps and whatnot again as that was a pain in the butt. I know there's backups and whatnot through TWRP and Titanium, but do they carry over from ROM to ROM or are they specific to a certain ROM?
Or am I completely off base with this whole assessment lol. I'm trying to learn all this stuff but it's definitely a lot of information to take in and I don't want another fiasco like last time
You can use titanium backup that way you can bring your data with you but restoring data can cause lag and other issues. That's why I just reinstall them all one by one I actually enjoy the process of setting up a new Rom. It is not Rom specific at all. Also check out SMS back up & restore. With that app you can even save your texts.
"You are and will become your most dominant thoughts" - Napoleon Hill
SkinnyBiggs said:
You can use titanium backup that way you can bring your data with you but restoring data can cause lag and other issues. That's why I just reinstall them all one by one I actually enjoy the process of setting up a new Rom. It is not Rom specific at all. Also check out SMS back up & restore. With that app you can even save your texts.
"You are and will become your most dominant thoughts" - Napoleon Hill
Click to expand...
Click to collapse
Good stuff thanks for the help man. I'll probably experiment with it a bit later but will probably just do a clean wipe to be safe
If you are flashing a rom with the same base that you already have (eg. both sense roms) you can try a dirty flash and you wont loose anything except your widgets on your home screens, I do it all the time bit it does not always work from one rom to another, ALWAYS make a nandroid backup before you flash anything!!! just in case.....
Greetings, and TIA for any replies.
I recently flashed ViperOne 3.0RC1 on my dev edtion HTC One. So far so good. However, I realized after the fact that with this ROM, I'm unable to successfully run revone and gain s-off (and therefore I can't upgrade my firmware).
So, I have two questions:
-I read in various places that people had success running revone under ViperOne 2.7. Does this sound like a reasonable thing to try, rather than trying to roll back to a completely stock ROM?
-Assuming that the answer to the above is 'yes', is it possible/safe to dirty flash 2.7 over 3.0RC1? I know one can do the opposite (dirty flash when upgrading) but I haven't been able to find any information about a dirty downgrade.
Again, thanks for any pointers. If somebody has a suggestion for a more elegant way to achieve s-off and upgrade my firmware, I'd love to learn about it.
Cheers,
/alex
r0shi said:
Greetings, and TIA for any replies.
I recently flashed ViperOne 3.0RC1 on my dev edtion HTC One. So far so good. However, I realized after the fact that with this ROM, I'm unable to successfully run revone and gain s-off (and therefore I can't upgrade my firmware).
So, I have two questions:
-I read in various places that people had success running revone under ViperOne 2.7. Does this sound like a reasonable thing to try, rather than trying to roll back to a completely stock ROM?
-Assuming that the answer to the above is 'yes', is it possible/safe to dirty flash 2.7 over 3.0RC1? I know one can do the opposite (dirty flash when upgrading) but I haven't been able to find any information about a dirty downgrade.
Again, thanks for any pointers. If somebody has a suggestion for a more elegant way to achieve s-off and upgrade my firmware, I'd love to learn about it.
Cheers,
/alex
Click to expand...
Click to collapse
Anytime that you change base, always do a full wipe, whether it's noticable or not chances are you will have problems sooner or later.
If it were me i would never dirty flash between bases.
dladz said:
Anytime that you change base, always do a full wipe, whether it's noticable or not chances are you will have problems sooner or later.
Click to expand...
Click to collapse
A dev of Viper ROM has clearly stated multiple times that you do not need to wipe flashing 3 over 2.7, even when it is a new base, see here and especially here.
So in general, yes, you are right, but in this case not.
Now about the original question:
How about you make a Nandroid backup and dirty flash 2.7 back and see if it works? If you get problems, re-flash your backup.
Cheers, Ingo =;->
If you are mainly downgrading for S-off, I'd make a nandroid of your 3.0 & flash a new version of 2.7 (just so you don't have any issues while running RevOne). I dirty flashed 3.0 on top of 2.7 to test it out (I couldn't give up my tweaks!), and there have been comments in the Dev thread saying there aren't issues. But like the previous commenter said, it's always best to wipe and start fresh with a new base.
TLDR: Backup, Wipe, Flash clean! Just in case.
Thanks, all, for the replies. I wasn't really thinking correctly about how to use nandroid backups to my advantage.
One last bit of clarification: the nandroid backup will include all apps, app settings, and system settings? (read: candy crush game progress and SMS history ) It does not, however, include user data (read: music)? What about a custom kernel (not that I even have one right now, just curious)?
I'm always sort of fuzzy on what exactly gets grabbed by a nandroid (which partitions, etc).
Again, many thanks.
/alex
Curly060 said:
A dev of Viper ROM has clearly stated multiple times that you do not need to wipe flashing 3 over 2.7, even when it is a new base, see here and especially here.
So in general, yes, you are right, but in this case not.
Now about the original question:
How about you make a Nandroid backup and dirty flash 2.7 back and see if it works? If you get problems, re-flash your backup.
Cheers, Ingo =;->
Click to expand...
Click to collapse
I absolutely don't care who says it's ok or not, i've had a tonne of phones and i've flashed more rom's than i could even mention, when you do a dirty flash you are much more prone to problems, corruption and issues than with a full wipe, don't try to bash someone who knows what they're talking about.
Flashing a rom the dirty way can and does end with problems.
Why do you think people who bug report don't dirty flash? I've bug reported for many dev's for many phones and my reports are consistent and true, that is something you will not get if you don't do a full wipe.
Reason being for this is because no two phones are the same, so for one person it may work perfectly and for someone else it won't, it's that level of inconsistency that means that a full wipe is always recommended.
r0shi said:
Thanks, all, for the replies. I wasn't really thinking correctly about how to use nandroid backups to my advantage.
One last bit of clarification: the nandroid backup will include all apps, app settings, and system settings? (read: candy crush game progress and SMS history ) It does not, however, include user data (read: music)? What about a custom kernel (not that I even have one right now, just curious)?
I'm always sort of fuzzy on what exactly gets grabbed by a nandroid (which partitions, etc).
Again, many thanks.
/alex
Click to expand...
Click to collapse
A nandroid will include all data on your phone, except what is stored on your 'sd card' partition. So a kernel is saved with a nandroid. So if you are switching between kernels backup and wipe cache/dalvik between.
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
you wipe cache and dalvik cache then you flash rom on top.
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
bober10113 said:
you wipe cache and dalvik cache then you flash rom on top.
Click to expand...
Click to collapse
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
youdoofus said:
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
Click to expand...
Click to collapse
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
bober10113 said:
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
Click to expand...
Click to collapse
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
youdoofus said:
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
Click to expand...
Click to collapse
If I were to go to advanced wipe when flashing a new build if I were to leave data option alone. Will that keep all of my data or not?
edit:
@R77
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
bober10113 said:
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
Click to expand...
Click to collapse
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
youdoofus said:
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
Click to expand...
Click to collapse
did i make it sound like i was replying to you?
guess i should have quoted him to make it obvious.
and again, if he's on rom A 1.0 and wants to upgrade to rom A 1.1 then no need to clean wipe or del android folder each and every time.
have you ever had an OTA ? samsung dosent wipe clean ure device just because u upgrade. so his question regarding a similar scenario would apply, dirty flash would work fine.
and again as stated before, if there is weird stuff happening then just clean wipe. no need to get nuclear each and every time.
btw various rom builds require clean flashes because they suppose people are coming from other roms. not saying that there aren't situations where continuously dirty flashing the same custom rom all along its progress wouldint eventually mandate ir benefit from a clean flash but i know of no one that clean flashes each time their rom dev updates/increments a build. they/we only do it incase of issues, this is of some sorts an unwritten law so to speak. devs even state it when users ask if they can do as such.