Database Info

twrp error

Got twrp-3.0.3-0-berlin installed, everything works except when i do a full backup it fails with the following error createTarFork() process ended with ERROR=255
I pulled the recovery log (mentioned in the nexus forum) the backup process is failing at a file that relates to the stock gps function of andriod.

Last entries from the recovery.log
I:Error adding file '/data/gnss/suplstalepos.dat' to '/external_sd/TWRP/BACKUPS/HSMDU17110000532/2017-02-23--19-27-40/data.f2fs.win004'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/HSMDU17110000532/2017-02-23--19-27-40/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/HSMDU17110000532/2017-02-23--19-27-40/recovery.log
Click to expand...
Click to collapse

https://forum.xda-developers.com/ho...p3-0-2-emui-4-1-one-click-root-built-t3532737
flash this recovery

Thanks kdark, but i already tried that. Both versions same error.

Did you find a solution to this?

No, however you can do a twrp backup of all but the data. That worked and I just backup my data with titanium backup.

Cannot get rid of TWRP 255 Error

Hello, i recently installed TWRP 3.1.1-1 as well as LineageOS, everything was working fine and i did a backup of the ROM (with root, xposed and all my settings and datas).
For some reasons i wanted to restore this backup but i cannot do that, the process stops at 54-55% while restoring datas :/ I get error 255 and when i look at the twrp log i see that "dataf2fs.win001" is the archive that cannot be extracted, when i delete it i can restore just fine but this is a 1,5 Gb file which contains important files.
Here is the end of the log:
extracting: //data/user_de/ (mode 40711, directory)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/73QDU16909001751/new lineage/data.f2fs.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/73QDU16909001751/new lineage/data.f2fs.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
Then i installed a clean EMUI version and i did a backup without any issue but I get the same error when i try to restore this backup and it comes from the same file.
i tried many things like mounting/unmounting datas, format datas, multiple reboots, factory reset before restoring...
I can restore the backup without the datas but the ROM isn't working properly...
Either TWRP is corrupted and cannot extract these files or the backups made are corrupted.
I installed a fresh version of LineageOS but i would like to restore my old backup which was fully customized and btw understand where this issue come from.
Thanks a lot for any help/advice :fingers-crossed:

Help RESTORING backup, "extractTarFork() process ended with ERROR: 255"

NOTE THIS IS NOT "UNABLE TO BACK UP" THIS IS "UNABLE TO RESTORE"
Lots of people on this forum, and lots of people on the internet have errors trying to back up because of this dreaded error 255. But, for me, the backup was fine, but now I can't restore. This is a huge problem because I just tried out a custom ROM (which turned out to be a huge fail), and I want to go back to stock.
So I switched back to the other slot (A/B ftw), wiped all data, formatted SD card, set up the OS to have the same lock pattern as the backup, transferred the backup onto the phone and tried to restore, and, well, fuck.
Code:
[RESTORE STARTED]
Restore folder: '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR'
Skipping Digest check based on user setting.
Calculating restore details...
Restoring 4 partitions...
Total restore size is 11276MB
Restoring Vendor Image...
[Vendor Image done (3 seconds)]
Restoring Boot...
[Boot done (0 seconds)]
Wiping Data (excl. storage)
Wiping data without wiping /data/media ...
Done.
Restoring Data (excl. storage)...
extractTarFork() process ended with ERROR: 255
It failed, and there is absolutely nothing I can do about it. TWRP is using buggy commands to extract the backup and I don't know what's triggering the bug.
As a result, right now all my data is in limbo. TWRP cannot restore this backup as-is. I can't just go back in time and use `pm remove-user 999` or `pm remove-user 10` because the backup has already been created. Any solution that has to be done before the backup phase is inaccessible to me now.
My hope is that some smart person here can help me find a way to get this backup back onto the phone. Right now the internet does not have a solution to this problem, no matter how many naive users spam discussion boards with "pm remove-user 999 totally worked". Serious answers only.
Relevant section in the recovery log:
Code:
==> extracting: //data/vendor_de/10/ (mode 40771, directory)
Cannot find key for 10
error looking up proper e4crypt policy for '//data/vendor_de/10/' - 1DE10
tar_extract_file(): failed to extract //data/vendor_de/10/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win000'
Error during restore process.
I:Error extracting '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win000' in thread ID 0
I:Error extracting split archive.
Error during restore process.
pigz: write error code 32
pigz: abort: write error on <stdout>
extractTarFork() process ended with ERROR: 255
I suppose the solution is to make it "find a key for 10", but how? Do I just need to somehow recreate the 10 user before restoring the backup?

