I run mean rom 3.4, s-off. I haven't upgrade to the new firmware, do have new radios, since I left on deployment when the beta was available and needed something stable but plan on doing so when I get home in a month. My question is after a fresh wipe, dalvik, cache, system, factory, I will install the next version of mean rom, or any rom for that fact. Then, to keep my applications, data and settings, I will restore only the /data folder from a nand backup after formatting the newly generating /data. Is there a problem with this practice? The only thing I notice is some of the larger application need to re download. But all settings, contacts, keys, passwords, screens, icons come back perfect. Although this seems to work in practice I feel like it shouldn't be this simple. I run the kitchen program on all my roms to keep my current bootani, splash, ringtones, sounds etcs and do a app cleaner script to remove the crap apps. I have seen the Aroma backup rom cleaner and am curious. Would this be a better method? Thanks in reply since the recent world events in Yemen and Egypt may prevent me from getting internet for a while.
Related
What does wiping data/cache actually do, whats does it wipe? Is there like a list or something of what it erases? I just want to install new rom and don't want to erase stuff I need. Thx to anyone that can help me understand.
Payaso1 said:
What does wiping data/cache actually do, whats does it wipe? Is there like a list or something of what it erases? I just want to install new rom and don't want to erase stuff I need. Thx to anyone that can help me understand.
Click to expand...
Click to collapse
It wipes all your user data. If u want to keep your apps go get titanium back up and back up all your apps. Then wipe data and cache then after flash a new rom download titanium again and restore apps with data.
Sent from Glacier with CM7
Hey thx so it doesn't wipe contacts, ringtones, or other info?
If you are installing a new ROM the best way to save contacts is to make them google contacts, sync, and then all of your contacts are kept with google, so when you log in with the new rom everything downloads to the phone. with ringtones as long as they are saved in media/sounds they are fine. It's difficult to install a new rom while keeping all of your current user data perfectly intact. Nothing is 100% guaranteed to work, and installing a ROM always comes with risks. If you are THAT dependent upon your userdata in it's current state, maybe you're better off where you are. Where there is a will, there is always a way, but if you are simply trying to save yourself time and effort, working with custom ROMs rarely affords you that comfort. Once you get it set up it can run like a dream, but getting there usually has a few bumps.
Yeah, I just flashed from EB01 SC 292 to ED01 MIUIWiz after full Data, Cache, Dalvik, and voltage double wipes, and restored all my old EB01 user Data and apps over MIUIWiz, all in under 17 minutes.
Edit: adding navenedrob's utility method has cut this down to under 10 minutes, plus navigation and reboot time. See post #5
How? Just followed what the Devs have taught us, plus Nandroid Advanced Restore in CWM.
I have been doing this for every ROM I have flashed since I discovered what a Nandroid backup was.
But this is not just a Nandroid Backup. This is a partial restoration called “Restore data” under “Advanced Restore.” All in CWM recovery.
Here is the method I use:
Charge to 100% (At this point, I started the timer)
Boot to Recovery
Wipe Cache and Dalvik (and Voltage for MIUIWiz) x2
Make a Nandroid backup
Wipe Data x2
Flash the new ROM (of your choice) in CWM
Let it boot
Boot to Recovery
Select “backup and restore”
Select “Advanced Restore”
Select the Nandroid Backup file you wish to restore from (probably your latest one)
Here is where it gets cool, and less scary…
There is yet another page, with options:
Restore boot
Restore system
Restore data
Restore cache
Restore sd-ext
+++++Go Back+++++
So no sweat yet
Select “Restore Data”
Reboot completely
Turn off phone (here is where I stopped the timer at 16.5 minutes)
Charge to 100%
Boot and enjoy.
BAM! All the old data is back. On top of the new ROM. Except for stuff that no longer applies, like maybe in-ROM launchers that no longer exist.
My ROM flashing evolution path has been:
Stock
Odin DXC DB/DO tar
EC01 DB/D0 (zip i think, can't remember)
Full ED01 (Adrynalyne method, not OTA)
ComROM 1.0 zip
Evil Fascination, all variants in sequence. Zip
EB01 SC 2.9.2 zip (Why? To see if it would work. Because it means restoring ED01 Nandroid data over an EB01 ROM. Without compromising the ROM. (Thanks for the assistance with this, Lttlwing16.)
ED01 MIUIWiz
Seems to work flawlessly so far. No forced closes, no hiccups, just sweet functionality. Every time so far. And so quick, I sometimes actually have time to use my phone between flashes.
As I said, I have been doing this for just about as long as I have been flashing through CWM. Your backup may overwrite some ROM theme elements, so that is something to think about.
Any other drawbacks? Not that I have found, but…Not completely sure yet, So… You know the drill…
DO NOT TRY THIS UNLESS YOU ACCEPT FULL RESPONSIBILITY AND ARE PREPARED TO DEAL WITH THE CONSEQUENCES!! YOU MAY LOSE DATA OR FUNCTIONALITY!! YOU MAY EVEN MANAGE TO BRICK THIS THING!
But you just made a complete clean-wiped Nandroid Backup, right? So you can always restore the whole thing. Or worst case, do the Odin recovery method. (or even worse case, Heimdall).
I suspect that there is some reason that this method has not been widely promoted already. It seems unlikely that it has not been experimented with, so maybe someone can help show a newbie the error of his ways. Or we may need someone with a thorough knowledge of Fascinate ROMs to add some warnings, caveats, or guidance around potential problems, etc. But it does seem to work just fine for me, and all of the ROMs I have worked with seem smooth and stable. All my apps always work, and update properly. Unless I get stupid and screw something up.
It does seem that Android should be able to pull this off if sufficient attention is given to file structure and dependencies, and if everything data can be kept where a data only restore would look for files. I suspect that I have been having success because of the good work of all the great ROM builders and developers working to fix the Fascinate, and make our experience all that it is. So if this works for you, they are the ones that really deserve the credit and the thanks. They made it work. I just followed instructions, got curious about Nandroid Advanced Restore, and pushed the right buttons. Oh, and wrote it all down.
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Well, I am expecting to learn something from posting this. So thanks. However, it raises more questions for me.
Does it mean that I never have actually needed to wipe data? I could have flashed all those ROMs without wiping data and without issues?
My understanding was that at least the cache would be re-written as needed by the new ROM, rather than trying to work with data created by the old one.
It sounds like it means that if bringing back the old data works, keeping the old data would have worked, too. So even Dalvik could have been left every time?
My thinking was that cleaning the cache and Dalvik before making the backup would mean that when restoring, they would come back blank, and not confuse the new ROM. I was under the impression that something was more likely to go wrong if all that stuff was left in there, and it was safer to bring it in later, after the ROM boots up, and give the new ROM a chance to properly recognize and deal with it.
Is there any logic in that logic? Just asking, because I really don't know. It sounds good.
If not, this thread is for educational purposes only.
But dang, either the Devs are even more awesome than we thought, or I must get lucky a lot. Because I have flashed quite a few ROMs without issues, force closes, etc.
Interested in more feedback on this process.
OK, I did have a couple of FCs of Gmail this last time flashing MIUIWiz, going from EB01 to ED01. It seemed to fix itself after I closed it twice, but I updated Gmail anyway. No repeats.
I have a new preferred method of backing up, cleaning the files, flashing new ROMs and restoring my data. Flashed MIUIWiz 111 over EF 360, the whole process taking about 10 minutes altogether plus navigation and boot time.
(Always create a clean Nandroid Backup (with wiped cache and Dalvik, possibly voltage) 4-5 minute process, not included. This should ensure that the new ROM will create its own compatible cache data after the restore.)
1. Run navenedrob's reformat utility [UTILITY]EXT4/RFS Formatter (CWM3 recovery packages) - xda-developers as a CWM zip from sd card <1 minute process.
2. Flash the new ROM in CWM <1 minute process.
3. Flash new Kernel if needed (before allowing ROM to boot) in CWM <0.5 minute process
4. Allow ROM to boot (3-4 minute process)
5. Nandroid Advanced Restore in CWM (Data only) (3 minute process)(Restores all User Data and apps)
From navenedrob: “Understand that this [format utility] will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device.” But it also puts things back in order if they have gotten screwed up. This could be the solution to issues you are having. Thanks, navenedrob! Very cool.
If there are particularly desirable user setups in the flashed ROM, be advised they may get lost in the restore.
The only issue I seem to have is the need to update/install Gmail. Then all is smooth.
Works for me, but you may totally bork yours. You are responsible for what you decide to do.
times_infinity said:
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think that means wiping data also wipes Dalvik. So Dalvik wipe is redundant when wiping data. Good to know about the partition info. Seems to support the idea that wiping Dalvik before making the backup would ensure that when the restored data is brought back, it brings no Dalvik data with it, avoiding potential issues with the new ROM.
This is basically identical to this thread:
http://forum.xda-developers.com/showthread.php?t=2402021
It is posted in the Nexus forum, however, and I don't know how much overlap there is between the users of that forum and this one, so I wanted to ask it here since I'm using an S4.
Basically, when ever a ROM that you're using comes out with a major revision, the expectation is that you do a clean install and wipe all data. This can be quite a hassle when it comes to restoring everything when you boot back up. Especially if it's an active ROM and you find yourself needing to do this monthly. I personally have been using Titanium Backup to restore user apps, but I don't use it for system apps as I presume some of that data might be incompatible with the newer revision of the ROM and I don't want to screw up any of the benefits that the update offers me. However, this still leaves a lot of system settings non-restorable and I was wondering what the experts on here did to minimize the complication of restoring all of their settings after their wipe their device for a software update. For example, Ringtones, WiFi/Bluetooth settings, system application options/settings. Does anyone have a good method to simplify this process of getting your phone back to exactly the way it was prior to the update or is it mostly just a tedious process you put up with every month or so?
Thanks.
The issue:
I upgraded to Jelly Bean 4.1.2. Eventually (within hours) I was unable to open the Gallery to view photos; the error message: "Not enough space. Delete unnecessary items such as downloaded software, pictures, videos and documents"; screen shots cannot be saved to the internal memory; images from within MMS messages cannot be viewed; neither Kies or TitaniumPro will allow me to perform a backup.
After attempting to "Clear data" (successful) and "Clear cache" (unsuccessful; cache remains full after hitting radio button) from Application Manager --> All --> Gallery, I noticed that my cache supposedly contains 88.17GB of data, which is WAY more storage than my phone has available. I went searching for these files, and their location is /sdcard/Android/data/com.sec.androud.gallery3d/cache.
Assumptions (and we all know what those do...):
-If I'm able to delete these files, it will solve the aforementioned issues.
-This is as a result of the auto-syncing of photos within my Google account; I believe this is supported by the fact that I was initially able to open the gallery post-update, but as the files continued to sync and the cache got too large, it disallowed my opening of the gallery.
-Other folks have had similar issues, and a factory reset did not resolve their problem (so it won't resolve mine).
Attempted fixes:
-I disabled syncing Picasa and photo albums from my Google account.
-In addition to the offending files (a parent folder and files named with symbol/wingding characters; many of the files supposedly contain 3.5GB worth of data... totaling the 88+GB of data), I was unable to delete anything from within the cache folder (which included Picasa folders) in MyFiles. As a result, I rooted my phone with Framaroot 1.6.0, enabled Root Explorer in ES File Explorer and changed all the permissions available to RW and restarted the phone. The files still "cannot be deleted".
Please help.
Phone info:
Samsung Galaxy SII i777
Android version 4.1.2
Baseband version I777UCMD8
I don't want to make any assumptions before I offer suggestions. So...
Did you upgrade via Kies?
What kind of experience do you have modifying phones, if any?
creepyncrawly said:
Did you upgrade via Kies?
What kind of experience do you have modifying phones, if any?
Click to expand...
Click to collapse
I did upgrade via Kies. I've little experience modifying phones, but I'm willing to put in a little leg-work to figure out how. If I could save my SMS/MMS messages and phone log in this process, that'd be great. That said, I'd rather put off buying a new phone, so I can live with it if I lose the data.
I'm not sure what went wrong with the Kies update, but as far as I know, there is no easy way to correct the problem. Actually, most of the people who frequent this forum are using custom firmware, rather than stock. In general, when things go wrong with a flash, (or update in your case), it is much easier to just re-flash. Of course, if you are an experienced developer, you can look at the log files and determine what went wrong, but even then fixing it is questionable.
You will most likely find that if you perform a wipe data/factory reset in 3e recovery and then perform a fresh Odin install of the firmware, you will have no problems. You can stay with the stock 4.1.2 UCMD8 firmware, or you can install the custom firmware of your choice. If you opt for custom firmware, there are a number of choices. Since you are accustomed to running stock, you may be more comfortable with a rom that uses Samsung Touchwiz as a base rather than one that is based on the Android Open Source Project (AOSP). I run SHOstock3 which is modified from the latest Samsung firmware for the International SGSII and is also 4.1.2 based. It is extremely stable and has many many features that you do not have with stock.
Since you are rooted, you should install Titanium Backup and do a complete backup of all your applications in it. You will then be able to restore application data so that you don't lose anything. With it you can also restore your SMS & MMS messages, and possibly wifi access points, call logs, and bookmarks of the stock browser. I'm not sure about the last three if you would be changing to a different base. I think the call log would restore from stock to SHOstock3 since they are similar applications.
If you will be flashing firmware in the future, you should consider purchasing Titanium Backup Pro, which gives you batch restore along with some other features. It is very tedious restoring things one application at a time.
Also, before you wipe and re-flash firmware, you could first install a custom kernel and do a nandroid backup. Titanium Backup will read and can restore things selectively from a nandroid backup so you would have access later to additional items if you need them.
Hope that's helpful and if you have any questions, just ask. You can find a lot of resources in my signature, including a link to the Download Repository.
Oh, and the call log is not your address book. Titanium Backup will not restore that, but you can save it in Google and restore it from Google which is what most people do, or I believe you can find a stand alone backup program for it.
Simple Solution:
1. Download your current ROM .zip file -- in my case ShoStock3 4.0 zip
2. Reboot into Recovery Mode
3. Locate your zip file -- in my case extSD card
4. Run your ROM .zip file -- no need to do a full wipe or anything.. Just run the zip file
5. Reboot once the installation finishes
6. ENJOY!
YEAH! to my first post!
Hi guys!
I've been fiddling around with different ROMs. With every new rom I install, I always wipe data/factory reset, wipe cache + Dalvik cache.
However, it seems there still are files lingering from earlier versions (eg. wallpaper settings).
Is it possible, and if so how, to do an ultimate reset, to make the phone as bare as possible before installing a new rom?
I've tried using CM recovery, TWRP, CWM, and others based on earlier mentioned recoveries. Right now I'm running the latest Candy 5 (infected) + CWM
It's not quick but if you encrypt before wiping it that is one way. I've always reccomended doing this when selling your device.
Sent from my D6503 using XDA Free mobile app
usually I do a full wipe with TWRP (go advanced wipe and check everything including internal sdcard), this will wipe everything you have on the phone like pics and other stuff, so make sure TO COPY THEM FIRST, the are not included in a nandroid backup, had to learn that the hard way
There's no better wipe then what you do (except formatting sd card).
I think the settings that stay between flashing are the one restored by your Google account.
Uncheck backup / restore from Google settings next time you install a rom and it should be all new !
pec0ra said:
There's no better wipe then what you do (except formatting sd card).
I think the settings that stay between flashing are the one restored by your Google account.
Uncheck backup / restore from Google settings next time you install a rom and it should be all new !
Click to expand...
Click to collapse
I'm quite sure it's more than just the google back-up files lounging around, but I'll make sure to try and set it up as a new phone next time around. Thank you for your help
munte89 said:
I'm quite sure it's more than just the google back-up files lounging around, but I'll make sure to try and set it up as a new phone next time around. Thank you for your help
Click to expand...
Click to collapse
If you mean files that are on your sd (internal or external) they are not Google's backup but have no big effect on your settings (except for some apps). If you want to get rid of this, just format your sd.
Now if you mean some settings like the wallpapers, they are restored by Google automatically but the setting is stored on the data partition (which you wiped).
Do you have other examples of things that stay between wipes?
pec0ra said:
If you mean files that are on your sd (internal or external) they are not Google's backup but have no big effect on your settings (except for some apps). If you want to get rid of this, just format your sd.
Now if you mean some settings like the wallpapers, they are restored by Google automatically but the setting is stored on the data partition (which you wiped).
Do you have other examples of things that stay between wipes?
Click to expand...
Click to collapse
Nothing that comes to mind, only the reoccuring feeling of "Huh? That shouldn't be there anymore". However, I'm quite sure I solved it using PhilZ to advance wipe and wiped everything but the boot.