As I root, I see all of these terms that I don't understand. I just generally follow steps of how to do some of the rooting methods. On Amon's recovery, I was wondering what BART is. What is the difference between BART and a regular Nandroid backup? What is a Nandroid + ext part mean?
I tried to google these terms and am still unsure about them.
These commands are used for backing up your phone's data to be restored if something bad happens.
I know the difference between "Nandroid" and "Nandroid + ext" is that the +ext will also backup the "ext" partition of your sd card, for if you're using apps2sd.
Bart is another type of backup but I'm not sure the specific differences.
BART = Backup And Restore Tool.
My explanation may be a little...weak... so, I'd also suggest looking here:
forum . xda-developers . com/showthread.php?p=4569600 (Still too new to be allowed to post URLs, so remember to remove spaces).
BART allows for you to store backups and name them while allowing for multiple backups. Furthermore, the backup can be tweaked (at time of creation) to include/exclude/modify (such as deleting dalvik cache) aspects of the backup.
Again, my understanding/explanation may be unpolished. Hopefully it's provided some insight, however.
Related
I don't have any partitions and I'm not even sure that would be a reason to not let me backup. I can run Nandroid backup fine but I can't run Nandroid backup +ext.....Can Someone please help!
Thanks
Robotnoize
tweet me @robotnoize1 if possible...thanks!
I've had this problem before when I rename the nandroid file.
I usually power off, go back into recovery, and it works.
Not restore but backup.
robotnoize said:
I don't have any partitions and I'm not even sure that would be a reason to not let me backup. I can run Nandroid backup fine but I can't run Nandroid backup +ext.....Can Someone please help!
Thanks
Robotnoize
tweet me @robotnoize1 if possible...thanks!
Click to expand...
Click to collapse
You have no partitions so backup + ext does not apply to you. That is the default error when the script doesn't detect an extX partition to backup.
okay.
Exactly, an ext partition is for the apps to sd technique which you are not using, so there is no need for an ext backup, a normal nandroid is just fine
And my apps messages etc. will all be backed up?
well it's time to try it now I guesss!
Thanks for the help guys very much appreciated!
I do believe you messages will be, however your apps will not! but a simple visit to the android market and then to your download tab will bring up your list again Otherwise just create an ext partition and do a nandroid+ext backup and that will save your apps.
Correct me please if im wrong, but hasnt the RA recovery been having issues with ext backups on cyangen?
sassyness77 said:
I do believe you messages will be, however your apps will not! but a simple visit to the android market and then to your download tab will bring up your list again Otherwise just create an ext partition and do a nandroid+ext backup and that will save your apps.
Correct me please if im wrong, but hasnt the RA recovery been having issues with ext backups on cyangen?
Click to expand...
Click to collapse
You are wrong.
Nandroid does backup the whole phone, everything under "/". By everything I do mean everything on the phone storage.
also, make sure it is fully charged before trying to restore.
Hi All,
Sorry, I got a pretty silly n00b question... but is Titanium Backup or any other backup/restore app needed, if you just do a backup/restore from the ClockworkMod Recovery too?
Thanks
Sam
A recovery backup doesn't cover the apps you've installed, so without Titanium or the like you'll need to restore them manually.
toysturnaseraphim said:
A recovery backup doesn't cover the apps you've installed, so without Titanium or the like you'll need to restore them manually.
Click to expand...
Click to collapse
This is wrong.
A Nand backup (recovery backup) through Clockworksmod DOES backup your apps. In face, it backs up EVERYTHING you have on your phone, aside from you SDcard. It makes a copy of your entire phone exactly as it is when you make the backup.
When you make a nand backup, be sure to mount your /system and /data beforehand or you could run into trouble. Likewise, mount your /system and /data when restoring.
As already stated, a recovery backup creates a full backup of your phones internal files.
Titanium backup should also be used.
Titanium is useful for backing up apps but more importantly it backs up your app data. This is a great feature if you change ROM's often as you can quickly restore your app data, thus restoring game scores, settings, etc.
You can also use Titanium to revert to older versions of apps should an update cause problems.
snowblind64 said:
As already stated, a recovery backup creates a full backup of your phones internal files.
Titanium backup should also be used.
Titanium is useful for backing up apps but more importantly it backs up your app data. This is a great feature if you change ROM's often as you can quickly restore your app data, thus restoring game scores, settings, etc.
You can also use Titanium to revert to older versions of apps should an update cause problems.
Click to expand...
Click to collapse
Very useful information I left out.
ah, thanks, so let's say I have a application that requires a activation code, and I switch from Fission to Liberty or whatever ROM, once switched, I can use Titanium Backup to restore my app, and I won't need to reactivate?
Thanks,
Sam
This is probably a really dumb question but how do I use the backups I've created?
When I flash a ROM that I don't like and I try to restore to an earlier backup I've created it is not working. It either says something about the MD5sum or just aborts in general...
What process do I take in order to restore the phone to an earlier backup?
And better yet, if I install a new ROM and don't want to go through the process of installing all my apps again is there a way to just restore my files from a backup?
You can do an advanced restore and restore only data to get your apps, etc. back. There is also titanium backup that is great for backing up and restoring between roms (the only way to restore apps when using a different rom... restore data from one rom onto another can cause serious issues).
If you're getting MD5 sum errors, the backups are being corrupted. So unless your messing with them on your sdcard, then there may be some bad areas on that sdcard and it might be time for a new one.
danaff37 said:
You can do an advanced restore and restore only data to get your apps, etc. back. There is also titanium backup that is great for backing up and restoring between roms (the only way to restore apps when using a different rom... restore data from one rom onto another can cause serious issues).
If you're getting MD5 sum errors, the backups are being corrupted. So unless your messing with them on your sdcard, then there may be some bad areas on that sdcard and it might be time for a new one.
Click to expand...
Click to collapse
Wait so in order to keep my apps I can go to advanced restore and restore only data but it could cause serious issues? So basically it is possible but risky?
and normally should my restore points flash just like a rom when I go to "Restore"? do I need to wipe everything before I restore?
I did copy and paste them onto my computer so I had them in two places... maybe that corrupted them. Anyways a new, bigger, faster SD card is in the mail so that's kind of a coincidence.
a restore in clockwork is an image restore, so everything in that partition will be wiped anyways.
So I am not even a week into rooting my Evo and flashing roms and I am not sure what the best way to organize my backups are.
What do you guys do to manage all the nandroids and app backups in Titanium?
Here is my situation, I have my nandroids from right after rooting and a few from doing the two updates that CM7 had. I first did a nandroid or two using CWM, I then flashed recovery to Amon_Ra and did nandroids in their also. I also had all my apps backed up using TB post-root (sense) and now that I am on CM7 I have many different apps that I have added. I have read some people say not to backup apps from 2.2 on sense to CM7, though the few that I have done work fine.
Should I delete all the backups in TB from my stock 2.2 w sense? Can I rename my RA nandroid backup files so that I can label them better to know what they are? Or should I just move them to my computer and put them in a folder named what they are and leave the file name alone? Can I move the backup folder from TB onto my computer that has my sense backups to save for a rainy day?
I can see this getting very messy and confusing if I do not get a handle on all these backup files. Just wondering if someone has a good system for keeping track of these and when to get rid of nandroids and app backups.
Thanks!!!!
i just created folders named clock and amon ra on my computer, and inside those folders i created folders with the names of the roms i flashed with each recovery and then i moved the nandroid files from my sd card into the computer folders that corresponded, and i only left my last working backup on my phone
- clear your TB and start fresh. i would advise against trying to criss cross your Sense/AOSP backups. it may work but i'd consider it a fluke not the rule.
- you cannot restore a RA nandroid with CWM nandroid and viseversa. so whichever one you think you'll stick with...you can get rid of the others.
- yes, you can rename the nandriod folder. no spaces. very handy once you get a few nandroids going.
- i use SyncToy from Microsoft to copy all the sdcard data onto my pc. this way i can protect my nandroids, pics, vids, mp3, misc crap.
i normally leave one or two nandriods on my device (i have had a bad nandroid in the past) and zip of the current rom.
as for the deletion policy..that depends on your level of paranoia and amount of available diskspace and time.
DraginMagik said:
- clear your TB and start fresh. i would advise against trying to criss cross your Sense/AOSP backups. it may work but i'd consider it a fluke not the rule.
- you cannot restore a RA nandroid with CWM nandroid and viseversa. so whichever one you think you'll stick with...you can get rid of the others.
- yes, you can rename the nandriod folder. no spaces. very handy once you get a few nandroids going.
- i use SyncToy from Microsoft to copy all the sdcard data onto my pc. this way i can protect my nandroids, pics, vids, mp3, misc crap.
i normally leave one or two nandriods on my device (i have had a bad nandroid in the past) and zip of the current rom.
as for the deletion policy..that depends on your level of paranoia and amount of available diskspace and time.
Click to expand...
Click to collapse
Thanks, I like the idea of clearing out TB (I just did it) I was just worried removing the files would somehow mess up the TB app.
Sticking with Amon RA and I knew about not being able to use nandroids from different recoveries.
I will checkout synctoy, sounds cool, I already have three folders of my entire SD card that I made during my rooting process and changing recovery process. I hate it, I don't know what I need to keep from them.
Thanks for the input
Using GS4 I9505, and my internal storage is getting shorter shorter, day by day. almost like its vanished. i've check emulated 0 and legacy drives nothing there. but as i gethered it coz of CWM, now using twrp, uninstalled CWM but still storage isn't available for usage.
Your space is still lost because it's still allocated to CWM for nandroid backups, even though you no longer have CWM on the device. Therefore, you need to put CWM back on the device, go into its backups and storage menu, delete any existing backups it made, then free the allocated space.
When you put TWRP back on to the S4, your space should return.
He can delete the CMW folder from the storage. The backups are there and they are not hidden.
I provided an in-depth explanation of this in an earlier thread on the same topic, but in essence CWM protects the nandroid backups space so nothing else can write to that area. This is because CWM performs incremental backups by default, and deleting older restore points messes up all of them. The protection persists even after CWM is removed, so when switching recoveries, all backups need to be deleted in CWM, and all allocated space freed using the "free allocated space" option in the backup and restore menu.
EDIT: To point out the obvious, there would be no need for a "free allocated space" option in CWM if the space weren't protected.
Well, that's stupid. With TWRP I can simply go inside the folder and delete the backups (without the need of booting into recovery and deleting them from there).
Calling it stupid is a bit harsh, and besides, Koush probably will disagree with you.
By default CWM is set to do incremental backups and does this as a space-saving feature. For example purposes let's say a nandroid backup is 2GB. Using the standard .TAR method four nandroid backups would take up 8GB. Switch to .DUP and those same four backups may only take 3GB. This is because .DUP only backs up the files that have changed between the current system and the previous backups, rather than backing up the entire partition. Since CWM in .DUP doesn't back up the entire partition when making its backups, it's vitally important that the backups be protected. Otherwise, deleting an older backup makes it impossible to restore any later backups.
The example I used in my other discussion to illustrate this was four backups, labeled A through D. A is the master backup and B through D are the incremental backups. If the space wasn't protected, deleting backup C in a file manager would render backup D invalid because of missing files. Naturally, deleting backup A would render all subsequent backups invalid, as it is the master backup.
In CWM it is possible to switch from .DUP to .TAR and thus stop CWM from allocating space for backups. The OP didn't do that, which is why his space disappeared even after switching to TWRP. There may be a manual method of removing the allocation through a terminal, but it's simply easier to restore CWM, delete the backups, free the space, then switch back to TWRP.