Hi.
So i decided to create the nandroid backup through ROM MANAGER. Before proceeding i selected the external SD as the backup storage from settings. I proceeded with creating backup which seems perfect and i went ahead and wiped my phone to install another custom ROM. Now i wanted to restore my nandroid backup and i tried to do that with ROM MANAGEr. Unfortunately rom manager gave "Md5 checksum mismatch" error. I checked my external SD and found out that the backup i created with ROM MANAGER for some reason was created in backupdate \ 01 \ 13 subfolder and this is the reason i cannot restore. I tried moving the subfolder "13" to the backup root but still get same error.
Now what can i do to restore my backup? I do have titanium backup of my apps thats not an issue, i just forgot to make contacts backup. Plus this will be helpful in the future if anyone knows the answer. I have no idea why the backup was created in second sub folder, this is not usually the case when done through CWM.
Any help is appreciated.
yusufjee said:
the backup i created with ROM MANAGER for some reason was created in backupdate \ 01 \ 13 subfolder and this is the reason i cannot restore..
Click to expand...
Click to collapse
How do you know that?
I'm sorry what? Do you use CWM 6 (like any CWM 6 version before 6.0.2.x?). If so, you've probably backed up with the blobs method instead of the previous default one (tar method). The tar backup method was once again made default in 6.0.2.x because the blobs thing was too much of a headache for most people.
I solved the problem by moving the contents of the subfolder to the main DATE folder.
Thread is closed...
Related
I'm curious about this. Maybe someone can enlighten me.
Lets say that I'm on stock 2.2, rooted. I do a nandroid backup. Then I allow the upgrade for 2.2.2. Of course I lose root.
Will a nandroid restore, restore root, or will I have to root again?
A full nandroid restore will restore everything - the system and data - and you will be right back where you were, on 2.2 and rooted.
maltloaf said:
A full nandroid restore will restore everything - the system and data - and you will be right back where you were, on 2.2 and rooted.
Click to expand...
Click to collapse
Ahh, okay.
So to confirm that I understand you correctly...
...the 2.2.2 update won't hold after the nandroid restore? I'll be back to 2.2, as it was before the (2.2.2) update?
If you just wanna backup and restore your apps, use Titanium Backup (it's free on the Market).
Nandroid backs up your entire phone. When you restore a nandroid backup your phone will be exactly like it was when you made the backup. Restoring a nandroid backup is used to recover from a crash or to revert to a previous ROM.
After a ROM change I will set up my accounts, root if needed and do any other basic setup stuff and then, before installing any apps, do a nandroid backup. I can then go back to a "fresh install" if I want to. I also do a nandroid each weekly to capture the state of my phone.
Backing up apps and restoring them across different ROMs may or may not work for you. When I have tried this with Titanium Backup I had many force closes and ended up reinstalling everything from the market. Others have had success. I have read the MyBackup pro does better, but most suggest that you just backup and restore data not the app itself.
I have not tried backing up my apps to Google, which you can do in later versions of Android. Go to Privacy in the setting menu and then to Backup and restore. There are boxes for data backup and automatic restore you can check. maybe someone who has used this can comment on how well it works.
If your nandroid backups hang up at "backing up firstboot" get the latest version of StreakMod Recovery.
marvin02 said:
Backing up apps and restoring them across different ROMs may or may not work for you. When I have tried this with Titanium Backup I had many force closes and ended up reinstalling everything from the market. Others have had success. I have read the MyBackup pro does better, but most suggest that you just backup and restore data not the app itself.
Click to expand...
Click to collapse
After installing a fresh ROM and rooting my device, the first thing I do is install Busybox. Then, with Titanium Backup I do Restore Apps Only, then reboot my device. I never get any FC's with this restore process.
Thanks!
Thank you everyone. I appreciate the info.
I've used Titanium BU, and have busybox installed too.
It was just a matter of if after an update (OTA), and restore with Nandroid, would root still be in place.
I totally understand what you guys are saying now.
I've also been using MyBackup to see how it compares to Titanium. So far so good.
~X
I prefer mybackup root to titanium. It's far more user friendly and more automated (in the free version). As for nandroids, I always take a backup before doing any system changes (hacks or rom updates) so I can roll back to a known good system if needs be.
BTW - it is a good idea to copy your ROM backups to another device, just in case your SD card dies. I copy mine to one of my desktop computers and to a USB drive. I usually back up my entire SD card, except my music folders, every couple of weeks.
Where does Nandroid put the backups so I can rename them and save off phone?
mine (from Streakmod recovery) are in /sdcard/rom_backup
StreakMod recovery puts the backups on the SD Card in a folder named rom_backup.
Each backup is in a sub-folder of it's own and uses a date-time format for the folder name. I rename the folders with a meaningful name by just pre-pending to the name. So my last backup is named BB351-2011-06-18-02.41.04. The following files are created:
.android_secure.img
boot.img
cache.img
data.img
firstboot.img
recovery.img
system.img
nandroid.md5
the md5 file is a text file that contains the md5 sums for the other files. This file is used to verify the other files when they are restored.
Hey all. I wanted to know if it was ok to change the name(s) of my backups in my CWM file from my PC. I'm not a fan of ROM manager and usually do my backups via CWM but it names it by date/time and when I get home I'd like to rename it so I can remember which darn backup it was.
If you rename nandroid backup that was created by CWM, you might get some MD5 errors when restoring that backup.
What you need to do is use ROM Manager for backup, and when you select "Backup Current ROM" you can name your backup and it will be fine.
Next time, use the Search
I found the answer here: http://forum.xda-developers.com/showthread.php?t=623348
ofek said:
If you rename nandroid backup that was created by CWM, you might get some MD5 errors when restoring that backup.
What you need to do is use ROM Manager for backup, and when you select "Backup Current ROM" you can name your backup and it will be fine.
Next time, use the Search
I found the answer here: http://forum.xda-developers.com/showthread.php?t=623348
Click to expand...
Click to collapse
Sorry, but I did search and the only problem I read about was you couldn't put a space in the new file name. I just renamed my 2 backups and restored with no MD5 errors. I just wasn't sure with the newer CWM version.... Thanks for the reply though.
Phoneguy589 said:
Sorry, but I did search and the only problem I read about was you couldn't put a space in the new file name. I just renamed my 2 backups and restored with no MD5 errors. I just wasn't sure with the newer CWM version.... Thanks for the reply though.
Click to expand...
Click to collapse
I have been renaming my backups with spaces with no problem. i think its a little weird that you might have an issue if you were to rename them with a space
Hi guys,
I know there are several threads on this topic, but no solution worked for me.
Yesterday I made a nandroid backup and everything went fine. Than I installed MiniCMSandwich, which works very great. But then I wanted to restore my old backup and got a md5 mismatch.
I tried this and this method, but they didn't work.
In my backup folder are only these files:
data.yassf2.img
system.yassf2.img
.android_secure.vfat.tar
There is no nandroid.md5 or any other file
What have I got to do to fix my nandroid backup?
By the way, I didn't rename it!
Please help
Michi
Ok Terminal Emulator method worked after trying a bit, but now I've got another problem! I created a new thread for that
You could have made new backup and replace the data and system stuff...? Or it might not work?
OK could you explain that pls? What exactley have I got to do.
I tried to take system and cache out of another backup before and put it in the (bricked) backup folder instead of the system and cache of bricked up. Then I tried the terminal method again, but theres md5 mismatch!
What have I got to do?
But... if you have an older backup, couldn't you just restore that one? Just saying.......
Feanor88 said:
But... if you have an older backup, couldn't you just restore that one? Just saying.......
Click to expand...
Click to collapse
Yes I restored it and it works fine, but that was a backup immediatly after the ics update and all apps installed. There are no settings from apps, etc. Can I restore Data and Apps out of my old Backup? Is there an App?
What I can say for sure is that you cannot "mix" files from different nandroid, and that's because of the md5 checksum itself. If you mix the files, you'll always get an error.
I'm sorry, but I don't know if there's a way to "extrapolate" your apps and settings from another nandroid. Think you'll have to reinstall all your apps
Titanium Backup Pro can extract apps with data from Nandroid backup.
Someguyfromhell said:
Titanium Backup Pro can extract apps with data from Nandroid backup.
Click to expand...
Click to collapse
Yeah, I just found out... while updating TB I was reading the notes, and there it was, written in front of my eyes!
I'll root my S3 and then will install a custom ROM, do I need to backup my existing ROM or I can flash it back by downloading it via the forums?
you can either:
-back it up with cwm recovery(making a nandroid backup) so that when you restore it,it restores to the way it was when you made a backup
or
-just flash a custom rom without making a backup.(Note:you can restore it to stock using the stock roms flashable available but you would have to set it up again like you do when you factory reset.)
Lither said:
I'll root my S3 and then will install a custom ROM, do I need to backup my existing ROM or I can flash it back by downloading it via the forums?
Click to expand...
Click to collapse
Always make a full nandriod (use the toolkit) backup of your own ROM, a stock ROM won't restore your the efs folder and, if it gets corrupted during ROM installation can't be recovered.
backup your efs
in cwm, a nandroid backup is simply labelled as back up. it'll be in a zip file in the location of your choosing when it's done or in the cwm folder labelled by the date and time it is backed up.
Sent from my GT-I9300 using xda app-developers app
mputtr said:
in cwm, a nandroid backup is simply labelled as back up. it'll be in a zip file in the location of your choosing when it's done or in the cwm folder labelled by the date and time it is backed up.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your quick reply !
It should work like that and even more hoped it would work like that !
Instead of a .ZIP file, I get 3 directories under /sdcard0/ClockWorkMod : these are BACKUP, BLOB and DOWNLOAD.
On every backup, there is indeed a directory created in the directory BACKUP with the current date as name (like "2012-11-04.23.27.05").
The data in there can never be a full nandroid back, as it's only 18 MB (yes megabytes).
Here is a listing for example : (size filename)
> ..
8.388.608 boot.img
811 cache.ext4.dup
1.479.801 data.ext4.dup
237 nandroid.md5
8.388.608 recovery.img
289.833 system.ext4.dup
18.547.898 bytes
Notice the file extentions .DUP and their size for cache.ext4, system.ext4 and data.ext4.
I guess the real data must be distributed in the BLOG directory with it's > 2500 sub-directories and taking up 2.7 GB space.
The directory download contains some strange named files :
> ..
6.182.912 -1032133489
157 -1046604230
6.180.864 -1582411299
60.826 -2110140792
907 -750693690
4.846 102398884
2.263 1306009840
73.462 1487533053
630 386293678
9.153 426056750
747 488289109
12.516.767 bytes
Filenames are "random" numbers and all together only about 12 MB
I suspect it has to do with ROM manager, do you have ROM manager installed ?
The problem is that the only backup I have are these, so I can't just trash ROM-manager because I'm unaware of any other tool that is able to handle these backups.
What version from CWM recovery is displayed when a backup is started ?
weird... this is what it looks like in my nandroid back up folder....
it should look like this.
EDIT: i used CWM app to run the backup from the OS, but recovery should be the same
Sent from my GT-I9300 using xda app-developers app
So if I didn't make a backup and wanted to restore back to JB, I will have to setup everything again?
a backup is only there to "restore" you to the point that you made a backup. think of it as a failsafe.
EDIT: yes, if you did not make a backup, you'll just have to flash a stock rom of choice (assuming you're going to stock) and set up everything again (contacts, apps, messages, etc)
the current CWM has 2 options when backing up the files.you can either choose TAR or DUP.default setting is dup.DUP saves more space when you make multiple backups as it stores the core files in the blob folder and only updates the different file when you make a different backup.if you want independent backups,set it to TAR in CWM recovery>backup and restore>choose backup format.
LaZyDood said:
the current CWM has 2 options when backing up the files.you can either choose TAR or DUP.default setting is dup.DUP saves more space when you make multiple backups as it stores the core files in the blob folder and only updates the different file when you make a different backup.if you want independent backups,set it to TAR in CWM recovery>backup and restore>choose backup format.
Click to expand...
Click to collapse
Thank you !
That must be why I could never make a single "stand-alone" NANDROID backup from my SG3 !
To eliminate any interaction from my ROM Manager, I uninstalled it using Titanuim Backup, as I've seen some posts saying that ROM manager doesn't work well with Sammy's, but I don't know for sure.
After rebooting, I went manually in to CWM recovery (the 3 button trick) and created a backup on my external SD card. (not on phone memory).
This is what I got :
An extra directory with current date as name was created under /mnt/extSdCard/ClockWorkMod with the files :
boot.img
cache.ext4.tar
cache.ext4.tar.a
cache.ext4.tar.b
data.ext4.tar
data.ext4.tar.a
nandroid,md5
recovery.img
system.ext4.tar
system.ext4.tar.a
system.ext4.tar.b
Total space occupied : 1.8 GB
Is this the "expected" output from a "backup" (I wanted a nandroid backup) from CWM ?
It seems that some .TAR files are 0 bytes and 2 files are then generated : one with a .TAR.A and one with a .TAR.B.
The file system.ext4.tar.a for example is is exactly 1.000.000.000 bytes, de rest is in system.ext4.tar.b
Note that I'm using the "Touch version 6.0.1.2" from CWM recovery (see method here by mskip (author from "The Toolkit v6.0 for SG3)"
Is this a so called "standard" NANDROID backup ?
Can this completely restore my SG3 to it's current state including all apps, settings,.... ? Obviously I can do a restore using CWM recovery (t least I hope so, but also using "The Toolkit" via it's ADB commands ?
Further, I'm also asking myself about keeping on to use ROM-manager or not, any experiences on SG3 with it (good and bad please) ?
When I try to recover my apps using Titanium Backup's "Extract from Nandroid" feature, it says "Could not find any data in this TWRP backup"
The files in my TWRP backup folder are
data.ext4.win000
data.ext4.win001
data.ext4.win002
md5 for the above
recover.log
Any help would be appreciated
Yup, same problem here. Im on a Galaxy Nexus running XenonHD and TWRP.
I've tried unpacking them on my pc, so i could use an emulator and run my phone through there.
That kinda works, and using Titanium Backup, it seems to extract it without an error. But afterwards, the app is very glitchy.
Im guessing Titanium Backup doesnt really do well on TWRP as i had no problems using clockworkmod.
I'm experiencing the same problem running Marshmallow trying to restore apps from a TWRP backup (Galaxy S4). At first, Titanium backup just refused to even see the backup files (although it accepts the containing folder as a backup location). Once it finally and magically accepted to see the backups it now tells me that it cant find any data in them...
Has anyone solved this yet?