Lately my nandroid backups have been coming up very very small only about 48mb I have no idea whats causing this?
Had changed backup format to DUP instead of TAR. Woops.
Related
I realized recently that my nandroid backups were not completing correctly (see pic). I noticed this because I have done numerous nandroid backups and there is only one backup showing in the nandroid folder. It always says "backup complete" but above that it looks like it might not be completing correctly? Is there a way to reinstall nandroid backup?
this is normal...
I've experienced problems with backups in Amon Ra as well. I've had a lot more success backing up via Rom Manager through Clockwork. Just an FYI for the future.
tyrnight, what is normal? and how come when I just ran this Nand backup, I have no new backups in the nandroid folder?
MSmith1, I thought Clockwork isnt a complete backup like Nandroid?
ryan2202 said:
tyrnight, what is normal? and how come when I just ran this Nand backup, I have no new backups in the nandroid folder?
MSmith1, I thought Clockwork isnt a complete backup like Nandroid?
Click to expand...
Click to collapse
*sigh*
clockwork is a recovery just like amon is a recovery -
THEY BOTH have nandroid backup feature... its just as easy if not easier in clockwork and yes it is a complete nandroid backup
ryan2202 said:
tyrnight, what is normal? and how come when I just ran this Nand backup, I have no new backups in the nandroid folder?
MSmith1, I thought Clockwork isnt a complete backup like Nandroid?
Click to expand...
Click to collapse
Clockwork & Nandroid are two different things. Amon RA & Clockwork are two different recoveries, & the nandroid backups can be performed by both of them.
I'm personally using Amon RA's recovery because i heard Clockwork doesn't wipe data as it's supposed to.
In the image you posted you are using clockworkmod backup/recovery. Therefore your back up images are in /sdcard/clockworkmod/backup, not nandroid.
Iceman5000 said:
In the image you posted you are using clockworkmod backup/recovery. Therefore your back up images are in /sdcard/clockworkmod/backup, not nandroid.
Click to expand...
Click to collapse
exactly...
OK I think I got it now. I thought Nandroid backed up differently than the Clockwork or Amon tools. I didnt realize the Clockwork (which I have been using) is a COMPLETE back up of the phone. I thought it was only backing up the ROM and not the data and apps, etc.
So since I have Clockwork/Amon through ROM Manager I can just use that to run my complete backups instead of going into Nandroid through recovery mode?
You can only use Clockwork to backup via ROM Manager. If you use Amon RA you'll have to manually boot into Recovery & backup from there.
Clockwork is not working properly. It is not backing up sdcard's and is not wiping all data. I recommend just using nand and quickboot however the new clockwork flashed over nand had to reinstall Nand Recovery via adb etc..
I'm new to this all myself but I think the reason it won't back up the SD card is because it would have to backup the entire card and where would it put the file? I'm guessing your SD card would have to be large enough and partitioned for it to write the backup to. That is total speculation of course...
First of all, according to the pic, your sdcard is pretty critically low on space so a nand backup probably won't complete fully. Second, the message about android.secure is a directory reference that occurs if you have transferred your apps to your sdcard. Since it can't find the directory, I'm assuming you aren't using apps2sd. The second message about the sd-ext directory only applies if you've actually created a secondary partition on your sdcard. So just because it skips those two areas doesn't mean that the remainder of your data has not been backed up.
Sent from my PC36100 using XDA App
First off I'm at the final stage before I introduce a 'software error' onto this phone and return it to a sprint shop for a replacement.
I have a broken nandroid backup, that DID however backup my wimax partition.
Now, my wimax RSA keys got nuked somehow and I figure if there's a way for me to restore JUST the wimax.img file, I might be in with a chance of having a workable evo again.
The thing is, I can only find guides for restoring a full nandroid backup, and nothing for restoring wimax individually.
Would anyone be able to help?
Thanks.
welp, i answered my own question.
I just copied the nandroid backup .img to wimax.img in my root directory and everything works fine now
Remember boys and girls - BACKUP FIRST. Thank-me
I might be wrong, but you should be able to make a new backup, and just copy the WiMax partition over. If your keys got nuked though, it might throw off the checksum of the backup, which I don't know how to change. And again, thats mostly theory, I'm no Dev.
Do a new nandroid backup, reboot, brows your SD card for nandroid, then there will be another folder, and inside that one will be the different backups. Open up the one with the working wimax partition, copy it, and put it in the nandroid you want to recover.
I would be sure to do yet another nandroid backup, just in case you mess something up.
Edit: Slow typing ftl, looks like you got it!
before i went to 4.2, i was using CWM and each backup usually only took up about ~1 gb of space.
now im using TWRP since it seems to work better with 4.2 and was recommended with 4.2, and backups are almost 2gb each.
i dont have much more than i did before. and this eats up SO MUCH SPACE on the internal SD i can only leave one backup on my phone, whereas i could have 2-3 backups before.
I;m not planning to jump back to cwm because its a huge hassle to to change recoveries. but is there anything i can do to downsize it? or save to my external SD and still have it working?
Ive tried backing up to external sd with bad results before.
Thanks for any help
Did you take the blobs folder in account when looking at the size of the CWM backups? I'm sure I'm over simplifying here, but CWM takes a 'snapshot' of your system on the first backup, and then only backs up things that have changed from then on, even if you delete the first backup. It makes things quicker for sure and since it only backs up changes, the backups are smaller too as they share some data. TWRP does a full backup each time. I use TWRP, but do miss the quick backups that CWM gave me.
lordmorphous said:
Did you take the blobs folder in account when looking at the size of the CWM backups? I'm sure I'm over simplifying here, but CWM takes a 'snapshot' of your system on the first backup, and then only backs up things that have changed from then on, even if you delete the first backup. It makes things quicker for sure and since it only backs up changes, the backups are smaller too as they share some data. TWRP does a full backup each time. I use TWRP, but do miss the quick backups that CWM gave me.
Click to expand...
Click to collapse
Yep, you are correct! That "blobs" folder is an extremely evil and deceiving... Its HUGE. I like TWRP because it backs up everything in one shot, so I can pull back ups off my phone and save them on my computer for "just in case." Can't do that with CWR....
BAM1789 said:
Yep, you are correct! That "blobs" folder is an extremely evil and deceiving... Its HUGE. I like TWRP because it backs up everything in one shot, so I can pull back ups off my phone and save them on my computer for "just in case." Can't do that with CWR....
Click to expand...
Click to collapse
You have the option of doing a nandroid backup the old way in CWM. You just have to change the backup format and it will backup without the blobs folder. It's how I do it.
Enable compression on TWRP. Takes a bit longer but can usually decrease the size around 30% or so.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hi guys, having an issue trying to restore my CM 10.1 backup, everything will restore apart from data, I've checked the MD5 sum and the data backup is fine, I can manually extract the data backup without any issues it just won't restore through TWRP. Anyone any ideas?
it once happened to me, I'm using CWM
I just mounted data from mount and storage then started an advanced restore then data only.
so why don't you try "advanced restore"
if it doesn't work, it won't harm anything
I've just restored my data from the backup using titanium so now everything is recovered. It's just strange that TWRP wouldn't restore it.
Good to know
update to the latest TWRP (if you haven't) , it might be a known bug.. since the data is not corrupted nor missing and the md5 is correct
all we can assume is that it's TWRP fault , right?
anyway, restoring with titanium doesn't restore all the settings if I remember right, or does it?
Hello,
I looked at other threads regarding the EFS partition but none that really answer my question. I hope it's not a stupid question...
So basically, I was trying out a new ROM and made a backup using TWRP. I inadvertently backed up the data partition separately, but I figured that didn't matter. I then backed up all other partitions (EFS and Modem included) in a separate file. I didn't like the new ROM I tried so I went to restore my backups. When restoring the "everything sans data" backup, I kept getting an md5 error, even though I didn't create an md5 upon backup nor did I ask it to look for an md5 on restoration. I decided to try and restore everything except the EFS, and it worked. Phone is up and running and it doesn't seem like there are any issues. Can someone please explain this to me? I'm assuming the existing EFS partition was never changed, so restoring everything but the EFS should still result in a complete system, but can anyone suggest a reason why it failed when trying to restore EFS with everything else? Thanks!