I have what seems like a very basic question on backing up using TWRP, and yet I havent been able to find this anywhere in the help threads.
When I am creating a backup it asks for what I want to backup: System, Data, Boot, Recovery, Cache, .android_secure.
Which of these do I want to make sure are checked? The first backup I did I left the default (which was only System and Data) and now I am unable to restore to that backup (I just get a blank, dark screen). Looking through the forums it seems I may need to flash boot.img in order to restore?
So does that mean in the future I should make sure to also check the Book option when I create backups? Any others?
Thanks.
system, data, boot
leave the other 3 unchecked
vincom said:
system, data, boot
leave the other 3 unchecked
Click to expand...
Click to collapse
Thanks again for all of your help over the last few days!
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? And is this fixable by flashing "boot.img" if I can find it somewhere?
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? > yes
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
vincom said:
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
Click to expand...
Click to collapse
You could probably just flash the same ROM you made the backup from and then just restore the data from that backup through TWRP. Then you'd be back to the same setup you tried to backup originally, right?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Jack_R1 said:
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Click to expand...
Click to collapse
My initial backup was made just with the default - first two boxes ticked. Unfortunately I now cannot get that backup to recover and boot, which is why I am asking. What else might be the cause or how would you suggest I try to solve?
Also, apologies but I dont understand what you mean when you say "Backing up recovery in recovery is useless, though." Do you mean this isnt the best way to make a backup/nandroid to recover to?
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Jack_R1 said:
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Click to expand...
Click to collapse
Thanks. I think I misunderstood your initial post. When you said "system, data, boot" advice might fail me, I thought you meant NOT to backup boot. But I think you meant to ALSO backup .android_secure, not to avoid backing up boot.
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
lirong said:
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
Click to expand...
Click to collapse
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Click to expand...
Click to collapse
LOL. Can't we all just get along.
Since I'm not one to speak for others I'll only guess that what he was trying to get at is restoring only erases the boot.img. It then restores boot.img, system, data, android.secure, and cache. So in theory it doesn't actually erase any of the remaining partitions. It just writes over them. Whether or not this leaves any residual parts of any of the partitions has been a source of debate for quite some time. If it does format the partitions before restore there is no indication textually that I have seen.
Carry on.
EDIT: I might as well point this out before some one else does. The restores I stated above where done from CWM not TWRP. I forget what the thread was originally about. For that I apologize. The logic behind the post stands for either recovery though.
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Maybe. But a couple of points. First, I've never had any issues. Second, have you watched what happens when you restore?
Wiping system.....
Formatting system....
Restoring system....
Wiping data....
Formatting data....
Restoring data....
Restoring boot...
This is on twrp 2.3.3.0 and 2.4.0.0. So technically it does the wipes for you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So basically you have no idea what you're saying. I guess I'll go back to my being concise point
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
You're obviously a CWM guy. I'm a TWRP guy. Both are good recoveries and used by many. So use what you're comfortable with and you know works.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Related
I'm stuck the factory wipe won't work from the menu because of the moded recovery and the modded recovery won't wipe the encryption. Anyone know how to do this without unrooting?
Edit
Got around it by unrooting what a pain in the ass..
zsnethen said:
and the modded recovery won't wipe the encryption
Click to expand...
Click to collapse
?!
... which recovery are you using? Any recovery that does a complete format of /data (as opposed to just wiping it) should blow anything that's there away, I'd think?
kcrudup said:
?!
... which recovery are you using? Any recovery that does a complete format of /data (as opposed to just wiping it) should blow anything that's there away, I'd think?
Click to expand...
Click to collapse
yeah, thus the modded recovery. To my understanding, the /sdcard-folder is basically just a link to /data/media and would therefore be wiped if you tried to format /data.
(and that is just not what I'd expect. If I wipe /data on my Desire HD, it'll still keep my pictures and music on my sd-card )
Only way I found after flashing EOS on my xoom was to do 'fastboot erase userdata' which of course erased everything in /data.
Sent from my Xoom using xda premium
quck and easy one, when doing a nandroid restore do i need to wipe all partitions or just go ahead and do it?
Yes I Always wipe before restore . Also wipe cash and dalvik, I also factory reset and stay in recovery upon completion to restore . Then reboot. This gives a clean installation. You're making sure the old Rom is gone before restoring. Hope this helps. If I'm in doubt I always wipe. Just to be safe. Remember even though is a backup, your still coming from a different Rom. So you will want a clean installation before restoring. I do my restorations this way and had never had a problem.
Sent from my Sensation 4G using xda premium
ldefeo1 said:
quck and easy one, when doing a nandroid restore do i need to wipe all partitions or just go ahead and do it?
Click to expand...
Click to collapse
No. It does that on it's own.
What you are supposed to do though, is search before posting a new thread.
well i have 2 contradicating answer here...
ldefeo1 said:
well i have 2 contradicating answer here...
Click to expand...
Click to collapse
Hi,
No need to wipe before restore.
The whole point of a nandroid is to wipe what's currently there and restore the backup you made. Wiping before restoring is wasted time/power/flash writing.
Sent from my Sensation using Tapatalk 2
Usually I just wipe data, cache, and dalvik. Today though I did this plus formated data, cache, and system. I never do this but the JellyWiz rom I was flashing said to do so. Since I did this the rom will not flash.
E: Can't open /external_sd_Root/Incubus26jc_JellyWiz_VZW_9_14_12_RLS3.zip (bad)
Installation aborted.
Click to expand...
Click to collapse
When I tried restoring the old JB version I was updating from it gave me a MD5 mismatch error. When I tried to restore my original stock root which I have restored from several times without issue it just gave me "Error while restoring /system."
Need help! Stuck in recovery with no idea what to do
Try flashing a firmware through odin: 0
sent from my Galaxy s3 GT i9300 using xda premium HD @ jelly bean leaked builds
i9100g user said:
Try flashing a firmware through odin: 0
sent from my Galaxy s3 GT i9300 using xda premium HD @ jelly bean leaked builds
Click to expand...
Click to collapse
Not really sure what this means to be honest. I rooted using odin but what do you mean by flashing a firmware?
josbor11 said:
Not really sure what this means to be honest. I rooted using odin but what do you mean by flashing a firmware?
Click to expand...
Click to collapse
Yes, do that again. Boot into Download mode(Batt pull to turn the phone off) then hold vol down+home+power till the prompt comes up.
Flash the root66 image using Odin from there.
Brian Gove said:
Yes, do that again. Boot into Download mode(Batt pull to turn the phone off) then hold vol down+home+power till the prompt comes up.
Flash the root66 image using Odin from there.
Click to expand...
Click to collapse
I can just flash 66 as is? Don't have to flash a stock unrooted version first like you do when you brick?
Do you have any idea why this could have happened? I did everything it said on the page and even watched an installation video for the ROM following every step by step instruction. What the hell does formatting system, data, and cache do in recovery? Never had done it before and as soon as I did my phone just messed up. Also, if I flash 66 using odin will my old backups work again?
josbor11 said:
I can just flash 66 as is? Don't have to flash a stock unrooted version first like you do when you brick?
Do you have any idea why this could have happened? I did everything it said on the page and even watched an installation video for the ROM following every step by step instruction. What the hell does formatting system, data, and cache do in recovery? Never had done it before and as soon as I did my phone just messed up. Also, if I flash 66 using odin will my old backups work again?
Click to expand...
Click to collapse
I'm guessing there was a bad download and sadly your nandroid might have been corrupted.
Yes if you flash root66 hopefully your backups will work if they aren't corrupted.
Sent from my Galaxy Nexus using xda app-developers app
voodoomanx said:
I'm guessing there was a bad download and sadly your nandroid might have been corrupted.
Yes if you flash root66 hopefully your backups will work if they aren't corrupted.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Cool thanks. Flashing 66 now through odin. My backups have worked fine before (the exact same ones that just failed). Once this is finished and I test out my backups (assuming they work) how should I go about reflashing JellyWiz? Should I format the system, data, cache again or just do the normal wipes? I'm afraid formatting will mess it up again. Is CWM inferior to TWRP? Thinking about using a different recovery after all of this.
josbor11 said:
Cool thanks. Flashing 66 now through odin. My backups have worked fine before (the exact same ones that just failed). Once this is finished and I test out my backups (assuming they work) how should I go about reflashing JellyWiz? Should I format the system, data, cache again or just do the normal wipes? I'm afraid formatting will mess it up again. Is CWM inferior to TWRP? Thinking about using a different recovery after all of this.
Click to expand...
Click to collapse
I personally use cwm and to me it's more a matter of preference. I too have had a error restoring backups once and it was after a system wipe. A word of advice, because this saved me, keep a ROM on your SD card at all times to be able to just flash in an emergency.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
I personally use cwm and to me it's more a matter of preference. I too have had a error restoring backups once and it was after a system wipe. A word of advice, because this saved me, keep a ROM on your SD card at all times to be able to just flash in an emergency.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
A rom of Root 66?
Is it cwm flashable? I keep synergy as an emergency backup.
Sent from my SCH-I535 using xda app-developers app
josbor11 said:
A rom of Root 66?
Click to expand...
Click to collapse
dont listen to him...flash root66 thru odin as already mentioned and go from there...use my guide if need be.
droidstyle said:
dont listen to him...flash root66 thru odin as already mentioned and go from there...use my guide if need be.
Click to expand...
Click to collapse
I think you missed my point, at this point he needs Odin. However, if you keep a zip on your SD card then if your backups gasp like his situation he can just fish that zip. It was simply some advice for future reference, were not all next to a computer ask the time. For people like me that just get an urge to flash it helps to have backups like this.
Sent from my SCH-I535 using xda app-developers app
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
annoyingduck said:
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
in order to flash jellywiz i had to do the following or else i bootlooped:
wipe data/factory reset
wipe dalvik cache
format system
flash rom
booted up flawless.
i also used this methid for paranoid android...i will probably update my guide with this. unfortunately i cant give any info on what formatting system is actually doing. never had to do this before??
annoyingduck said:
No one is addressing the format question originally asked. Why is formatting being requested on yhe newer jb rom's, and what (in detail) does it do?
Many posts that people are soft bricking thier devices because of formatting instead of just wiping.
What's the deal, want some real answers here, and I think many others do too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I don't know why they are suggesting it but it doesn't do anything beyond the normal factory reset and then the zip formatting system itself.
Its just the manual way of doing what a clean flash does.
Why are people having issues restoring nandroids after doing this? Apparently bootlooping occurs after format/jb install/restore previous nandroid.
Sent from my SCH-I535 using xda premium
Brian Gove said:
I don't know why they are suggesting it but it doesn't do anything beyond the normal factory reset and then the zip formatting system itself.
Its just the manual way of doing what a clean flash does.
Click to expand...
Click to collapse
if im not mistaken formatting the system deletes the rom/kernel itself...normal factory reset from cwm recovery only deletes rom data/cache.
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
annoyingduck said:
Why are people having issues restoring nandroids after doing this? Apparently bootlooping occurs after format/jb install/restore previous nandroid.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
edit* good question!
droidstyle said:
if im not mistaken formatting the system deletes the rom/kernel itself...normal factory reset from cwm recovery only deletes rom data/cache.
Click to expand...
Click to collapse
Yeah you're right but the zip of the ROM 99% of the time formats system also.
Brian Gove said:
Yeah you're right but the zip of the ROM 99% of the time formats system also.
Click to expand...
Click to collapse
i wonder why i had to format system to get the latest jellywiz rom to not hang on galaxy s splash screen? it makes no sense.
Also, how does a format not erase your nandroids? It should also wipe titanium backups if they are not on your external. Am I wrong on that? Could formatting lose certain bits of info that the nandroid may not have partitioned, and that's why the restores are not working correctly?
Sent from my SCH-I535 using xda premium
---------- Post added at 09:57 PM ---------- Previous post was at 09:55 PM ----------
Add on: good info guys
Sent from my SCH-I535 using xda premium
I am currently on CWM touch recovery v14.4.6. If I want to a restore a nandroid backup, do I perform the following steps before I hit the restore button?
1. wipe data/factory reset
2. wipe cache partition
Any guidance is greatly appreciated.
Sure why not
Sent from my SGH-I727 using Tapatalk 2
If you're restoring a nandroid it doesn't make any real difference what you do. As long as you don't wipe the the nandroid
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
For a full restore I wipe system/data/cache. I've never had a single issue restoring.
hechoen said:
For a full restore I wipe system/data/cache. I've never had a single issue restoring.
Click to expand...
Click to collapse
Thanks for the response. I don't see the wipe system in CWM touch, only factory data and cache.
Skyrocket2 said:
Thanks for the response. I don't see the wipe system in CWM touch, only factory data and cache.
Click to expand...
Click to collapse
It would be format system in cwm if I remember right. Haven't used cwm since twrp came out.
Sent from my SGH-I727 using Tapatalk 2
xcrazydx said:
It would be format system in cwm if I remember right. Haven't used cwm since twrp came out.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Xcrazydx! So, is doing a format/system the same as wiping system?
Skyrocket2 said:
Thanks Xcrazydx! So, is doing a format/system the same as wiping system?
Click to expand...
Click to collapse
Yeah it's the same. So I should have said I format system/data/cache. Do those and you'll be fine.
Just remember that you have to flash the radio separate if you need to change radios. Nandroids to not contain the radio / modem. If you want to keep the same radio / modem, then you won't have to do anything except flash the nandroid.
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Jnewell05 said:
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Have you resolved the issues? I got error messages when I tried to do a nandroid backup with preload option checked. So, I decided to do a normal nandroid leaving out the preload and got no errors. I haven't tried to do a restore yet afraid that I might have the same issues as you.
I do believe that my backups got corrupted maybe from just not unmounting from pc properly as I just un plug it most the time. I lost the backups but still got titanium so no big loss. I change roms like I do underwear.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Jnewell05 said:
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
I've always had problems backing up/restoring from external SD. Try moving your backup to internal SD, should work fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
curiouscrackers said:
Jnewell05 said:
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
I've always had problems backing up/restoring from external SD. Try moving your backup to internal SD, should work fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I would never backup to internal sd where it can get wiped. Also keep backups on you're pc
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Hello
All XDA members
I have a problem that made me raise a question an that is an we know the name of a rom from a nanriod backup either on PC or on Andriod.??
Ideally PC would be good !!
Thanks
Most ( not all) recovery apps let you name the file. Are you asking how to find the file? If so, it likely is in a folder named backups. You can move the file to your pc and keep it there if you are out of storage space.
Sent from my CROM-i X powered TF700T using tapatalk
stevens243 said:
Most ( not all) recovery apps let you name the file. Are you asking how to find the file? If so, it likely is in a folder named backups. You can move the file to your pc and keep it there if you are out of storage space.
Sent from my CROM-i X powered TF700T using tapatalk
Click to expand...
Click to collapse
Sorry if I wasn't clear please consider the following situation :
I have around 12 backups of different roms and I dont want to restore each n every backup for sake of simple file or simple thing. So any tool which can read the name of Rom? Probably the buildprop or about phone info will help
Sent from my A110 using Tapatalk
Well, if you gave a single boot system, your recovery should "see" all of those files. If so, you can usb them or copy to a sd card and move them. Just move them back when you need to.
Sent from my CROM-i X powered TF700T using tapatalk
Can someone explain nandroid backup to me? Does it mean I can make a backup my current rom and save it? Sorry for the dumb question.
Yep
TPS_Reports said:
Can someone explain nandroid backup to me? Does it mean I can make a backup my current rom and save it? Sorry for the dumb question.
Click to expand...
Click to collapse
Simply,it is a backup of your OS and settings. It is extremely valuable if you flash a new ROM that doesn't/won't function. Then, you can use your recovery to, well, recover your previous WORKING OS.
When/if you begin to flash new ROMs (and other tools that may corrupt your OS) you should always.first.backup.your.files.
Can I assume I would need to wipe data/factory reset, etc. before I restore the backup?
Sent from my VS980 4G using Tapatalk
No assumptions
TPS_Reports said:
Can I assume I would need to wipe data/factory reset, etc. before I restore the backup?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
So, that depends on what your starting config is, what you upgraded to.
For instance, if you are stock and flash a ROM using the stock recovery, then likely yes. You should and you would use the stock bootloader to wipe with.
If you have loaded a new recovery (TWRP, CWM) then read(!) the instructions on the developers page. My example is that on my tablet, once I upgraded to TWRP, I SHOULD NOT use the factory wipe option as that would wipe both TWRP and the backup files. That would cause lots of problems so, don't assume.
Typically, you do need to data/reset/wipe prior to flashing a new or recovering to an old ROM, just be careful what/how you do it.
I have a CWM recovery installed and installed custom Rome before. I have always redid everything again. So a backup would save me a lot of time.
Sent from my VS980 4G using Tapatalk
TPS_Reports said:
I have a CWM recovery installed and installed custom Rome before. I have always redid everything again. So a backup would save me a lot of time.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Then, unless the ROM developer states otherwise, you should make backups, wipe data, install ROMs and recover your device using the Nandroid backup.
You likely shouldn't use the "factory" wipe data as that would cause issues.
Larry