Is there a way to edit the name of the backup files in amons recovery. and is there a way to delete the backups. any help appreciated thanks
The backups are all located in the nandroid folder on your sdcard. the first folder inside nandroid is your device's serial number or something, the ones inside that are the backups, named by date and time. im pretty sure you can renaame these folders with no harm done to nandroids restore abilities and deleting them does absolutely no harm
if you want to edit the internals, you need to unyaffs it
When i rename the back up it will never let me back up so i wouldnt do that.... i lost my backup because of this :/
that sucks
He is right.. i went into the sd card went to nandroid and tried changing the names of the backups to keep them organized and it wouldnt restore.. then i renamed them to what they were before i changed them and they restored succesfully.. so can anyone shed some light if it is even possible to rename these nandroid backups?
Im sure it is an issue with Amon-ra's program.
Go find the guy and ask him.
There is a way to edit the name and still have the backups work.
The original name is BSD-20100330-0745. You apparently need the last part for the date and such. I changed the name to EvilEris1.1 and it failed, but if it is changed to EvilEris1.1-20100330-0745 it works. You just need the "-20100330-0745". So "(name)-20100330-0745" will work.
Amon_RA said:
Renaming works fine, just don't use spaces or special characters.
Click to expand...
Click to collapse
i didnt link the thread he posted that in because i told him about this thread and dont want posts in two places. though you could find it easily im sure....
Excellent, that is better than what I had to do.
Problem solved!!!!!!!
I was just messing around with it for an hour or so and I resolved my own question.... You can name the backups what ever you want.. you dont have to have the dates or anything just no spaces in the name... so if you wanted to name it "Evil Eris 1.1" it would have to be something like this... "Evil-Eris-1.1" No Spaces...
You could also (from a computer with your phone in recovery) do:
adb shell
nandroid-mobile.sh -b
It will ask you what to name it, and then it will automatically add the suffix.
you get the "run mobile.sh" error if you rename the folder directly under the "nandroid" folder on your sd card directory. you will also get this error if your battery is low or you have no storage left. the folder directly under the "nandroid" folder it is your serial number. if you're having issues, just go to the "other" menu and select "send recovery.log to SD card." then go in and search the recovery.log file on your sdcard for "serialno=" right after that there will be a 12 character string of capital letters and numbers directly followed by lower case letters that are useless for this purpose. Create a folder with the same name as that string (capital letters and numbers only, no lower case) and place your previously renamed backups into that folder and voila! you'll be able to restore them.
burdenedreflect said:
The backups are all located in the nandroid folder on your sdcard. the first folder inside nandroid is your device's serial number or something, the ones inside that are the backups, named by date and time. im pretty sure you can renaame these folders with no harm done to nandroids restore abilities and deleting them does absolutely no harm
if you want to edit the internals, you need to unyaffs it
Click to expand...
Click to collapse
thank you, it worked for me
I'm not sure this is the correct place to post this info or my question, but I believe it is at least relevant to the topic at hand. If not, I apologize profusely.
I have numerous backups created with CWM (v6.0.1.0) that are eating up an enormous amount of space on my Galaxy Nexus SD card. I've been flashing numerous ROMs and Kernels and I want to get rid of most, if not all of those backups and then create a fresh one from my current working/bootable ROM (JB 4.1.1), just so I have a good backup to roll back to if/when I hose up my phone.
For poking around on the the SD card, I'm using a Windows-based program called 'Android Commander' (Google it), which I find to be exceptionally handy. It is very much like Total Commander, which I've been using for MANY years (since version 1.0 of the original Windows Commander) on Windows boxes, as well as a variant under numerous Linux distros.
At any rate, what I've discovered is as follows;
1. the contents of the /clockworkmod/ directory on the SD card contains three directories and a couple of files (in its root). The directories are;
/clockworkmod/backup/
/clockworkmod/blobs/
/clockworkmod/download/
2. the /clockworkmod/backup/ folder contains folders that are dated and time stamped (date and time the backups were created).
3. within each of the /clockworkmod/backup/date-time folders, there are six (6) files, the largest being the 'recovery.img' file. There is also a 'boot.img' file and four (4) other files that are quite small. Each 'recovery.img' file sizes are in gigabytes (yeah, I have a lot of crap on my phone), so it's pretty obvious that deleting these directories will give me a great deal more storage space, which is my main goal in life right now (recoup all that space).
4. my main point here, however, revolves around the /clockworkmod/blobs/ director. There are over 3000 sub directories within that directory, and I have no idea how many files are within those sub directories or how much space on the SD card they occupy, although my guess is around 8-10 gigabytes. Being an astute user of Google, here's what I found out about all this;
"Starting with version 6, duplication support has been built into clockworkmod recovery. The blobs directory folder contains a hashed directory structure that holds the duplicated files across all backups."
// This info was derived from a post on Android Enthusiasts (author unknown).
"Don't delete anything in your blobs folder. Those are your nandroid backups. Starting with CWM6, it makes incremental backups and your backup files point to the files in the blobs folder. To free up space, delete unwanted backups and the next time you run nandroid, it will delete the unneeded files in the blobs folder."
// This info was derived from a post by 'NotJustAPhone', a very senior member of the Android Central forum.
And for my next trick ... what I'm wondering is if it REALLY matters whether or not I blow away the contents of the 'blobs' directory, and I guess that's my question. What if I do delete everything in 'blobs'? Since I'm going to flash another ROM and Kernel anyway, does it matter? That directory obviously started out life as being empty, right? What will CWM do, or more importantly, NOT do, should I blow away the contents of the 'blobs' directory (assuming the file system will let me)? Won't CWM just create a new/fresh/relevant set of directories/files within 'blobs' the next time I do a backup? Has anyone actually tried doing that?
And just in case anyone is wondering, the only thing in the /clockworkmod/download/ directory is the clockwordmod img file.
Thanks in advance for any response this might elicit.
Old Fart
ImaOldFart said:
I'm not sure this is the correct place to post this info or my question, but I believe it is at least relevant to the topic at hand. If not, I apologize profusely.
Click to expand...
Click to collapse
Hi! You're in the HTC Droid Eris section of the forum, and the latest version of CWM for the Eris is much older (v2.x).
Without direct experience with the newer versions, all I can wonder is that doesn't CWM have any way built-in to delete old backups?
On the Eris, the easiest and most reliable way of using CWM is through installing the "ROM Manager" app, in which you can then manage your backups from the Android interface. In the future, you might want to consider trying that for your device as well as it may make it easier for you to manage your own backups.
I have no idea if under your configuration if installing ROM Manager now would help you delete your old backups, and I realize that even then you would probably only be able to delete them one by one, which is how it works for me in ROM Manager, and that being able to delete them en mass via Windows might be tempting. I keep four backups of my currently running ROM, and number them. I keep the very first one which is usually after I configure the ROM to my liking without really installing or restoring any apps.
Maybe you should ask wherever CWM-specific support is, but definitely at least in the section for your phone might attract better answers.
Good luck.
Related
Simple Question. Is there an easy way to rename the backups?
I use root explorer, sdcard2, nandroid and just longpress to rename
I'm living on a yellow submarine
Was wondering this myself. Its a folder that gets renamed right? Which one? I did this once before and tried a restore and it gave an error and wouldnt restore.
ftmaniac948 said:
I use root explorer, sdcard2, nandroid and just longpress to rename
I'm living on a yellow submarine
Click to expand...
Click to collapse
I figured root explorer, but wasn't sure if they would still function as backups after being renamed.
Always has worked for me.
I'm living on a yellow submarine
Pretty sure you can do it with ES file explorer or astro as well, which are free. Root is a paid app.
Yup...you can even access the backups from the PC. I would just be careful about renaming the folder that contains the backups because a new folder might get created as the file may not be recognized.
Sdcard->Nandroid->HT19X.......->(Rename these)
Hmmm
I always thought the folder name was part of the MD5 calculation, and if you renamed it, it wouldn't restore.
You can rename the folder for the backup. It is the sub folder with the date and time.
You just need to be careful with the names. No spaces and avoid special characters. Also keep them as short as possible but still descriptive
For example mine are something like
MyROM-v1.3-Final
or
MyROM-v1.3-Test
Obviously the test means a version I am testing and Final means the version I released to the forum
NilsP said:
You can rename the folder for the backup. It is the sub folder with the date and time.
You just need to be careful with the names. No spaces and avoid special characters. Also keep them as short as possible but still descriptive
For example mine are something like
MyROM-v1.3-Final
or
MyROM-v1.3-Test
Obviously the test means a version I am testing and Final means the version I released to the forum
Click to expand...
Click to collapse
Thanks for clearing that up. Wanted to make sure before trashed backups.
I know the answer is on here some where but I searched and searched and couldn't find anything. When I put the title in this post the most current thread was from 2009. So any way is there a way to rename the backup files on the phone so that it isn't the date and a few letters and numbers that I will forget what they mean in a month or two? I get a feeling with all this extra space on my sd card I won't be clearing out my backup files nearly as much as I did on the OG evo. I don't want to change a file name and lose my stock backup that I will be storing on my pc because I rename it and the system doesn't know what to do with it.
You mean the nandroid backups? you can rename them its just you can't use spaces in them, use hyphens or underscores. Nandroids all have their own individual directories per backup, rename the directory and nothing else.
Sent from my Transformer TF101 using Tapatalk 2
Thank you, I probably should have searched rename nandroid backups. If a mod needs to lock this feel free.
tl;dr `rm -rf <directory>` returns "Directory not empty"
I noticed that the old folder for Google Currents [/storage/sdcard0/Android/data/com.google.android.apps.currents] kept showing up regardless of how many times I 'cleaned it' with the app SD Maid. ES File Explorer returns that it contains 7 folders and contains 0 bytes and cannot be deleted.
Instead of letting an app handle it, I just mounted my phone with go-mptfs and decided to `rm -rf` from there. That returns "Directory not empty". There's two folders each with the same amount of sub-folders with similar names. Both contain files that are registered as 4GB with crazy characters as their name [according to my file manager]. `ls -al` won't list anything in any of the directories, but it will spit out that it can't find anything.
`rm -rf` through adb shell spits out the same error as before and Windows Explorer shows the same files with 4GB sizes. Despite the files appearing to be deleted through a file manager they still appear on the phone.
I'm completely stumped here. The only idea I've come across that makes a little sense is fsck, but I'd like to hear other ideas before I venture into unknown territories.
Ideas?
I have had I think the same issue with fders in a few occasions. For a while what I was doing was just renaming them BAD. Since it would not let me delete them. I had the same kind of issues where something in the folder would just refuse to be deleted. I THINK some part of the file got corrupted between doing something on a windows machine and my phone.
After I had a few BAD, BAD1, Etc files I finally decided to back up all my WANTED/NEEDED files and apps or whatever I had on my sdcard (internal) to a PC. This took a while with almost the whole sdcard filled. Once it was done I was then able to go into recovery and format my sdcard (internal) via cwm recovery. Then I restored all my files/folders I wanted/needed back to phone. It is the ONLY WAY I was able to get rid of it. Hope this helps ya.
Sent from My SGH-I777 Running Spiderman Themed AOKP or Spiderman Themed CM10
Thanks for the idea! I forgot about CWM's ability to format the storage it detects. I feel that may be the way I have to go, but I'd like someone to comment on the fsck idea first.
SquidLord said:
Thanks for the idea! I forgot about CWM's ability to format the storage it detects. I feel that may be the way I have to go, but I'd like someone to comment on the fsck idea first.
Click to expand...
Click to collapse
Hi… I also experiencing same problem like you.
Do you manage to delete those file without going through format feature via CWM Recovery?
You can also try the file manager from mrrobinson aroma.
It loads from recovery...so, could work.
Sent from my SGH-I777 using xda app-developers app
Okay, here's the back story, it's short. My SD card fried on me yesterday. I had a nand backup of my stock setup on that card. That backup contained a couple of voicemails from my 2 year old daughter (not saved/forwarded, just downloaded into the voicemail app) which i hadn't gotten around to saving in the forever style yet. (was going to restore the backup and save them, then jump back to current ROM)
Anyway, i got a utility that will scan the card and found a whole ton of files on there. What's more it looks like it actually pulled a lot of it from within the backup files (no kidding, i'm seeing icons and temporary internet files and that sort of stuff) in addition to stuff stored on the root.
Was hoping someone could tell me what format these files would be in (3gp, mp4, etc.) so i know what to tell it to pull out. it's a trial software and will only let me restore 10 files before it chokes (could probably just run again on another pc though) but can anyone help me? it's doesn't give me a folder structure at all, just files, and they're even named genericly. So if i know what file type i'm looking for i can just grab those and maybe one of them will be it.
thanks!!
I looked before, and believe its something proprietary. Try using ES file explorer or something similar, store a vm and check which folders updated the time and date..start there..only thing I can think of currently.
Sent from my EVO using xda app-developers app
dangle79 said:
Okay, here's the back story, it's short. My SD card fried on me yesterday. I had a nand backup of my stock setup on that card. That backup contained a couple of voicemails from my 2 year old daughter (not saved/forwarded, just downloaded into the voicemail app) which i hadn't gotten around to saving in the forever style yet. (was going to restore the backup and save them, then jump back to current ROM)
Anyway, i got a utility that will scan the card and found a whole ton of files on there. What's more it looks like it actually pulled a lot of it from within the backup files (no kidding, i'm seeing icons and temporary internet files and that sort of stuff) in addition to stuff stored on the root.
Was hoping someone could tell me what format these files would be in (3gp, mp4, etc.) so i know what to tell it to pull out. it's a trial software and will only let me restore 10 files before it chokes (could probably just run again on another pc though) but can anyone help me? it's doesn't give me a folder structure at all, just files, and they're even named genericly. So if i know what file type i'm looking for i can just grab those and maybe one of them will be it.
thanks!!
Click to expand...
Click to collapse
Mine are located on sdcard/smvvm
They are AMR files
I use ES Flie Explorer to find them
Hope this helps
stealthl said:
Mine are located on sdcard/smvvm
They are AMR files
I use ES Flie Explorer to find them
Hope this helps
Click to expand...
Click to collapse
sorry, just circling back to see this. i ended up giving up on it. wasn't able to find any reliable way to recover the card, so i guess it's just lost
TitaniumBackup does not backup my APK anymore. I think this happen after i update to LP 5.0.2. Is it not working properly on LP?
I even did a factory reset and it's still the same. Everytime I backup my apps, after complete, the icon is a tick. Used to be a smiley face.
Anyone have a fix for this?
EDIT: OK I found out it does backup everything include APK on the first run, subsequent run it only detect the app data and the icon change from a smiley to a tick.
ljhsquall said:
TitaniumBackup does not backup my APK anymore. I think this happen after i update to LP 5.0.2. Is it not working properly on LP?
I even did a factory reset and it's still the same. Everytime I backup my apps, after complete, the icon is a tick. Used to be a smiley face.
Anyone have a fix for this?
EDIT: OK I found out it does backup everything include APK on the first run, subsequent run it only detect the app data and the icon change from a smiley to a tick.
Click to expand...
Click to collapse
The reason is in LP TB how adds .txt to its .properties file and TB itself cannot recognize..
Nobody had the same as issue as me? How can this be?
I have the same issue.. How did you fix this???
ljhsquall said:
The reason is in LP TB how adds .txt to its .properties file and TB itself cannot recognize..
Nobody had the same as issue as me? How can this be?
Click to expand...
Click to collapse
I think I may have a related issue.
This is my problem description:
- phone: Samsung S4 I9505 upgraded to Lollipop 5.0.1, rooted with CF-Auto_Root
- using Titanium Backup version 7.1.2
1. set backup location to SD card using the DocumentProvider interface
2. after "Calculating scenarios" for different batch actions, for "Redo backups for modified data" shows 402 backups to be redone
3. run the scheduled action "Redo backups for modified data"
4. immediately afterwards, there are still 402 backups to be done
and
- "Calculating scenarios" never seems to finish. It's as if TB is having trouble scanning the backups
- the "properties.txt" files are created in the backup folder but they are empty files
I sent a report of a possible bug to Titanium Backup support.
I'm amazed this bug isn't more widely reported.
At a guess, the DocumentProvider API allows some sort of file type hint when creating a file and TB is optimistically setting this to text rather than whatever binary format is used for the archives, and for god knows what reason android is appending a .txt file extension.
I've spent the best part of a day banging my head against a wall trying to figure out why my backup couldn't be restored. Thank **** I found this thread, I was close to admitting defeat and starting from scratch.
Just to assist people in finding this, here's some of the stuff I googled for: "has app no", "no restore button", "restore question mark", "unknown"
I was lucky that my google-fu led me to this thread, and another one about Titanium backup adding .zip after .gz because I took a backup of my S5 yesterday, upgraded and hard reset, and then it couldn't find any backups. I knew they were there, but it turned out that both those bugs had struck me at the same time! So I copied the directory to the SD card, took the card out of the phone, put it into my pc and did a bit of old school "ren *.zip *." and "ren *.txt *." which put it all right again. Thanks for the thread!
Mastiff said:
I was lucky that my google-fu led me to this thread, and another one about Titanium backup adding .zip after .gz because I took a backup of my S5 yesterday, upgraded and hard reset, and then it couldn't find any backups. I knew they were there, but it turned out that both those bugs had struck me at the same time! So I copied the directory to the SD card, took the card out of the phone, put it into my pc and did a bit of old school "ren *.zip *." and "ren *.txt *." which put it all right again. Thanks for the thread!
Click to expand...
Click to collapse
renaming files work
This issue is not fixed even in 7.4.0.2 version of TB on LP. But this issue depends on ROM, because on CM12.1 it didn't reproduce.
Here is the fastest fix for Windows:
1.Open cmd
2.Switch drive to sdcard
3.Go to titanium backup folder (or wherever your backups are)
4.Execute two commands:
rename *.gz.zip *.
rename *.properties.txt *.
Example sequence of commands:
g:
cd G:\backup sept 2016\TitaniumBackup
rename *.gz.zip *.
rename *.properties.txt *.
saneksem said:
This issue is not fixed even in 7.4.0.2 version of TB on LP. But this issue depends on ROM, because on CM12.1 it didn't reproduce.
Here is the fastest fix for Windows:
1.Open cmd
2.Switch drive to sdcard
3.Go to titanium backup folder (or wherever your backups are)
4.Execute two commands:
rename *.gz.zip *.
rename *.properties.txt *.
Example sequence of commands:
g:
cd G:\backup sept 2016\TitaniumBackup
rename *.gz.zip *.
rename *.properties.txt *.
Click to expand...
Click to collapse
Unfortunately, this didn't made the trick for me... When restoring any update (app+data) it takes so many time that it doesn't end... I don't know what the hell happened...