Related
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.
I have a Samsung Galaxy S2. When I did a firmware update, I did a backup of everything.
Then I did a firmware update, of course it failed, dont know why, I think it was because I was using a USB 1.1 socket on the computer, since the emergency restore worked when switching to a USB 2.0 socket on the back of the computer.
Now I have lost everything. When I try to restore, everything is greyed out. Had some important passwords saved into "Memo" in the phone and need to get them back.
How I do to restore the memo data?
The first attachment show the backup screen, and the second screen show that the memo (in swedish: "Anteckningar") is greyed out. Everything in Personal details (swedish: "Personuppgifter") is greyed out.
How I do to restore the memo data? Only option is to restore some photos.
Solved it. Did this, first I started recovery, since I had some heavy files, I could start a very long recovery.
Then I went into my document folder, where the SBU files are placed. Kies does a temporary extraction, so I could go into the file, and found a memo.bk file.
Copied it to desktop, renamed to .txt and found this:
BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
DESCRIPTION;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:PASSWORD1=0APASSWORD2
DTSTART:20111010T110217Z
X-ALLDAY:UNSET
END:VEVENT
END:VCALENDAR<#JIG#><#COUNT#>1
(of course I don't show the passwords here, thats why they are replaced Password1 and Password2)
Thanks!
sebastiannielsen said:
Solved it. Did this, first I started recovery, since I had some heavy files, I could start a very long recovery.
Then I went into my document folder, where the SBU files are placed. Kies does a temporary extraction, so I could go into the file, and found a memo.bk file.
Copied it to desktop, renamed to .txt and found this:
BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
DESCRIPTION;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:PASSWORD1=0APASSWORD2
DTSTART:20111010T110217Z
X-ALLDAY:UNSET
END:VEVENT
END:VCALENDAR<#JIG#><#COUNT#>1
(of course I don't show the passwords here, thats why they are replaced Password1 and Password2)
Click to expand...
Click to collapse
Thanks a million buddy
Almost a year and a half later since you posted this, but you just saved me!
Had the same problem after updating from ICS to Jellybean, all my important data and password info in my memo files
When i tried to tick the box to restore, it was all greyed out to my disappointment.
So i started the restore process, when the error came up, navigated to the temp folder within Kies directory and BAM! memo file right there.
Thanks again!
Audwin
Greetings,
Not sure if this something Ive done when rooting and putting busybox on, but im trying to backup the entire contents of my sdcard to my desktop.
The files start copying, but at some point it fails and most of the folders of high interest are empty on the desktop. I need my titanium backup and mybackuppro, rom backups, etc. What it looks like I have to go into each of these folders and copy manually.
I just want to select all, copy, paste and be done with it.
Has anyone had an experience like this?
same here.
and can see not all folders/files' and even worse: i see dfferent folders with windws explorer, total commander mtp and total commander adb... only on the device itself i can see everything correct...
dn't know what it is, never seen before...
I made some progress here. Im preparing for a firmware upgrade which wipes, so I need this backup.
I noticed that from the root, if I drag one folder alone, it will copy that with all sub-folders properly.
It's only when you copy multiple folders that it fails.
Maybe this is solved in the firmware upgrade to HBOOT 1.35. I will report back here when complete.
Paz75 said:
I made some progress here. Im preparing for a firmware upgrade which wipes, so I need this backup.
I noticed that from the root, if I drag one folder alone, it will copy that with all sub-folders properly.
It's only when you copy multiple folders that it fails.
Maybe this is solved in the firmware upgrade to HBOOT 1.35. I will report back here when complete.
Click to expand...
Click to collapse
This appears to be fixed now after the firmware upgrade. Copying all files without any recursion problems
Paz75 said:
This appears to be fixed now after the firmware upgrade. Copying all files without any recursion problems
Click to expand...
Click to collapse
same here, update to HBOOT 1.35 and all folders appear in every way and can be copied without problems :good:
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...
I had autoupdate to google drive turned off for Whatsapp. Got myself a new phone now, and I had coppied the "stickers.db.crypt14" from my old phone already before it got bricked. It was in the "backup folder" and because of this I thought it was the only file needed to recover a backup. I had a lot of stickers and so it's actually a big file. So for this it seemed verry obvious that this was the file I needed.
But now I try to restore and I come across toppics on google and here, talking about more files from other dirs too.
Is it possible to restore stickers from only this "stickers.db.crypt14" file?
I also backuped another, containing all (or at least most of all the individual stickers as a "image" file.