So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2
Related
Now that the recovery has been made sticky on the later versions of the One-click-root, how would I go about restoring the original stock Recovery if I ever wanted to?
I'd rather prefer it not to be sticky, or at least the script for restoring it to be renamed rather than deleted, so I can run it manually later to restore the original recovery if needed.
I haven't run the run.bat script yet, and would appreciate help in the process to backup the recovery and be in a good situation for allowing full roll back before I do the rooting.
ggggg1 said:
Now that the recovery has been made sticky on the later versions of the One-click-root, how would I go about restoring the original stock Recovery if I ever wanted to?
I'd rather prefer it not to be sticky, or at least the script for restoring it to be renamed rather than deleted, so I can run it manually later to restore the original recovery if needed.
I haven't run the run.bat script yet, and would appreciate help in the process to backup the recovery and be in a good situation for allowing full roll back before I do the rooting.
Click to expand...
Click to collapse
Assuming you're using this: http://forum.xda-developers.com/showthread.php?t=1138755
Just extract root.zip, go into the updater-script and remove the line:
delete("/system/etc/install-recovery.sh");
Save the file, repack the zip and continue (you can turn off signature verification in CWM)
You can easily rename it using adb, remounting /system manually, or via root explorer or a similar app once rooted.
Excellent, thanks; I'd seen that delete of the .sh , but wasn't sure if removing it would allow the rest of the bat or it would break further down expecting it to have been removed and a reboot to go back to CW.
Thanks!
So I got a phone with cryogen7 or whatever from my friend. I want to make it completely stock again. I dont have his sd card. so I just have mine from another phone. I downloaded the stock g2x gingerbread file, but when I try to restore it, i get a md5 mismatch or something. I saw a thread on that but I dont know how to write code. just hoping someone could help me out. thank you.
Download it again, also try another browsee
Sent from my LG-P999 using Tapatalk
Download the V21E nandroid from this thread:
http://forum.xda-developers.com/showthread.php?t=1196019
Then use your computer to extract the folder from the zip file you download. Copy that folder to the sdcard on your phone, and place it in the ./clockworkmod/backup directory. Then boot into clockworkmod recovery and select backup/restore > restore and then choose the backup folder you just copied to your sdcard. Make sure to do a full wipe/factory reset from within clockworkmod before you reboot or you might get a bootloop.
If you want stock recovery then use tga gunmanns one click app in the development section to restore stock recovery. Then you'll be 100% unrooted stock again.
IF the name of the zip has spaces in it it wont flash
Mister Hat said:
IF the name of the zip has spaces in it it wont flash
Click to expand...
Click to collapse
Nandroid backups aren't flashable zips. With the files from the thread i linked to, you have to extract the backup folder from the zip before you restore it. But yes, you are correct that spaces in the name of the backup create issues.
Did you figure it out yet?
Sent from my LG-P999 using XDA App
it freezes on "checking md5 sums"... don't know what to do
Are you using your computer to extract the V21E folder from the zip file? Ive used my phone before to extract it before and gotten the md5 mismatch error, and then used my computer to do it and it worked fine.
are you sure the rom your using is for your phone?
Normally I did backups from the ROM Manager app, but this last time I did a backup from ClockworkMod 5.0.2.2 recovery menu. When I tried to restore it, I get MD5 mismatch.
I found a thread with instructions for creating a new MD5 but it seems some of the files that are supposed to be in the backup folder aren't there. Here's what I have in this folder:
.android_secure.vfat.tar (yes, .tar ext)
boot.img
data.yaffs2.img
nandroid.MD5 (This file was not there before I created it)
recovery.img
system.yaffs2.img
The instructions I found for creating the MD5 file additionally had .android.secure.img, cache.img, data.img, sd-ext.img and system.img, although I suspect the .android_secure.vfat.tar = .android_secure.img, data.yaffs2.img = data.img and system.yaffs2.img = system.img so the only ones I actually seem to be missing are the sd-ext.img and cache.img.
I think all of the meat and potatoes are there. I just need to find some way to get them restored.
I found some posts that suggested to mv md5sum but I don't have this file so this is not an option.
Like a moron, I dumped all of my other back-up to save space before checking that this one worked.
Harry Seaward said:
Normally I did backups from the ROM Manager app, but this last time I did a backup from ClockworkMod 5.0.2.2 recovery menu. When I tried to restore it, I get MD5 mismatch.
I found a thread with instructions for creating a new MD5 but it seems some of the files that are supposed to be in the backup folder aren't there. Here's what I have in this folder:
.android_secure.vfat.tar (yes, .tar ext)
boot.img
data.yaffs2.img
nandroid.MD5 (This file was not there before I created it)
recovery.img
system.yaffs2.img
The instructions I found for creating the MD5 file additionally had .android.secure.img, cache.img, data.img, sd-ext.img and system.img, although I suspect the .android_secure.vfat.tar = .android_secure.img, data.yaffs2.img = data.img and system.yaffs2.img = system.img so the only ones I actually seem to be missing are the sd-ext.img and cache.img.
I think all of the meat and potatoes are there. I just need to find some way to get them restored.
I found some posts that suggested to mv md5sum but I don't have this file so this is not an option.
Like a moron, I dumped all of my other back-up to save space before checking that this one worked.
Click to expand...
Click to collapse
If you made the backup using a version of clockwork that wasn't 5.x.x, it can't be restored. To restore it you need to downgrade your clockwork, only if that was the case...
lowandbehold said:
If you made the backup using a version of clockwork that wasn't 5.x.x, it can't be restored. To restore it you need to downgrade your clockwork, only if that was the case...
Click to expand...
Click to collapse
I'm not sure which version of Clockwork I used, but I'm almost positive it was the latest version. Is there a way to tell from the files or a .log or something?
No there isn't. Just be aware, the new version is fairly new. It might be worth a shot to downgrade it and try that. You can downgrade right through ROM Manager...simple process.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
lowandbehold said:
No there isn't. Just be aware, the new version is fairly new. It might be worth a shot to downgrade it and try that. You can downgrade right through ROM Manager...simple process.
Click to expand...
Click to collapse
Some other info that may be important.
The backup I'm trying to restore is from a gingerbread rom. I'm currently on the Sprint Lovers 3.70.xxx ROM. Do I need to flash to a GB rom first?
Harry Seaward said:
Some other info that may be important.
The backup I'm trying to restore is from a gingerbread rom. I'm currently on the Sprint Lovers 3.70.xxx ROM. Do I need to flash to a GB rom first?
Click to expand...
Click to collapse
No, that shouldn't be an issue.
lowandbehold said:
If you made the backup using a version of clockwork that wasn't 5.x.x, it can't be restored. To restore it you need to downgrade your clockwork, only if that was the case...
Click to expand...
Click to collapse
Will this throw an MD5 mismatch error?
As i am sure that it is to late, i will share anyway.
I had the same problem and found the same way to fix it that didn't apply.
so after sitting in front of my computer for hours, it dawned on me. What was i doing different? I created the backup in Rom Manager, but was trying to restore in CWM. So After getting back into an old restore, i launched Rom Manager and it's restore feature with great success. Well almost great...
There are some launcher settings that need to be reset and a couple of widgets that need some tweaking, but the call log and all of my text messages are there.
I hope it helps
Same problem here: md5 mismatch!
Some facts: (device LG Optimus 3D)
1. Backup was made just on November 26, 2011, just a few days ago, so I presume no new version of ROM Manager + Clockworkmode Recovery has been released,
2. Backup was created from ROM Manager (which restarts in Recovery mode after),
3. I have no spaces on my Backup name: 2011-11-26-17.11.47,
4. Backup was made to sdcard (not _externalSD),
5. Looking at the log in the Recovery Mode (log is in Advanced) says that md5 fails only in file .android_secure.vfat.tar,
6. I have downloaded and installed md5Calc.msi (Win7, 64 bits) from http://www.bullzip.com/download.php and performed the generation of md5 for that file, and it's THE SAME which figures on file nandroid.md5,
7. I've deleted from nandroid.md5 the checksum and reference to .android_secure.vfat.tar,
8. Now, the md5 problem not happens but restoration fails in system.ext3.tar...
Now, I'm stucked, I can't even boot beyond Recovery...
Any ideas will be appreciated...
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
mafo5000 said:
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
Click to expand...
Click to collapse
Here's a few things you could do assuming that what you want is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
hachamacha said:
Here's a few things you could do assuming that what yowant is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
Click to expand...
Click to collapse
OK Ill see if the titanium backup way works. I'll report back to you if it works. Also if I do get all my apps back is there a way to get the app data?
Hi - If Titanium is bringing up the selections screen then the usual choices for each app are data/app/data+app, so yes.
The titanium back option is called "extract from Android backup" I can't do
It right now because I don't have my tf with me. But I don't think it will work because
The Android backup I made was currupted. I would get the .android_secure error
And couldn't restore. So if titanium takes the data.img from my Android I'm thinking
It won't work but if I can give it the zip it probably will. I won't be home for a couple
Hours.
thank you so much i got all my stuff back using titanium backup!
mafo5000 said:
thank you so much i got all my stuff back using titanium backup!
Click to expand...
Click to collapse
Cool! --
Congrats.
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
silentecho13 said:
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
Click to expand...
Click to collapse
Not sure if it's available in the Free Version but Titanium Backup allows you to extract from a Nandroid backup.
I just checked and it gave me a listing of all the apps I have installed and there was one listed as Messages, I can only assume that it's my texts.
Yes I do have the paid version. I tried restoring both Go SMS and the Messages app from TiBu using my TWRP backup, but they basically just reinstall the app. I still have no messages in either app :/
I didn't realise TiBu was Titanium - how retarded of me... haha
Any chance of backing this one up restoring the other nandroid and then backing up the txt's from within the stock messaging app then restoring?
Unless someone else knows how open .win files
I did think of that, but I don't want to run the risk of a corrupted restore. I've had it happen s bunch of times, unfortunately.
Sent from my HTC One X using xda premium
silentecho13 said:
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
Click to expand...
Click to collapse
Yep, it's fully possible. Just get the nandroid backup file, and make a copy and change the extension to .zip After that just unzip, and volia. A bit of searching (should be in the apps file, I forgot the details).
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Yep, it's fully possible. Just get the nandroid backup file, and make a copy and change the extension to .zip After that just unzip, and volia. A bit of searching (should be in the apps file, I forgot the details).
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
....so I saw this too late.
I went and restored my backup, grabbed the files, and restored the new backup hoping that neither were corrupted.
It all went smoothly, but I'll definitely remember this for the next time I mess up...haha.
Thanks!
silentecho13 said:
....so I saw this too late.
I went and restored my backup, grabbed the files, and restored the new backup hoping that neither were corrupted.
It all went smoothly, but I'll definitely remember this for the next time I mess up...haha.
Thanks!
Click to expand...
Click to collapse
Glad I could help, almost everything that uses the term "compressed" seems to be able to be turned into a .zip
Sent from my HTC One XL using xda premium
Sorry I'm not following this. I made a twrp backup using 2.5.0.0 and I got a bunch of .WIM files.
7-Zip recognizes those and opens them to have a .ext4 file. However every ext browser and mounter (in windows) I've tried can't seem to browse them. I tried renaming them zip, but I'm guessing I'm doing something wrong.
With old CWM releases, my backups were tars which were easily browsable.
Am I missing something?
Thanks!
eldamobo said:
Sorry I'm not following this. I made a twrp backup using 2.5.0.0 and I got a bunch of .WIM files.
7-Zip recognizes those and opens them to have a .ext4 file. However every ext browser and mounter (in windows) I've tried can't seem to browse them. I tried renaming them zip, but I'm guessing I'm doing something wrong.
With old CWM releases, my backups were tars which were easily browsable.
Am I missing something?
Thanks!
Click to expand...
Click to collapse
I know this is an old post, but it's the first Google result.
What you want to do is rename the .wim file to .tar.gz, then extract the file (command line is tar -xvzf filename.tar.gz). If you look at the TWRP logs it indicates that it uses tar to create the archive file.
uberamd said:
I know this is an old post, but it's the first Google result.
What you want to do is rename the .wim file to .tar.gz, then extract the file (command line is tar -xvzf filename.tar.gz). If you look at the TWRP logs it indicates that it uses tar to create the archive file.
Click to expand...
Click to collapse
Thanks uberamd. I'll give this a shot. I guess I should have checked the logs. Tar would be great!
hi there.. i made backup too.. now i want to bring back the boot.img and recovery.img..
most of guys said to me the " boot.emmc.win " is the stock boot.img.. but this one is 16 MB and other boot.img i saw till now are 6 MB..
and how can i restore the stock recovery? does the backup contain the recovery?
any idea?
N5 TWRP Backups
I made a backup with TWRP, and copied the .WIN files to my PC. Tried renaming those to .ZIP or .tar.gz, but 7zip could not open either of those!?
Are you guys sure the backups are actual zip or tar/gz files?
EDIT: Nevermind, I renamed to .tar and it opened. I suppose compression is not enabled by default
Except the data.ext4 is splitted in two files: data.ext4.win000 and data.ext4.win001 and renaming either of those to .tar, .zip or .tar.gz doesn't help
Just a guess here but what if you concatenated the files together?
If you can post the details from the twrp log that would also probably help.
eldamobo said:
Just a guess here but what if you concatenated the files together?
If you can post the details from the twrp log that would also probably help.
Click to expand...
Click to collapse
Yes concatenating can help however all those .WIN files are either .tar files or .tar.gz (if compression is enabled). That's quite simple in the end, except that 7zip doesn't always recognize the format properly. If I open the system.win file, it only shows about 60MB of files, whereas the whole .win file is 600MB uncompressed, hence I was confused about the format.
I've been able to update my app to read those .tar, .tar.gz and extract any file from it now Pretty cool!
Be advised though, for some reason when I rename the backup to .tar or .tar.gz for twrp 2.6.3.1, it doesn't want to open or extract. I don't know if it's only happening only for t-mobile sgs3 or the developer removed the ability for us to do it. But I did revert it back 2.6.3.0 and it's working fine for me. Thought I want to just throw it out there.
-VIPLightning
VIPLightning said:
Be advised though, for some reason when I rename the backup to .tar or .tar.gz for twrp 2.6.3.1, it doesn't want to open or extract. I don't know if it's only happening only for t-mobile sgs3 or the developer removed the ability for us to do it. But I did revert it back 2.6.3.0 and it's working fine for me. Thought I want to just throw it out there.
-VIPLightning
Click to expand...
Click to collapse
That's interesting. Which app are you using to open those TWRP backups? Asking because I found out that many extractor are unable to open those in the first place! 7zip for example showed me a 80MB content while the file was 600MB! And I'm using a very old 2.6.0.0 TWRP, so I got to try this last version out
Would you mind trying Android Tuner Free, last update allows opening those .tar and .tar.gz files, but got to rename the TWRP backup to either of those first. It won't open the tar inside the gz file, but you should be able to extract it and then open it If you don't have the time, I can understand, but hopefully you still have a 2.6.3.1 backup file around?
3c said:
That's interesting. Which app are you using to open those TWRP backups? Asking because I found out that many extractor are unable to open those in the first place! 7zip for example showed me a 80MB content while the file was 600MB! And I'm using a very old 2.6.0.0 TWRP, so I got to try this last version out
Would you mind trying Android Tuner Free, last update allows opening those .tar and .tar.gz files, but got to rename the TWRP backup to either of those first. It won't open the tar inside the gz file, but you should be able to extract it and then open it If you don't have the time, I can understand, but hopefully you still have a 2.6.3.1 backup file around?
Click to expand...
Click to collapse
I should have no problem giving it a try. Yeah I deleted my backup. I'll go ahead and update the recovery when I get a chance to later on. Then I'll make another backup And the program I used for extracting and opening was WinRAR. Everytime I tried to, the 2.6.3.1 backup would always come up as corrupted or damaged.
EDIT: So I tried out your app. Indeed the explorer does work. Thanks so much. Even though first it took some time, I was able to get to my stuff. But it was worth it. I've never seen an app that can actually do so much. Thanks again.
-VIPLightning
What are WIN files?
Along with win and md5 files TWRP creates recovery.log file. If you look inside this file, you can see the full log of what TWRP has done. There you can notice that win file with the boot partition is in fact a result of the dd command, so that's a bit-to-bit copy of the boot partition, sometimes named as .img file.
Other partition win files are tar files. If you used compression, you got .tar.gz files.
So .win files are raw partition data, .tar, or .tar.gz files. See recovery.log
If you use compression in TWRP, just rename the .win to .tar.gz
i.e data.ext4.win to data.ext4.tar.gz , then use tar -xvzf , extracts perfectly fine.
I used this to extract my apps from a TWRP backup just now.