EDIT NOTICE: THIS DIDN'T WORK, DON'T MAKE IT WORSE BY TRYING
ORIGINAL POST IS BELOW
Alright. Well, I found a solution. That was quick.
The error is triggered by the backup containing a user that isn't present during the restore, I think. One solution is (theoretically) to create the missing user... another solution is to remove the missing user from the backup.
Turns out, backups are not so hard to modify, even in their compressed form. However, it is a little bit unintuitive at first.
You can't use the `tar` command to modify the backup, at all. TWRP's tar doesn't even support the --delete flag, nor does the BSD tar command (what ships with macOS). Even after installing GNU tar, it still refuses to work on a compressed archive (probably for the better).
You either need a Windows system with WinRAR/7zip (allows opening/modifying compressed files without extracting them), or a macOS/Linux system with FUSE and archivemount. If you're on Windows, you will have to manually search every single folder for 10 or 999 folders and delete every single one. If you're on macOS/Linux, the process is a bit more technical but also a bit more automated. And in both cases you will have to do this many times, and it can easily take half an hour or more and many restore attempts.
First and foremost, you need the recovery log to find out where the process failed. Every time it fails you will need to go to Advanced > Copy Log, copy them to the SD card, then use the flipping horrible Android File Transfer program to transfer the recovery.log to your PC, then use the cat/tail command or a text editor of your choice to read the log file.
Somewhere around the end of that file you will find something that looks like this:
Code:
==> extracting: //data/misc_de/10/ (mode 41771, directory)
Cannot find key for 10
error looking up proper e4crypt policy for '//data/misc_de/10/' - 1DE10
tar_extract_file(): failed to extract //data/misc_de/10/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/2020-11-08--22-06-46 PRE-RR/data.ext4.win003'
This contains all the info you need: the archive where the tar command gave up, and the file it gave up on.
Destroy that file with extreme prejudice.
Make a mount point with `mkdir mnt`, and mount the archive with `sudo archivemount data.ext4.win003 mnt`. (Of course, substitute data.ext4.win003 with the culprit archive file.)
If you're like me and have this problem with 10 folders, or 999 folders, you can find every single one of its kind with `sudo find mnt -name 10`. You can then use `sudo rm -rf` to delete every one of them. If you're brave, try `sudo find data -name 10 -exec sudo rm -rf \{\} \;`. I'm not responsible for any data losses incurred by using powerful commands that don't prompt you for confirmation.
Notice how I'm repeatedly using `sudo` for this: FUSE is kind of quirky and so is the kernel about multi-user filesystems. If you don't use sudo to mount the archive, then the user won't have permission to represent files it doesn't own, even if root is the one asking. You'll get weird "No such file or directory" errors for files and directories that are contained in parent directories' file listings. If you don't use sudo for the find or rm commands, you won't have permission to look inside folders or delete folders. Really, do everything with sudo because it's the only way to do this correctly.
Once you're done scrubbing the problem files away (be careful, do not use a file explorer of any kind, especially macOS's, which generally craps .DS_Store files all over your filesystem), unmount and save the archive with `sudo umount mnt`.
The next part is very important because recompressing files is not instant.
You will need to run `watch -n 1 du -hs data.ext4.win003` and WAIT.
Watch the file size slowly grow; only continue once it has stayed the exact same for at least one minute. Yes, it can definitely stop for 30 seconds at a time and then resume. You will need to give it time to recompress. It's also probably normal for the recompressed file to be about half the size of the initial file; that's just an artifact of TWRP not using very good compression to begin with. archivemount will create a backup of the archive with .orig appended, so you can try again if your backup ends up getting corrupted. (I just created an entirely separate copy of the backup to use archivemount on)
Of course, if you're on Windows you can skip all this and simply delete the problem file from WinRAR/7zip, and it'll be gone instantly and you can just proceed to copy the archive over to your device and retry the backup. You will have to do all the searching manually though, or perhaps you could try your luck with WSL. (Does WSL support FUSE?)
Expect this process to fail multiple times, but all at different points; whenever it fails at a different file, you know it got past the one you just removed. all you need to do is repeat this process over and over, slowly fixing your backup until it restores properly. This is what needs to be done if you can't reproduce the event that created that user in the first place. I'm sure if the user is important, it'll get created again.

Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/

LoganDark said:
Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/
Click to expand...
Click to collapse
Glad you managed to get your device back!
I had the same problem on another phone. The reason I got the error was because I tried to restore a decrypted backup on an encrypted device. After choosing the option "Format" in TWRP and typing 'yes' to confirm the decryption process, I was able to restore my backup.

Im having the same error in my realme xt...
sir..please help me.. I have a twrp backup of system image vendor image data boot recovery persist but im unable to recover because it shows an "error extract tar fork process ended up with error 255".during backup i had a pincode for screenlock.
i also have a backup of my internal storage in twrp but im not able to restore because of this error

