I tried both Paul's version and the latest clockworkmod recovery from ROM Manager, but both of these would put wrong backup dates in the backup image files and folder. What's wrong? The phone or the recovery program??
It's a bit inconvenient, since if i rename to the correct date/time, the MD5 checksum would be wrong, so I need to keep the wrong ones as well.
What I observed is that the month is always +1 and the time is always using UTC timezone.
dohanin said:
I tried both Paul's version and the latest clockworkmod recovery from ROM Manager, but both of these would put wrong backup dates in the backup image files and folder. What's wrong? The phone or the recovery program??
It's a bit inconvenient, since if i rename to the correct date/time, the MD5 checksum would be wrong, so I need to keep the wrong ones as well.
What I observed is that the month is always +1 and the time is always using UTC timezone.
Click to expand...
Click to collapse
i am definitely noobie, so i could be totally wrong. please anybody correct me if say something totally absurd.
md5 checksum is for individual image files, not entire directory. for example mine is
# cat nandroid.md5
ee5f9313d30caa0956a8a6b24f75ddfa boot.img
8786667ac7d45546156b2e19bc0168cf cache.img
4b3fda00aa2255e2314fbbd20fa22d5d data.img
d4de133f5d712f7164151f319cebb728 recovery.img
93c71d12eab5c13d2a66e08a1b346696 system.img
i don't think renaming the directory will affect any md5 checking. sure, it is a bit inconvenient, but not the end of the world, i guess. maybe you can copy whole directory, rename it, and do recovery see if that works.
i agree wrong date is probably bug, and should be fixed.
as for time, i'm guessing (and i'm totally guessing here) that system is using UTC and get timezone information from network, so that clock is always correct even though you travel other region, instead of using local clock and figure out UTC. another reason i can think of is to use android market. i don't know why market checks time and date, but lots of people reported not being able to use market when date is set wrong. since market (or any other google servers) is kind of global, it is just easy to use UTC and then apply local time zone.
you may be able to disable getting clock from network by go and uncheck "Settings > Date & Time > Automatic" and manually set your local clock might do the trick ?
I have the same problem, its really annoying to restore several backups before you find the latest.
You can easily rename backups through ROM manager
I currently have backups named MCR14 and CM-nightly. I have them both on SD and internal memory due to CM switching them around.
pastime1971 said:
md5 checksum is for individual image files, not entire directory. for example mine is
Click to expand...
Click to collapse
yes, that's what I thought. But when I restore the whole backup (not individual img) in the clockworkmod recovery, it was not allowed. Then I renamed the folder to the original date/time, it passed. So, maybe the recovery program actually did check the files's dates against the folder name then? if not, then probably my new name was a bit long.
Did you put a space in the new name? It doesn't like them.
oh yes, then that's the reason.
now i use rom manager's interface, and it defaults the folder name to the correct date & time, that's good enough (although the actual file date/time still wrong)
Sent from my LG-P990 using XDA App
I have this issue as well and its bloody effing annoying. Makes it more of a hassle restoring your backups.
Please fix ASAP.
Not only that, but it sometimes changes the system date when flashing a new ROM to a month in the past as well...
Anybody know who the dev is (so we can let them know as they obviously don't seem to know about it)?
Sent from my LG-P990
withoutwings said:
Not only that, but it sometimes changes the system date when flashing a new ROM to a month in the past as well...
Anybody know who the dev is (so we can let them know as they obviously don't seem to know about it)?
Sent from my LG-P990
Click to expand...
Click to collapse
Amonth in the past I could live with. But CWM 3.2.0.0 ALWAYS puts mine a month in the future, so If I get a text/call before changing the date then that stays at the top of the list for a whole month. VERY silly schoolboy error.
I always rename backup folders, have been for a year. No issues.
Related
Anyone know if there is a way to give a nandroid backup a name of your choosing? Sometimes when I'm flash and loading a bunch of different stuff I like to do nandroid backups before each one so I can save my phone in various states. unfortunately that means that just the date and time stamp naming convention isn't enough for me to locate the exact one I want to restore.
DaveKid said:
Anyone know if there is a way to give a nandroid backup a name of your choosing? Sometimes when I'm flash and loading a bunch of different stuff I like to do nandroid backups before each one so I can save my phone in various states. unfortunately that means that just the date and time stamp naming convention isn't enough for me to locate the exact one I want to restore.
Click to expand...
Click to collapse
Yep, drag them to your pc and just rename them!
That's the easy way anyway.
Whenever I flash a new rom and I like it, I backup a full clean install so I can start from scratch again, it's better then going through the syncing and logging in again.
I also store mine on the pc, so if my card gets fubar'd then I've still got them.
great idea....never even considered that.
thanks
Not to sound rude, but I would think that'd be the most obvious solution to your question.. o_0
DaveKid said:
Anyone know if there is a way to give a nandroid backup a name of your choosing? Sometimes when I'm flash and loading a bunch of different stuff I like to do nandroid backups before each one so I can save my phone in various states. unfortunately that means that just the date and time stamp naming convention isn't enough for me to locate the exact one I want to restore.
Click to expand...
Click to collapse
Just use any file explorer (Astro, ES, etc.) and rename the backup file to anything you like...
i just tried to restore a nandroid backup, i did as above says, i went on the PC and re-named backup as something i`d remember put it back on the Desire, and nandroid just fails instantly at `MD5 mismatch`
could this be because the folder name changes after the backup has been made??, thanks.
You don't even need a computer to name your backups. All you need to do is download ROM manager from the market (the free version will suffice). Then whenever you need to make a nandroid backup, open the app, choose "Backup current ROM" and it will automatically ask you to name your backup from the get-go so that there aren't any problems afterwards.
DJ 1 said:
i just tried to restore a nandroid backup, i did as above says, i went on the PC and re-named backup as something i`d remember put it back on the Desire, and nandroid just fails instantly at `MD5 mismatch`
could this be because the folder name changes after the backup has been made??, thanks.
Click to expand...
Click to collapse
I get the mismatch failed sometimes if my battery isn't sufficiently charged. Renaming the folder won't mess up your backup.
If you use ROM Manager, it will allow you to specify the name of the backup before you create them and it generates the appropriate MD5 sum.
quahog_convo said:
If you use ROM Manager, it will allow you to specify the name of the backup before you create them and it generates the appropriate MD5 sum.
Click to expand...
Click to collapse
Which is exactly what I said just two post before this one.
when you rename a nandroid backup on your phone using a file explorer, don't put spaces when you rename it, putting spaces gives it an md5sum mismatch.
...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.
Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a
I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?
tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy
I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.
Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin
No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.
Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!
OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.
So... let's say that you didn't save your android id before you flashed... will that cause problems?
beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.
I was fooling around with new ROM's.
When i wanted to return to my previously backup i got the "MD5 Cheksum wrong"
I then had a look at the backup i wanted to use, and checked all of the checksums manualy (using a md5 checksum checker)..........all of the MD5's it the "nandroid.md5" were correct.
The only thing i had changed was the folder name........
Any syggestions on how i can get the backup to work?........or make it skip the MD5 checksum check?
Rename the folder back to what it was.
He he.......yes, i keept those 12 digits in my memory.......
/irony may occur in the previous sentence
But i renamed it on a hunch, and either i was extremely lucky, or "close" is good enough.......i doubt i got it right down to the seconds.
But i'm restoring it now.
For future use, can i make a folder with a name of my choice to put the backup in, and then restore from within that folder??
Yeah I'm guessing there is a 'close enough' element involved. As for moving it, I don't think you can unfortunately.
I suppose you could move it someplace and stick it back in the /clockwork/backup folder when you want to restore though. Not ideal, though.
You cant have any space in folder name...
Use underline _ instead
Sent from my LG Optimus 2x using XDA Premium App
Nice!
Thank you!
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
tramp20 said:
Hi,
Since 4 days I cannot make valid backups. The last good one is from October 12 and has a size of ~ 1000MB.
Now all backups have a size of ~13 MB. You can see the sizes on the attached hardcopy.
There is a \blobs\-subdirectory with many many files.
I tried to de- and reinstall the Rom Manager, checking permissions and so on, rebooted several times...
I restored the "good" backup, did a new backup and got other sizes of the files but always some with the extension .dup.
Even I installed an older version of RomManager without success.
The recovery system is v6.0.1.4 installed within the RomManager.
I have a LG-P970 with Zeus ROM 7.03.
Click to expand...
Click to collapse
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
N00BY0815 said:
You might wanna flash this: http://forum.xda-developers.com/showpost.php?p=22121547&postcount=22
Follow the instructions give there. The new CWM v6 doesnt make full backups anymore everytime, but just backs up the parts, that have been changed. The dup files only contain the information about the files that have been changed and a link to them I think. Look in /sdcard/clockworkmod/blobs. There you can find a lot of folders with the made changes Just check the size of that blob folder.
Click to expand...
Click to collapse
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
tramp20 said:
Thank you for answering.
So is it correct that I have a blobs subdir with ~ 1GB files and a small backup directory?
What happens to the \blobs\ dir if I make new backups? I assume then only changed files etc. will be added here?
Do I really need to flash your link if I don't need touch? I read the whole thread
I did not understand all.
Click to expand...
Click to collapse
The link I provided is for CWM touch 5 only. This version will make the "normal/full-sized" backups. I think you're right about the new update, but I gotta confess, I dont really understand it myself yet... I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
If your not sure about the old version, just install the one from the link I provided.
Hope it helped you, if not, you may also PM me.
N00BY0815 said:
I also didnt yet try to restore such a backup and dont really know, how to delete old ones, if you dont need them anymore, but I hope it all should work fine
Click to expand...
Click to collapse
To test:
I made a backup, installed a new app, then after another backup I looked in the blobs dir: only a few subdirs are new, all other remain unchanged.
So all files in blobs are cumulative and important for a restore, but bad for a later extern backup on my pc.
The old method of CWM was better.
Perhaps I will try the link from you.
I was trying a backup and found under "choose backup format" the following points:
- dup (default)
- tar
-
-
So I can choose
I did a backup (dup format) and all is working again.
Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)
Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working
Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.
I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app