• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root renameing Backups

cammykool

cammykool

Android Expert
can i rename my backups because i synced stuff to the 222ov backup that was posted here as stock and i edited it a little syncing my stuff and before i restore to ICS i want to backup and rename saisd backup can i?
 
If you are talking about nandroid backups the no. I believe it messes up the MD5 checksum rendering the backup file useless.
 
riggerman1 said:
No it doesn't, I rename all the time to prevent confusion as to which one is what.
Click to expand...

Maybe I am wrong, I actually haven't tried it. I had read about it somewhere on here. Hmmm, I guess I give it a go this weekend and see what happens, lord knows I have plenty of useless nandroids lying around.:rolleyes::D
 
Yes you can rename a backup. I do it all the time. Since the pertinent files that are used in the backup/restore are placed in a folder (/sdcard/clockworkmod/backup/"Name of Folder") all your doing is changing the name of the folder.
 
So far i've got 3 backups, my original rom, BACKside, and ICS. I renamed them all except ICS and so far I have had no issues with reloading BACKside after renaming and been on ICS. It makes it easier to keep up with, thats for sure.
 
Just open nandroid.md5 file located in the backup folder with text editor and you'll see the answer.
 
I have renamed backups from CWM of the BACKside ROM.
It would not restore any backup I renamed. I no longer rename the backups and just create a new folder with the name I want and move the backup there.

Would be easier to just rename the actual backup, but has not worked for me when trying to restore.
 
If it helps to make reading the name of the backup easier, you can use a period in place of a space. That's what I do.
 
DO NOT TRY THIS IF YOU DON'T COMPLETELY UNDERSTAND IT!!!

If you get an md5sum error when attempting to restore a backup, you can open the md5 file in the backup folder, and edit it with proper md5sums for each backup img.

This is dangerous. You shouldn't have an issue with md5sums, but nothing is perfect. ;)
 
I don't think fixing md5 sum itself is dangerous. Bad image is a bad image regardless of md5 sum. md5sum doesn't verify the image against the source, does it?
 
You must log in or register to reply here.
Back
Top Bottom