yashsingh1/xdaforums huggingface dataset:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Chewieez:
I'm running Leedroid 3.8.2 and TWRP 3.1.1-0 and noticed that in TWRP, in Mount, it shows that "Keep System Read only" is checked. Shouldn't this be unchecked? I'm having some issues with the kernel setting that adjusts vibration voltage not sticking and I'm wondering if having system read-only is causing it. Is it safe to uncheck that setting in TWRP without doing a clean rom flash? Will it mess up encryption or anything?

It's strange because I have dirty flashed Leedroid twice since I first installed it and I would think TWRP would fail or give an alert if system was set to read only. But I don't fully understand the new methods with the HTC 10 in respect to encryption and keeping things read only or allowing modifications.

Thanks for the help!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
If you're running a custom ROM, it is safe to uncheck that box. That box has nothing to do with encryption.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] :
In official TWRP 3.1.1 changelog it says

What exactly is backed up?

Because I'm trying to update/dirty flash my current ROM without loosing adopted storage.

At the moment I get the message to format my sd-card after dirty flashing.

Maybe if I just restore adopted storage keys, I can still use it after dirty flashing without formatting my sd-card?

I tried to backup vold folder in data\misc and restore it after dirty flashing the ROM, but it wasn't working. It still shows me the message to format my sd-card, because it's not supported.

After restoring the whole TWRP backup I was able to use adopted storage again without any problems.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] RoMadrid:
does it work on the nougat update (rooted)?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Magnum_Enforcer:
If you're referring to the latest TWRP version 3.1.1-0, it works fine.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] RoMadrid:
i ment the stock rom of the htc 10 with android 7.0 nougat.

u say that the twrp 3.1.1 will work for me?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
TWRP doesn't care what version of Android you're running, so as you were already told, it will work fine.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] enduromen:
hello

i have a backup of 2.41.401.3 done with TWRP-3.0.3-0_UNOFFICIAL can i restore it with 3.1.1-0 version?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
As long as the backup isn't corrupt, it should restore fine.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] enduromen:
thanks for your answer

can someone please tell me how many time take the phone reboot do system after a system+boot restore( more or less of course)

it take a long long time more than 15m? i ask than becouse i did it becouse i stay in HTC green logo e suposing the phone is bricked flash a RUU.exe

But i need do to it again becouse i need too stay READ ONLY state to take OTA and i guess just flash a RUU dont solve my problem
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Black-FR:
If you before had modified framework files and then switch back to stock, by flashing system.img and boot.img, a boot time of 15-30 minutes is pretty normal on the m9.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Guys I have problem with restore Data partition. When I was in 95% recovery I saw

extractTarFork() process ended with ERROR=255

and backup restore was stopped. I have last version of TWRP 3.1.1.0.

I try unmount data partition but nothing.

Could You help me?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ali nz:
Yes but with log
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
recovery log was 22 mb but I zip them
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
In the backup folder there's a copy of the recovery.log that was made during the backup. Can you compress and upload that so I confirm it's the "leaked string" problem.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
I'll just leave this here for you in case it is your problem https://xdaforums.com/showpost.php?p=73507866&postcount=154
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
recovery.log
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
This is linux software. I have only Windows 7. So this two aplication cant run in system :(

Thanks for Yours help :)

