Can nandroids be renamed? I'm getting quite a few saved up and the date code is not tickling my memory of what the set up was on that particular day. Just wondering if I rename them will they still work?
I've renamed all of mine and they work fine when I restore them. Just be sure there are no spaces in the name.
If you happen to get a md5 mismatch make sure you didn't put a space in the name, and if so remove it and use _ , -, or a .
Also, don't use an ampersand (this will cause the Nandroid restore to be launched in the background via the shell and never able to return his status to the recovery that launched it). Stick with "normal" characters (letters, numbers, dash, underscore, period, etc.) and avoid using any character that the shell might interpret as a meta character (asterisk, question mark, greater than, less than, vertical bar, semi-colon, ampersand). This is because your custom recovery will launch the nandroid-mobile.sh script to a shell and pass its arguments and parameters that the shell will interpret and possible take action against that you didn't anticipate. Also, be sure to not rename the folder name above the Nandroid backup directory. This will be your phone's serial number and custom recovery won't be able to find your backups if you rename it (you can always rename it back to its proper value if you need to). Cheers!
Edit...I tried renaming that same type of folder, I left the original name and added to the beginning of it so it looked something like this... abcd-abcd-abcd-10-26-2012-34.96.37 I got the same as you say in the post below this one???
Odd. When I renamed those I got md5 errors. I had no spaces. Either it was my error or Fission somehow jacked them up. I'm not positive.
I've named mine "ApeX_RC2_BigDX_Red" "Apex_V1_Theme" etc. with no problems, I take out all the original text. Maybe it can only be so many characters?
I have a few that are named based on the date and what ROM it has running. 10-24-10-Apex-OC1.35 This is the name of my Apex backup that I made on 10-24 that is overclocked at 1.35GHz. I've restored it and it works fine.
Lol! (as always!--these forums wouldn't be the same without jreed ) By the way, my post above came from researching how nandroid-mobile.sh works when invoked by Amon_RA's custom recovery, specifically on the HTC Droid Eris. I have yet to find the source for Koush's ClockworkMod even though I've seen references saying its open source. edit: I do see that Koush's ClockworkMod source is available in the CyanogenMod source tree...I'll grab a copy and update this thread when I get a chance... But, I assume that nandroid-mobile.sh script is probably invoked in the same manner for either recovery (albeit with different options since its known that the Nandroid backup directories contain different files between ClockworkMod and Amon_RA's). The nandroid-moible.sh script is invoked via fork()ing (yeah, that's right ) /sbin/sh with a command of /sbin/nandroid-mobile.sh -r -e --norecovery --nomisc --nosplash1 --nosplash2 --defaultinput -s <backupdirname> where <backupdirname> is the name of the Nandroid backup directory selected via custom recovery. So, you can see that passing a <backupdirname> containing spaces or other meta characters such as an asterisk, ampersand, etc. will potentially cause the nandroid-mobile.sh script to not be able to properly identify and operate against (i.e., restore). Also, the nandroid-mobile.sh script itself uses the backup directory name passed from recovery and does a RESTOREPATH=`ls -trd $BACKUPPATH/*$SUBNAME* 2> /dev/null | tail -1` which certainly would fail should certain meta characters be present in the SUBNAME variable (which is populated with the -s <backupdirname> name from custom recovery. These assumptions might not be correct for ClockworkMod, but then again... Cheers! edit: by the way, the full path name for a Nandroid backup using Amon_RA's recovery is /sdcard/nandroid/<device serial #>/BDS-ccyymmdd-hhmm and contains the system.img, boot.img, data.img, and nandroid.md5 files. The <device serial #> directory is the serial number of your phone (don't publish that here since it uniquely identifies you and your phone) and must match your phone's serial number in order for custom recovery to find it (i.e., you don't want to rename this directory). So, you should be able to rename the BDS-ccyymmdd-hhmm directory name (or whatever format ClockworkMod uses) as long as you stay away from meta characters that might be interpreted by the shell.
Somebody ate their wheaties this morning. Seriously though even tho I comprehend most of what you just said, it still makes my brain hurt. Especially in the am.
Figured out my issue...I had an extra space before the beginning of the name that I did not see until I went to remove the additional naming. I think it was an autospace from swype I didn't catch while editing. It looked something like this... " Apex-nextheme-noclock-2010-10-26.15.42.59" Removed that space from the front and they now work just fine. I also added folders within "backup" and moved renamed backups to them. "Original", "Themes", "ROMs". They all work now. Thanks again Ladies and Gents.
I take this back, the folders do not work properly. When I boot into recovery, got to restore, and go to my "ROMs" folder, it does not show me the multiple options within...just immediately goes to the restore confirmation screen without letting me select which of the 2 folders contained in "ROMs" to restore. I did not hit yes as I did not know what would happen, so I've removed the extra folders and am sticking to my naming convention, I'll be able to figure it out well enough.
Oh, you created subfolders under the main Nandroid backup directory? Sorry, didn't catch that before... Yeah, I don't think "they" (custom recoveries) will like that (but you know that now, eh? ).
I renamed mine through root explorer, just make sure your keyboard doesn't add spaces automatically, that's how mine messed up a couple of times.
