Related
Does anyone know of a way to reduce the size of my nandroid backups. I see it backing up cache and temp files. Where can I find some of these files to clear them out.
sgtagem said:
Does anyone know of a way to reduce the size of my nandroid backups. I see it backing up cache and temp files. Where can I find some of these files to clear them out.
Click to expand...
Click to collapse
I use the root app SD Maid...lets you clean up all those pesky leftovers.
This is one of the advantages of AMON recovery, it allows you to pick what you want backup. CWM does not have this yet...you could try moving the files to another folder and editing the md5 file. This way when it restores it doesn't run into a md5 error.
When doing a backup in cwm, this is what it says right before completion. What does this mean?
Also, can you not rename ur backups. If you have more than one. How do you tell them apart?
Thank you
That's normal. If i remember correctly, its a partition inside your internal sd card for your external sd card and it's not mounted in CWM by default.
And you can rename it. Once you back up I'm CWM, boot your phone and go into your sd card. Inside clockworkmod/backups there's folders with date and time as the name, rename it to your hearts content
Sent from my SGH-T769 using xda app-developers app
sd-ext is an ext4 partition on the sdcard in addition to the normal fat32 partition. Just as an fyi, the defacto "standard" for alternative sdcard partitions also includes the ability to have a dedicated swap partition.
I have a proper sd-ext partition and get the same message, so it's likely that CWM isn't set up correctly. Nothing you can do about it unless you want to rebuild CWM
I also believe that partitioning the sdcard through CWM also doesn't work properly.
jparnell8839 said:
And you can rename it. Once you back up I'm CWM, boot your phone and go into your sd card. Inside clockworkmod/backups there's folders with date and time as the name, rename it to your hearts content
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Everytime i renamed backup. It would never let me restore, if needed too. Due to MD5 checksum error (or something like that)
i googled why it was happening and read changing backup name will cause the issue.
So next backup i made, i didnt rename it, annd restored as expected. kinda sucks would like to no which back up, is which.
trevor7428 said:
Everytime i renamed backup. It would never let me restore, if needed too. Due to MD5 checksum error (or something like that)
i googled why it was happening and read changing backup name will cause the issue.
So next backup i made, i didnt rename it, annd restored as expected. kinda sucks would like to no which back up, is which.
Click to expand...
Click to collapse
that's weird :/ I always rename my backups and it's never gave me that error on all 3 android phones i've had (htc thunderbolt, wildfire s, and the blaze). something like "Current-10/3-preICSkies" and it never hurts. of course, I always copy my backups to windows to store on my hard drive before I rename
merwin said:
sd-ext is an ext4 partition on the sdcard in addition to the normal fat32 partition. Just as an fyi, the defacto "standard" for alternative sdcard partitions also includes the ability to have a dedicated swap partition.
I have a proper sd-ext partition and get the same message, so it's likely that CWM isn't set up correctly. Nothing you can do about it unless you want to rebuild CWM
I also believe that partitioning the sdcard through CWM also doesn't work properly.
Click to expand...
Click to collapse
So it is all good if we get this message?
correct, phones of yester-year had low memory and storage. people devised ways to make apps2sd prior to froyo and thus an ext partition on the sdcard was born. i didnt include it as any device since the sgs1 has had plenty of space (the samsung galaxy prevail's /data partition was only 140MB's which included things like google maps updates etc)
you can use rom manager to rename backups, but cwm generates an md5 sum off the folder name, in this case a very specific date
trevor7428 said:
Everytime i renamed backup. It would never let me restore, if needed too. Due to MD5 checksum error (or something like that)
i googled why it was happening and read changing backup name will cause the issue.
So next backup i made, i didnt rename it, annd restored as expected. kinda sucks would like to no which back up, is which.
Click to expand...
Click to collapse
Can't you just make a folder name what you would like then put the back up into the folder that has the name you wanted to be able to tell them apart?
I just thought of it, Hey I actually came up with an idea on my own at xda, wow, not bad, it's about time though after so many years and not too technical either, Hey but I don't know if that is a good thing for me or not.
Well anyways I am going to try my new techniques. LoL
Oh hey I forgot why I was here's until just now, not only did my backup say the op title, but also said something about not backing up applications either
1) is that normal too!?
2) I looked for the back up and shows up fine I the new folder. Although I can't say I ever remeber after clicking backup then clicking the backup file seeing 4 other files to chose from, like system, data, etc.
What is really going on now? I thought after clicking on the file it would go to the confirm option and that was it.
I just did my first ROM / unlock / TWRP /CROM install today and all went perfect thanks to all the guides here, but I have some questions now, more so about my TWRP flash....
I just updated twrp from 2.3.3 to the newest 2.4.4 following their guide using goo manager. I assume it was successful because I'm typing on her now' however.... My home screen now displays <Safe mode> on thebottom left.... Why is this? Also, after the flash, I lost my swiiftkey board app? Actually, seemed to have lost all my apps lol... What did I do wrong? (I didnt titanium backup before I updated, didn't know I needed too lol)
Do most use both nandroid backup AND titanium or just one?
Think that's all I have for now....
BTW, on Cleanrom in her 3.4.7 odex i think...
Edit, I still have all my app icons on my screen, but not in the main menu?
Proweedsmoker said:
I just did my first ROM / unlock / TWRP /CROM install today and all went perfect thanks to all the guides here, but I have some questions now, more so about my TWRP flash....
I just updated twrp from 2.3.3 to the newest 2.4.4 following their guide using goo manager. I assume it was successful because I'm typing on her now' however.... My home screen now displays <Safe mode> on thebottom left.... Why is this? Also, after the flash, I lost my swiiftkey board app? Actually, seemed to have lost all my apps lol... What did I do wrong? (I didnt titanium backup before I updated, didn't know I needed too lol)
Do most use both nandroid backup AND titanium or just one?
Think that's all I have for now....
BTW, on Cleanrom in her 3.4.7 odex i think...
Edit, I still have all my app icons on my screen, but not in the main menu?
Click to expand...
Click to collapse
Have you try to power down, then power it backup?? If successful you should have all your apps back.
Edit: what firmware you were on before flashing CROMI??
Yes sir, soon as I did a quick 2nd reboot, she was back to normal. Thank you for the reply, I just get nervous with this being my first time time. Go figure, and finally give up waiting for 4.2, unlock and romantic up, and it drops the next day lol.
I was on 10.4.4.25 I think
Proweedsmoker said:
Yes sir soon as I did a quick 2nd reboot, she was back to normal. Thank you for the reply, I just get nervous with this being my first time time. Go figure, and finally give up waiting for 4.2, unlock and romantic up, and it drops the next day lol.
Click to expand...
Click to collapse
Hahaha, indeed of your luck! but not to worry, sdbags is going to get the update 4.2 dlpkgfile sometime today and we should see our 4.2 cromi sooner than expected...in a few days...
Few more questions
Just had a few more questions that I thought of while playing with my NEW tablet, (I honestly stopped using my tablet for months after I got it because it was so laggy, and CROMI has changed all of that!!!!!!!) and figured I would bump this thread vrs start a new one... Sorry for the noob questions, but knowledge is power and Im trying to learn! ( I do read alot! )
Currently on TWRP 2.4.4, CROMI 3.4.7 Odex w/ the OC Kernel 1.8ghz
Now, I have noticed a huge increase in my system files from when I came from stock... IE Stock, I had around 55gigs or something free on internal memory, now, I have around 30, is this normal and what is using that much space? I currently appear to have 2x backups in TWRP menu..
I also have got the Titanium backup as suggested, and backup regularly... But what exactly is it backing up other then apps? Does it create the same backup files that TWRP does? I assume TWRP is backing up the critical O/S files??
How many backups in TWRP are needed and when can I delete (if ever) some? Im guessing here, that TWRP is needed only if you get stuck in bootloop or some other situation that prevents a full boot to home screen?
Should I try to find the backup files in TWRP and Titanium and copy them to my home PC for safe keeping? (I did follow the guides and also have them on clouds)
When preforming a "clean install" of an updated CROMI version, will those backup files on the internal storage be wiped, or are they protected from a wipe / "clean install"? Is a "dirty flash" un-advised? I plan to only use CROMI roms...
I also downloaded the ROM manager thing, as suggested by some.... but, do I really need that? It seems like its just a Titanium clone, with some extras... Also, the ROM manager has some things like boot animations and such, are those safe to use with CROMI? I was looking at some apps to clean up my storage from junk files, but I wonder, if those apps are compatible with CROMI?!?
Ok, thats all I have for now I think, and thank you for the help as always!!!!
OK. I will provide you the best advise as possible but there are variations depend on individual taste.
1. Internal memory growth - possible you backup to your internal instead of external sdcard. Look for large file like videos, rom/kernel in the /sdcard/ download folder. Do clear cache weekly. I just assumed that you download all the roms and backup to your internal.
2. Backing up
a) TWRP - this is called nandroid backup. It will back up your entire OS with all the apps and cache and setup...everything. Before you upgrade from one rom version to the next you should take a backup before do so. Or once in a while if you making a major change to your OS on the same version, you should do a second backup. This backup can restore you back exactly the way it was before you mess up. The disadvantage is you don't have a choice to pick and choose what you can restore. It's either all or none. For this you should keep one backup for the current OS, one for major modified to current OS, one for new OS and one for major modified to the new OS, so total about 4 max. Unless you flashing more than just cromi. This nandroid backup will bring you back your previous setup if you have boot loop.
b) Titaniumbackup - This only backup your system apps, user installed apps and all the settings belonged to the app. You can't use this to restore your OS.(like when you have bootloop). It used to restore applications only. To keep the backup from growing, you should set Max backup history to 5. It's only keep maximum of 5 recent backups.
3. Clean install will only wipe INTERNAL memory, not your external SDcard. So it's highly to keep your Titaniumbackup and TWRP backup on your External sdcard. For double protection make a backup of your sdcard to PC.
4. Personally, I stay away from Rom Manager. Only use bootanimantion, themes etc.. from the tf700 threads. Rom Manager is not tf700 specific so some features may work, some may even brick your device.
5. App to clean up junkfiles - you don't need such app. Most of the stuff you download will be in the /sdcard/download or in the download app folder, example if you use Sugar Sync app to download, the download file will be in /sdcard/mysugarsync folder. You need to keep track of what you put onto the devcie is the best way to manage your internal storage. For external sdcard, you should keep 1), rom, kernel or any necessary zip files to reinstall your OS. 2) all your TWRP and Titanium backup files 3) Anything that important to you.
Hope it all makes sense to you!
Internal memory growth - possible you backup to your internal instead of external sdcard. Look for large file like videos, rom/kernel in the /sdcard/ download folder. Do clear cache weekly. I just assumed that you download all the roms and backup to your internal.
Click to expand...
Click to collapse
Yes, I was backing up to the internal memory! I have now backed up TWRP onto my microSD card! I was trying to change Titanium's backup path to the microsd, and I have 3 folders: /storage -Red, not writable -sdcard0 -sdcard1- I assume red is a system folder, sdcard0 is the internal storage, and sdcard1 is the mircoSD, however, when I try to select it, it says "this folder cannot be accessed"?? How do I fix this? I have never formatted my mircoSD or anything, just plugged it in when it came in the mail, and it worked.... Got about 50 gigs worth of movies, and my new TWRP backup on it now....
Do clear cache weekly.
Click to expand...
Click to collapse
How do I do this?? Would it be in TWRP menu??
TWRP - this is called nandroid backup. It will back up your entire OS with all the apps and cache and setup...everything.
Click to expand...
Click to collapse
Thanks for clearing that up! I thought nandroid backups were another type of backup, and the only thing I could find was an Online Nandroid backup app, so, of course I used that.... I guess I can get rid of that now!
you should set Max backup history to 5
Click to expand...
Click to collapse
Ok great, max is 5, so if I just use a value of 1, Im golden then! (BTW, honestly, the only apps I care about are what keeps my tablet running butter smooth, so..... Maybe that will change now that I have a tablet I can actually use lol)
Clean install will only wipe INTERNAL memory, not your external SDcard. So it's highly to keep your Titaniumbackup and TWRP backup on your External sdcard. For double protection make a backup of your sdcard to PC.
Click to expand...
Click to collapse
What are the chances of the mircoSD corrupting the files or becoming unreadable when I need to get those backups like TWRP / Titanium?? I assume the PC backup file push is the last resort if the above happened?
App to clean up junkfiles - you don't need such app. Most of the stuff you download will be in the /sdcard/download or in the download app folder
Click to expand...
Click to collapse
Actually, that folder is empty.... However, I found how to make it explain what was in each "file catagory" so I understand what is where and how big!
For external sdcard, you should keep 1), rom, kernel or any necessary zip files to reinstall your OS.
Click to expand...
Click to collapse
ALL of these files (rom,kernel, etc..,) would be found in the CROMI zip file I used on initial install? Would it be best to leave them zipped if so, or to create a folder and unzip and copy paste it in?
Many thanks!!
Last question, WTF is tunny browser??
Proweedsmoker said:
Yes, I was backing up to the internal memory! I have now backed up TWRP onto my microSD card! I was trying to change Titanium's backup path to the microsd, and I have 3 folders: /storage -Red, not writable -sdcard0 -sdcard1- I assume red is a system folder, sdcard0 is the internal storage, and sdcard1 is the mircoSD, however, when I try to select it, it says "this folder cannot be accessed"?? How do I fix this? I have never formatted my mircoSD or anything, just plugged it in when it came in the mail, and it worked.... Got about 50 gigs worth of movies, and my new TWRP backup on it now....
Click to expand...
Click to collapse
**** Directory of your external sdcard should be /Removable/microSD.
How do I do this?? Would it be in TWRP menu??
*** You can download a free cache cleaner app from the market
Thanks for clearing that up! I thought nandroid backups were another type of backup, and the only thing I could find was an Online Nandroid backup app, so, of course I used that.... I guess I can get rid of that now!
*** When you do a TWRP backup. This is nandroid backup! so you already using it and didn't know about it lol!
Ok great, max is 5, so if I just use a value of 1, Im golden then! (BTW, honestly, the only apps I care about are what keeps my tablet running butter smooth, so..... Maybe that will change now that I have a tablet I can actually use lol)
*** Yep, 5 is max but anything less is better!
What are the chances of the mircoSD corrupting the files or becoming unreadable when I need to get those backups like TWRP / Titanium?? I assume the PC backup file push is the last resort if the above happened?
*** The chance is very small, but that's why I said a second backup of sdcard to your pc. It easy because it's all in one location (sdcard).
Actually, that folder is empty.... However, I found how to make it explain what was in each "file catagory" so I understand what is where and how big!
ALL of these files (rom,kernel, etc..,) would be found in the CROMI zip file I used on initial install? Would it be best to leave them zipped if so, or to create a folder and unzip and copy paste it in?
*** They should be zipped and move to sdcard.
Last question, WTF is tunny browser??
I believe its a cache directory for Dolphin Browser.
One last question for the night, lol...
As I mentioned, I have never formatted my mircoSD.... Just opened its package (64g Scandisk something or another), plugged it in and its been working just fine ever since, although Xfering files is abit slow :/
Its currently formatted in a "Generic hierarchical" file system..... Being that it will be a life line for my tabby, will TWRP / Titan / etc.., be OK with reading, booting, and w/e else may be required from this type of file system??
Proweedsmoker said:
Its currently formatted in a "Generic hierarchical" file system..... Being that it will be a life line for my tabby, will TWRP / Titan / etc.., be OK with reading, booting, and w/e else may be required from this type of file system??
Click to expand...
Click to collapse
That's not the real filesystem that the card is formatted with, that's what Windows sees 'through' the connection with the tablet.
Searched all over before making this thread but I couldn't seem to find an answer. Rooted my phone to install PAC-man mod. When I finished I made a backup of my original system with CWM. I flashed PAC-man but I'm havign issues and I wanted to go back but CWM can't seem to restore the backup. I checked, and it's still there but when I try to restore I get:
Couldn't open directory.
No files found.
Any ideas?
Is your backup stored on the phone storage or an external card?
Sent from a Shaftamle Galaxy S3
Please hit the "Thanks" button if I helped you!
Shaftamle said:
Is your backup stored on the phone storage or an external card?
Sent from a Shaftamle Galaxy S3
Please hit the "Thanks" button if I helped you!
Click to expand...
Click to collapse
phone storage
SuperBrother said:
phone storage
Click to expand...
Click to collapse
Edit: before you go about following the steps I wrote below there is one other options. If you are using an app to try to restore the backup then this way should work. Manually boot into recovery mode click on backup and restore then restore from SD card and under the file labeled 0 there should be a folder listed as clockworkmod. From there you should be able to restore your backup if that doesn't work then follow the steps that I wrote about moving the file to the external card. Either way in the future I would recommend always backing up to the external card.
Assuming you're coming from a 4.1 build when you install a 4.2 ROM it changes the file structure of the internal drive. This is due to the fact that 4.2 roms support multi user functions. So most likely when you try to restore your backup it's located in a different path then it was originally.probly something like sdcard/0/clockworkmod instead of sdcard/clockworkmod. My advice would be move your back up to the external card manually reboot your phone into recovery and restore your backup from the external card. If you use DUP you have to move the backup and the blob folder. If you used a tar backup, just move the backup. When in recovery mode select restore from external SD card and navigate to the folder you put it in.
From here on out if you do your backups from recovery make sure you back up to the external card. If you use ROM Manager make sure before you do your next backup that you select under the settings panel to use external storage. The newest update of ROM Manager allows you to do so.
One other thing, once you restore your backup and your back to a 4.1 build it's going to look like your internal storage is wiped. It's definitely not use a file manager to browse the internal storage there will be a folder labeled 0. That's all of you data. Open that folder up highlight and cut all of the contents go back to the root of your internal storage(the folder you just came from) and paste it there. It will ask if you want to overwrite certain files just click Yes the only files that will be overwritten are the ones that were just made when you rebooted on the 4.1 system you will not lose anything.
Sent from a Shaftamle Galaxy S3
Please hit the "Thanks" button if I helped you!
What's the size of the back up? Are all the required files in there? Try updating your su app, then try making another back up and make sure it works. What version of cwm are you using? Is your system r/w?
Surge1223 said:
What's the size of the back up? Are all the required files in there? Try updating your su app, then try making another back up and make sure it works. What version of cwm are you using? Is your system r/w?
Click to expand...
Click to collapse
the SU binary and the clockworkmod version should have little to nothing to do with restoring a backup especially when it says the file cannot be found. Thus far is the size of the backup goes unless you opened up the file and started jacking around with stuff that was backed up there's no chance that he's missing information. When it says the file cannot be located it's because rom manager/ ROM toolbox is looking for the file that was originally placed in a specific area and is no longer there hence the 4.2 file structure I spoke of.
Sent from a Shaftamle Galaxy S3
Please hit the "Thanks" button if I helped you!
You're assuming you know why I was asking those questions, and as a result that you're more knowledgeable than I am in this subject area. Besides human error, there are still numerous ways cwm, su, and the back up size can contribute to a failed recovery. We're both just trying to help.
Surge1223 said:
You're assuming you know why I was asking those questions, and as a result that you're more knowledgeable than I am in this subject area. Besides human error, there are still numerous ways cwm, su, and the back up size can contribute to a failed recovery. We're both just trying to help.
Click to expand...
Click to collapse
I agree everybody just tries to help everybody that's what makes this website great. The only reason I said what I did is because I ran into this exact problem about 4 months ago so I know exactly what he's talking about. Sorry if I came off as a ass, I didn't mean to.
Sent from a Shaftamle Galaxy S3
Please hit the "Thanks" button if I helped you!
Is alright ,thanks for explaining though. No room for hate in a cwm debate.
Shaftamle said:
Edit: before you go about following the steps I wrote below there is one other options. If you are using an app to try to restore the backup then this way should work. Manually boot into recovery mode click on backup and restore then restore from SD card and under the file labeled 0 there should be a folder listed as clockworkmod. From there you should be able to restore your backup if that doesn't work then follow the steps that I wrote about moving the file to the external card. Either way in the future I would recommend always backing up to the external card.
Assuming you're coming from a 4.1 build when you install a 4.2 ROM it changes the file structure of the internal drive. This is due to the fact that 4.2 roms support multi user functions. So most likely when you try to restore your backup it's located in a different path then it was originally.probly something like sdcard/0/clockworkmod instead of sdcard/clockworkmod. My advice would be move your back up to the external card manually reboot your phone into recovery and restore your backup from the external card. If you use DUP you have to move the backup and the blob folder. If you used a tar backup, just move the backup. When in recovery mode select restore from external SD card and navigate to the folder you put it in.
From here on out if you do your backups from recovery make sure you back up to the external card. If you use ROM Manager make sure before you do your next backup that you select under the settings panel to use external storage. The newest update of ROM Manager allows you to do so.
One other thing, once you restore your backup and your back to a 4.1 build it's going to look like your internal storage is wiped. It's definitely not use a file manager to browse the internal storage there will be a folder labeled 0. That's all of you data. Open that folder up highlight and cut all of the contents go back to the root of your internal storage(the folder you just came from) and paste it there. It will ask if you want to overwrite certain files just click Yes the only files that will be overwritten are the ones that were just made when you rebooted on the 4.1 system you will not lose anything.
Sent from a Shaftamle Galaxy S3
Please hit the "Thanks" button if I helped you!
Click to expand...
Click to collapse
This would make a lot of sense! That's my situation exactly. I don't want to try it just yet because I'm still trying to get a ROM working properly on my phone (PAC-man, having issues but that's for another thread). If I end up throwing in the towel and this checks out, I'll be sure say thanks.
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Have a look at and/or post your log from twrp. You can find this under advanced options then copy log or use the command adb pull /tmp/recovery.log.
Also, I know in the past titanium backup hasn't been great at extracting nandroids. Try https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore and see if it makes a difference.
runner1717 said:
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Click to expand...
Click to collapse
Have you actually tried using the backup to restore? You sure the app you are using to check isn't the issue?
runner1717 said:
Hi all,
I have a Droid MAXX with 4.22 (jellybean) installed, unlocked bootloader, rooted, with TWRP 2.6.3.1 installed.
I use Android File Verifier to verify backup and keep getting Java read errors on the backups. If I open the backups in Titanium Backup, several files are missing, so the backup if definitely bad. I've made several backups, all with the same error. I backed everything up on my Internal SD and used TWRP to wipe the internal SD, thinking the partition was corrupt. No difference.
I installed TWRP 2.7 thinking that might help. The files seem to verify through a little further but then fail with the same message. I've attached a screen shot of the error message.
Any thoughts? I'm freaking out not having a good backup and I'm scared that maybe the internal SD in bad? I hope not, I like my unlocked MAXX! Is there a way to format or sector check the internal SD? I don't think the wipe in TWRP actually does a format, just an erase.
Anyone else having similar problems? Things to check?
Thanks!
Mike
Click to expand...
Click to collapse
Switch to Philz it will handle twrp bu's too. You can watch the md5 check going on before you command the restore to take place. At least on 624.
Thanks for the help and suggestions. Here's what I found:
Tried TWRP 2.6.3.1, 2.6.3.0 and 2.7, all with the same result. Corrupt files. I verified this using Android File Verifier (great utility, used for years). When running Calc MD5 checksums on the individual backup files, some would verify and others would not.
Running multiple backups with each version resulted in failed backups. On a weird note, I could not remove the TWRP directory using either Root Explorer or ES file explorer. Both would cause the phone to reboot. The only way I could remove the directory was using file manager in TWRP.
Switched to Philz recovery and ALL backups verified just fine! Although it doesn't have the fancy interface or some of the features of TWRP, it gets the job done!
My conclusion is that there's some sort of issue with TWRP writing to the internal SD as proven with the incomplete backups and the directory problem it caused on the SD. I would recommend others use the Android File Verifier to make sure they are getting complete backups!
Mike
I just installed twrp and completed my first nand, the adv program said everything was fine. So I should be safe finally