I try compile this code to x86 but I can`t. Did You know where is compiled version?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Yep leaked string problem again :mad:

Sorry, I'm not the one that made the apps, I never even tried them myself, I just found the problem :angel:

But it's relatively easy to fix the backup, even in Windows using a normal hex editor.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Thx mate.

Im very grateful for Yours time. I try hex editor :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Make sure to remove only the leaked strings i mentioned, no more no less (including the ending 0x0A)

I would make a copy of them first, just in case, and no need to worry about .win000, only .win001 and above
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] yldlj:
I had the same problem a few days ago. I just ended up clean flashing tho.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PunishedSnake:
What am I doing wrong? Latest nougat firmware, unlocked boot loader, installed twrp via fastboot then installed rom, but stuck in boot loop with htc screen and red letters.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] yldlj:
Obviously you installed the ROM with twrp so this is not a twrp issue. Check your ROM md5
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PunishedSnake:
Did that twice downloaded different ROMs all bootlooped. Even the stock back up
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
You haven't provided any real details, including what's requested in the OP. So, no one will really be able to help you.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PunishedSnake:
Logs most likely gone, just RUU'd back :'(

Given how straightforward the process is,didn't think logs were that important.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Mr Hofs:
Logs are always important, the more info the better. Just like i kindly asked for more info on your ram management issues in the Q&A section which you keep ignoring. If you don't want help than it's better not to post questions.

Solving problems is always a 2 way street :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PunishedSnake:
For some reason Mr hof is in my ignore list...did ya troll me sometime ago or something? Which ram management post?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] xunholyx:
I think he meant "RAN Management" on the 10 Q&A Forum ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Mr Hofs:
Never mind. If you don't know what posts you started.....just leave me on the list, probably for the best.

Edit : troll ? No i don't troll, i just tend to tell the truth straitforward and sometimes people seem to take that the wrong way.

Let's get back on TWRP topic......

Good luck on the issue, hope you will solve it soon.

:)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PunishedSnake:
OK?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] EVOuser94:
The ROM has to be for the firmware you're using....
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] PunishedSnake:
Doubt that was the problem would boot loop with the stock rom when restored.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Twrp 3.1.1.0 - htc 10 2.41.401.41

I have problem with restore data partition in TWRP 3.1.1.0. I`ts second time when my backup was stopped when restore process is 50%.

Than TWRP shows:

extractTarFork() process ended with ERROR: 255

Part of my recovery.log

I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/FA***********/2017-10-02--15-07-58_DATA/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/FA**********/2017-10-02--15-07-58_DATA/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
https://xdaforums.com/htc-10/development/recovery-twrp-touch-recovery-t3358139/post73706529
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Maybe it`s still leaked string problem? How check this? Log is big so I can check by myself. Please give me short tut.

thx Mate :)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Open data.ext4.win00

1

using a hex editor, go to: "end of file - 1024 - 14" and check if there's a text there "I:Closing tar", if yes then it's the leaked strings problem.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
I:Closing tar

49 3A 43 6C 6F 73 69 6E 67 20 74 61 72 0A

It`s leaked strings :(

How fix it in Hex editor? I use WxHexeditor 0.23

....

In Broken archive I found this file "effect_endpoint_update" maybe this is some kind of twrp mark when failer?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
https://xdaforums.com/showpost.php?p=73507866&postcount=154
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Thank You but I don`t have a linux to compile this stuff. Maybe autor of this aplication give us win32 version?

P.S. I found something else...in broken archives I don`t see

I:Closing tar
Splitting thread ID 0 into archive 1 (or 2 or 3....)

I:Closing tar

is only on end of log. In good archives Data backup is partial too and before next part is

I:Closing tar
Splitting thread ID 0 into archive 2...
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] mick_soul:
The TarCleaner there seems to be a comand line .exe for windows.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Do You have link to this software?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] mick_soul:
It is the second linke nkk71 has posted.