LoganDark said:
Also, looks like user 10 is what happens when Google Play updates Device Personalization Services. Is this the generic "updates for system apps" user or is it specifically for that app?
EDIT: But updating that app doesn't create user 10. Interesting...
EDIT 2: User 10 is the guest user!! All I needed to do was create user 10 and that allowed me to restore my backup!
My post above is still good to see what I tried at first but it actually bricked my device until I factory reset it again, so :/
Click to expand...
Click to collapse
Hi. Did you create user 10 in Source, or in destination?
How did you do that in source?
If in destination, then is it possible to do it via TWRP?
EDIT: disregard. Mine user in the error path is 0 :-( '//data/system_de/0/'

just use option format data when entering wipe selection

erosman23 said:
just use option format data when entering wipe selection
Click to expand...
Click to collapse
doesnt work
redmi k20 davinci

Can't install/flash Update.zip with TWRP? (important!)

Hi, I would like to say in advance that I am grateful for any idea or solution.
Well, I wanted to install certain files, that is .apk files on my Samsung Galaxy S8, after which I created an Update.zip with a tool (Android Script Creator). Since my smartphone constantly stuck in an infinitely long bootloop, I have briefly reset my smartphone to sign the Update.zip with the app ZipSigner. After I reset everything so that I could install the signed Update.zip with TWRP, I got the error "Updater process ended with ERROR: 6 / Error installing zip file '/external/_sd/Update-signed.zip'". By the way, before that there was the note "no Digest file found", if that should be important.
If you have an idea what this could be and maybe a solution, then I look forward to your answer.
Many thanks in advance!
PS: If anyone knows how to replace .apk files and the associated data in the TWRP backup files, I would also be very happy about it.

AstroPepz said:
Hi, I would like to say in advance that I am grateful for any idea or solution.
Well, I wanted to install certain files, that is .apk files on my Samsung Galaxy S8, after which I created an Update.zip with a tool (Android Script Creator). Since my smartphone constantly stuck in an infinitely long bootloop, I have briefly reset my smartphone to sign the Update.zip with the app ZipSigner. After I reset everything so that I could install the signed Update.zip with TWRP, I got the error "Updater process ended with ERROR: 6 / Error installing zip file '/external/_sd/Update-signed.zip'". By the way, before that there was the note "no Digest file found", if that should be important.
If you have an idea what this could be and maybe a solution, then I look forward to your answer.
Many thanks in advance!
PS: If anyone knows how to replace .apk files and the associated data in the TWRP backup files, I would also be very happy about it.
Click to expand...
Click to collapse
Mount system. Go to advanced-file manager. There you can copy all the apps to their perticular location. Copy the files rom the updater zip. If the copying doesn't succeed then post the update.zip here

[QUESTION] Android 11 boot loop after restoring TWRP backup

Nandoid B/U with TWRP. Seems to backup just fine, but (immediately) restore on the same device causes boot loops.
It looks like the backup filed are something like win000, win001, etc that are actually tar files.
I'm wondering if I got into terminal mode on TWRP, could I just extract the tar files to restore the partition?? I've always used tar to b/u and restore /data/media.
FWIW, the device is a Pixel 3a running android 11 and the version 11 compatible TWRP flash file.
Help if you can...... Thanks

Hi @Boowho 1234,
seems you have accidentially posted in the wrong forum. I have moved your question to the Google Pixel 3a Questions & Answers forum.
regards
alecxs
moderator

alecxs said:
Hi @Boowho 1234,
seems you have accidentially posted in the wrong forum. I have moved your question to the Google Pixel 3a Questions & Answers forum.
regards
alecxs
moderator
Click to expand...
Click to collapse
sorry......

You're welcome! Regarding your question. May you clarify why you want to extract tar files manually - did the restoring via TWRP menu not extract the files successfully? Usually TWRP would throw an Error code in that case, and you can always have a look into /tmp/recovery.log

alecxs said:
You're welcome! Regarding your question. May you clarify why you want to extract tar files manually - did the restoring via TWRP menu not extract the files successfully? Usually TWRP would throw an Error code in that case, and you can always have a look into /tmp/recovery.log
Click to expand...
Click to collapse
Restoring using the TWRP restore option restored the files perfectly. But, upon rebooting back to SYSTEM just boot loops. No error code thrown, but I've not looked at recovery.log

It's probably because of one or more outdated files restored. try to delete this. you should also try to restore on formatted userdata partition (beware of / data/media = /sdcard is not included in backup)
/data/unencrypted
/data/misc/keystore
/data/misc/gatekeeper
/data/misc/vold
/data/system/locksettings.db*
You should ask TWRP maintainer to fix that issue.

I'm now using a Windows .bat file to backup ALL partitions on the device. It works great except throws errors on these two partitions : mmcblk0 and mmcblk0rpmb
I've read that these two partitions are not REALLY partitions at all, but are some sort of "special" files within the /dev/block directory.
The question is do I have a complete Nandroid back up without these two included?? Anyone??
Thanks