Follow this project to TarProject/TarCleaner/bin/Release/ and try the TarCleaner.exe
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Thank You [MENTION=484498]Mike_S[/MENTION]oul I skip them. I download Release and Debug version but both doesn`t work on Win7. This is Dos 16 version I think :( Aplication start and was stopped with error. I use this files

TarCleaner.exe *.tar **.tar and with param -V
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] mick_soul:
It's working for me on Win10.

Did you download the file correct?

Do not use params!

And sorry for OT
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] wetxxx:
Yes I try both version od files but nothings . With or without parameters doesn't work. Maybe Windows 7 makes some problem.

"Live long and prosper"
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Not that this has anything more to do in here, but I just tried it:

C:\Users\nkk71\BROKENTAR>TarCleaner.exe

Enter file to clean:

data.ext4.win002

Enter copy file name:

fixed_data.ext4.win002

1243752960 Leaked file: /data/user_de/0/com.google.android.youtube/code_cache/com.android.opengl.shaders_cache

1243855966 Leaked file: /data/user_de/0/com.htc.dialerservice/

1247263932 Leaked file: /data/user_de/0/com.google.android.apps.docs.editors.docs/code_cache/

1247295770 Leaked file: /data/user_de/0/org.adaway/code_cache/com.android.opengl.shaders_cache

1247580024 Leaked file: /data/user_de/0/com.htc.soundrecorder/shared_prefs/

1247846358 Leaked file: /data/user_de/0/com.htc.contacts/no_backup/

1247944756 Leaked file: /data/user_de/0/com.android.nfc/

1248125074 Leaked file: /data/user_de/0/com.google.android.apps.tachyon/code_cache/

1248186608 Leaked file: /data/user_de/0/com.htc.usage/code_cache/

1248440654 Leaked file: /data/user_de/0/com.htc.cs.identity/

1297777068 Leaked file: /data/user_de/0/com.dsi.ant.server/

1298084362 Leaked file: /data/user_de/0/com.google.android.backuptransport/

1298358888 Leaked file: /data/user_de/0/com.htc.android.mail/code_cache/

1299022534 Leaked file: /data/user_de/0/com.android.vpndialogs/

1299075876 Leaked file: /data/user_de/0/com.google.vr.vrcore/

1299100546 Leaked file: /data/user_de/0/com.android.wallpaperbackup/code_cache/

1299170272 Leaked file: /data/user_de/0/com.htc.dotmatrix/

1299174462 Leaked file: /data/user_de/0/com.android.location.fused/cache/

1299362972 Leaked file: /data/user_de/0/com.htc.android.worldclock/code_cache/

1303794938 Leaked file: /data/user_de/0/venom.theme.prism.Venom_Underlays/

1408467288 Leaked file: /data/magisk_debug.log

Clean time: 20 seconds

And the output file looks *correct-ish*, cannot say if is or not, but better than before.

Anything else, and I'd take it up with the dev of the app. And yeah, I don't understand the output either, but everyone has a different perspective, on verbosity so if that's what he needs then that's what it will be. :good:

(PS: Windows10, but doubt it would matter what version you're running)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] KotTHECat:
Hello,

i cant restore my backup from external SD card. I also tried to move it to the internal storage and restore it from there, but still no success; the process ends by ~42% with "extractTarFork() process ended with ERROR: 255"

This is the first time i have such a problem with restoring data from ext_sd.

Here is the link to recovery log.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Mr Hofs:
Think that's related to this
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] biker57:
I have a couple of things involving Titanium Backup after flashing the Pure Fusion Oreo rom.. First I had my backups stored on an ext card and I can't get TB to see them, but I can with file manager etc. I moved them to internal storage so I could restore them for the time being.The other thing is when I try to go to the main menu in the upper left of the main TB screen it goes straight to the batch menu so I don't have the option of being able to restore my messages, calls and wifi.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gorm:
Wrong forum.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] biker57:
Instead of just telling me this was the wrong forum can someone tell be which one would have been better.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] myheroduane:
Pure fusion thread or titanium backup thread.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
I had 3 different TWRP backups. Now, every one of them is corrupted by extractTarFork. I tried TarCleaner.exe but it does not work for me on Win10. I runned is as admin, it works for 30 minutes without any progress in command windows and then ejects 1KB backup file. I am just fed up with no reliability from TWRP now. I can not restore my phone.

Is there any other way to make a reliable backup of my phone? Preferably complete image of the nand? Any other software or solution? It is pointless completely to do backups which become unusable after some time because of no reason.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Well I ran it two posts above, my command prompt output is quite clear, where's yours?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
Mine is clear after specifying name of the backup file, that's the problem. The TarCleaner process is utilizing cpu with ~20-30% for 30 minutes and then it makes a specified backup file which has only 1KB comparing to 800MB original one.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Other than the part that i don't double click an cmd line tool, i also wouldn't bother with win000, since that will not be corrupt (if it is the "leaked strings" problem), I can't if it is or not given the information provided, but if it is, then you can start at 001 and above, the 000 will never be corrupted.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] hoang555:
The latest TWRP v3.1.1.0 is unable to recognize 128GB (and above) external SDCard, is that correct ?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] sgtslaughter64:
It works fine for me.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Nope.

I'm using a 200GB sdcard and it works fine. Why not upload your recovery.log that should could some relevant information in it.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
I tried launching TarCleaner via cmd line, laso by just double clicking the exe (as administrator). Same effect. Nothing happens besides stressing cpu for ~30min and ejecting 0 or 1KB file. I am launching this as default and only administrator account in Win10.

I literaly do not have a clue what is wrong. And right now I do not have any viable backup option to protect my phone. I am completely hopeless.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Where is your updated command prompt output from running the tool on win001 instead of win000?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
I attached it now.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
And how about a "DIR" listing too, for all we know, the files didn't copy over properly. Did you transfer via a card reader or MTP?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
I am copying entire BACKUP directory with it's sub dirs structure like:

BACKUPS\FA64DBN02569\2017-09-24--01-39-43_NRD90M_release-keys

from internal storage to my PC with wifi ftp from Solid Explorer. But does it matter how I copy it from Internal storage to pc for TarExplorer to work properly? Right now I have "original" files stored on Internal memory in my phone and they cant be restored by TWRP. Moving them to pc can corrupt them even more?

Is it possible to fix the error in TWRP itself, so it would not create corrupted files? Or maybe I should use diffrent option, like System Image backup in TWRP or sth?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Well I just tried again, here you go: (Windows 10 64bit by the way)

C:\Users\nkk71\Downloads\BROKENTAR>dir
Volume in drive C is Windows
Volume Serial Number is 68F9-92CE

Directory of C:\Users\nkk71\Downloads\BROKENTAR

03/11/2017 17:38 <DIR> .
03/11/2017 17:38 <DIR> ..
14/06/2017 14:30 1,408,514,918 data.ext4.win002-og
17/08/2017 20:16 34,816 TarCleaner.exe
4 File(s) 2,785,404,645 bytes
3 Dir(s) 19,455,123,456 bytes free

C:\Users\nkk71\Downloads\BROKENTAR>TarCleaner.exe
Enter file to clean:
data.ext4.win002-og
Enter copy file name:
xdata.ext4.win002-og
1243752960 Leaked file: /data/user_de/0/com.google.android.youtube/code_cache/com.android.opengl.shaders_cac
1243855966 Leaked file: /data/user_de/0/com.htc.dialerservice/
1247263932 Leaked file: /data/user_de/0/com.google.android.apps.docs.editors.docs/code_cache/
1247295770 Leaked file: /data/user_de/0/org.adaway/code_cache/com.android.opengl.shaders_cache
1247580024 Leaked file: /data/user_de/0/com.htc.soundrecorder/shared_prefs/
1247846358 Leaked file: /data/user_de/0/com.htc.contacts/no_backup/
1247944756 Leaked file: /data/user_de/0/com.android.nfc/
1248125074 Leaked file: /data/user_de/0/com.google.android.apps.tachyon/code_cache/
1248186608 Leaked file: /data/user_de/0/com.htc.usage/code_cache/
1248440654 Leaked file: /data/user_de/0/com.htc.cs.identity/
1297777068 Leaked file: /data/user_de/0/com.dsi.ant.server/
1298084362 Leaked file: /data/user_de/0/com.google.android.backuptransport/
1298358888 Leaked file: /data/user_de/0/com.htc.android.mail/code_cache/
1299022534 Leaked file: /data/user_de/0/com.android.vpndialogs/
1299075876 Leaked file: /data/user_de/0/com.google.vr.vrcore/
1299100546 Leaked file: /data/user_de/0/com.android.wallpaperbackup/code_cache/
1299170272 Leaked file: /data/user_de/0/com.htc.dotmatrix/
1299174462 Leaked file: /data/user_de/0/com.android.location.fused/cache/
1299362972 Leaked file: /data/user_de/0/com.htc.android.worldclock/code_cache/
1303794938 Leaked file: /data/user_de/0/venom.theme.prism.Venom_Underlays/
1408467288 Leaked file: /data/magisk_debug.log
Clean time: 25 seconds

C:\Users\nkk71\Downloads\BROKENTAR>dir
Volume in drive C is Windows
Volume Serial Number is 68F9-92CE

Directory of C:\Users\nkk71\Downloads\BROKENTAR

03/11/2017 17:40 <DIR> .
03/11/2017 17:40 <DIR> ..
14/06/2017 14:30 1,408,514,918 data.ext4.win002-og
17/08/2017 20:16 34,816 TarCleaner.exe
03/11/2017 17:40 1,408,513,024 xdata.ext4.win002-og
5 File(s) 4,193,917,669 bytes
3 Dir(s) 18,046,586,880 bytes free

C:\Users\nkk71\Downloads\BROKENTAR>
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
The fix for this issue has already been merged into upstream TWRP. But that won't help you restore any old backups.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
Jesus it is driving me mad... I am running genuine Win10 64bit Pro. I do not have any additional antimalware or antivirus software besides built in Win Defender which is not reporting and blocking anything related to those actions. I completely do not know what is happening.

What do you mean upstream TWRP?

I am using latest version pretty much from the time it was released (twrp-3.1.1-0-pme). It was updated in the meantime?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
Yes, the TWRP code has been updated, but a new build hasn't been run.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
In the folder (on the device) where your backup is, there should be a recovery log, can you upload that, just to confirm it is the leaked strings problem, cause in your Screenshot the files look like they're being split at less than 1GB, whereas TWRP should be splitting at 1.5GB
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
I do not know why I do not have a recovery log in my latest backup I was mentioning above but I have it in my second previous backup. I have downloaded all backups to my PC and formatted Internal storage and ran RUU to restore my phone to working condition quickly.

I attached in this post screen with my dir structure of my second backup: 2017-09-02--13-00-18_NRD90M_release-keys and also attached recovery.log from my second backup. I have 3 backups and all of them are corrupted according to TWRP.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Can't read logs on the phone properly, but are you using compression? If so then it's not a leaked strings issue, that only affects uncompressed and/or unencrypted backups
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] cavist:
I can not paste the log into pastebin, it is over 4MB. But I have closing tars in it:

D:\Google Drive\Backup\M10\TWRP_LeeDroid\BACKUPS\FA64DBN02569\2017-09-02--13-00-18_NRD90M_release-keys\recovery.log (7 hits)
Line 6611: I:Closing tar
Line 10114: I:Closing tar
Line 10159: I:Closing tar
Line 47524: I:Closing tar
Line 48596: I:Closing tar
Line 49614: I:Closing tar
Line 53108: I:Closing tar

Yes, the backups are compressed. They should not be?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
I was just referring to the fact that compressed and/or encrypted backups do not suffer from the potential leaked strings problem.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Captain_Throwback:
I would recommend uncompressed and unencrypted - that gives you the best chance of being able to successfully restore. Here's an updated test build of TWRP which should include the fix for the leaked strings problem. Then you shouldn't have any issues restoring.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
That is perfectly normal, and actually proves you don't have the leaked strings issue. To clarify, the leaked strings would be the ones you are seeing in your recovery.log ending up in your tar file, so (with the exception of the first one) they wouldn't show up in your recovery.log at all and instead get leaked into the tar.

So their presence in the recovery.log means they did not get accidentally pushed into the backup tar files.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] romixer:
test version works fine.... along with material theme too ;)