yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] Yoinx:
I've answered this numerous times... So I'm positive that a search would have yielded the answer....

You need to look at /tmp/recovery.log while in recovery (adb pull it). Look in it for the last file that it tried to read before it gave the error. Your options are either delete that file or pull it then delete it. However, the file is corrupt in some way and the backup will never finish.

Restoring an older nandroid fixes this because it deletes the existing files and writes your nandroid back over them.
[Nexus 6 Q&A, Help & Troubleshooting] MiuKing:
The search feature on xda is subpar at best. I've googled as much as I could before asking this question and I didn't get any solutions from that.
[Nexus 6 Q&A, Help & Troubleshooting] ComradeCase:
This happened to me a few months ago and I just had to bite the bullet and do a fresh install of my ROM without backing anything up.
[Nexus 6 Q&A, Help & Troubleshooting] gman88667733:
What do you mean by ADB pull it? How can I do this?
[Nexus 6 Q&A, Help & Troubleshooting] MiuKing:
Apparently, I'm still getting this issue... I don't know what is triggering this.

This is the recovery.log file i pulled from my tmp folder...

/system/addon.d ---- is this the issue? If so, twrp is looking for this file, how would I be able to fix this? delete that addon.d file?

I: Operation_start: 'Nandroid'

Updating partition details...

I: Data backup size is 5212MB, free: 23014MB.

I:Unable to mount '/usb-otg'

I:Actual block device: '', current file system: 'vfat'

...done

I:Backup Name is: '2016-02-09--13-32-48_MMB29T'

I:Full_Backup_Path is: '/data/media/0/TWRP/BACKUPS/ZX1G32284P/2016-02-09--13-32-48_MMB29T/'

I:Calculating backup details...

* Total number of partitions to back up: 9

* Total size of all data: 8174MB

* Available space: 23014MB

[BACKUP STARTED]

* Backup Folder: /data/media/0/TWRP/BACKUPS/ZX1G32284P/2016-02-09--13-32-48_MMB29T/

Backing up System...

E:Error opening '/system/addon.d' -- error: Not a directory

E:Error in Generate_TarList!

I:InfoManager saving '/data/media/0/TWRP/BACKUPS/ZX1G32284P/2016-02-09--13-32-48_MMB29T/system.info'

E:createTarFork() process ended with ERROR=255

Backup Failed.

Cleaning Backup Folder

I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/ZX1G32284P/2016-02-09--13-32-48_MMB29T/recovery.log

I:Set page: 'action_complete'

I: Operation_end - status=1

I:Set page: 'clear_vars'

I:Set page: 'main2'

I:Set page: 'advanced'
[Nexus 6 Q&A, Help & Troubleshooting] MiuKing:
bump
[Nexus 6 Q&A, Help & Troubleshooting] The_Fuzz22:
Hey man, I was able to resolve mine so should work for you:

- Ran a Titanium backup of all my apps and exported these to a PC to be safe.

- Performed a factory reset.

- Installed a fresh ROM.

- Restored my app backups. The wipe didn't reach them

- That's it. Standard wipe doesn't delete media so that's safe.

Whole process took about an hour. Good luck!
[Nexus 6 Q&A, Help & Troubleshooting] MiuKing:
Yeah I realized that it wasn't even worth it. Clean installed BenzoRom. Everything is fine now.
[Nexus 6 Q&A, Help & Troubleshooting] clamum:
Man, I've been having this issue for a long time (backups used to work in TWRP; they seemed to stop when I tried it once while enabling Compression).

Anyway, thanks to Yoinx, I did a "adb pull /tmp/recovery.log c:/recovery.log" command and it looks like I'm getting an error with the same file as MiuKing:

I hate to delete this file that I don't know anything about. I think I'm gonna try The_Fuzz22's solution of using TitaniumBackup for backing up all my apps and then just restoring an old backup of CM12.1 that I did when TWRP backup still worked.
[Nexus 6 Q&A, Help & Troubleshooting] Yoinx:
Addon.d is just a directory that contains backup scripts to backup things to carry forward after a rom install.

If TWRP is seeing it as a normal file instead of a directory, it's broken. Just delete it (if you can) and try you backup again. It won't hurt anything with that directory removed, and will just be recreated next time you flash a rom.
[Nexus 6 Q&A, Help & Troubleshooting] clamum:
Hmmm. Yeah **** it, I'll give that a shot. Thanks man.
[Nexus 6 Q&A, Help & Troubleshooting] clamum:
Huh. ES File Explorer says "Cannot delete addon.d" when I try to do it from within Cyanogenmod. Using the File Manager app, I can't even browse to the root device and get to the /system/ folder.

So I rebooted to Recovery and used that file manager; I found what I thought was the /system/ folder but there were no files in there. It's possible I didn't have the right location but I could not find anything else. At first I thought maybe the file was created when CM boots but that's not true, as far as I can see, because the file was created in Oct. of 2015.

Sick of this crap. Think I'm just gonna have to use my old backups and restore apps using Titanium Backup. The only bad thing is that ****ing "addon.d" file will be there and backups still won't work until I figure out how to delete it.
[Nexus 6 Q&A, Help & Troubleshooting] Yoinx:
Sounds like you didn't mount /system in recovery before trying to browse there in the file manager.
[Nexus 6 Q&A, Help & Troubleshooting] schasch:
thanks Yoinx!!!

I have the same issue on CM13-160729 LG G4...

needed to delete addon.d, then it backs up again. But if trying 2nd backup,

failure comes again, have to delete it again by adb in recovery.

2nd problem is that the keyboard is not working after recovery.

Funny thing is that this recovery was made after first clean-install of CM13160729 and TWRP 3.0.2.0.

...

is it a TWRP bug?

is it a VM13 160729-bug?

regards
[Nexus 6 Q&A, Help & Troubleshooting] delca85:
I have tried to solve createTarFork() 255 error in the way you suggested. This is the error I have retrieved from the file /tmp/recovery.log:

Do you have any idea about a solution?

Thanks a lot!
[Nexus 6 Q&A, Help & Troubleshooting] Yoinx:
I don't want to sound rude... But, yeah... Literally look at my post that you quoted and the bit from the log you posted... Then do the thing that I say to in the past you quoted. second paragraph (for lack of a better term).
[Nexus 6 Q&A, Help & Troubleshooting] Hatman41:
Same Issue

I am having the same issue. I deleted the addon.d and then try to backup the ROM again and it gives me the same error. The addon.d is back. I then delete it again and try and the addon.d is back again. No clue why it keeps getting added.

[BACKUP STARTED]

* Backup Folder: /data/media/0/TWRP/BACKUPS/ZY2233DBZ8/Pure.2016-10-18/

Backing up System...

Error opening: '/system/addon.d' (Not a directory)

I:Error in Generate_TarList!

Error creating backup.

I:InfoManager saving '/data/media/0/TWRP/BACKUPS/ZY2233DBZ8/Pure.2016-10-18/system.info'

createTarFork() process ended with ERROR: 255

Backup Failed. Cleaning Backup Folder.
[Nexus 6 Q&A, Help & Troubleshooting] brisinger08:
I had this same issue on my nexus 6P...what ended up working for me was disabling compression. I *think* TWRP/tar is having issues creating the tar with odd directories. Maybe try disabling compression and give it another shot :)
[Nexus 6 Q&A, Help & Troubleshooting] ins5736:
+1 for disabling compression
[Nexus 6 Q&A, Help & Troubleshooting] darkruby:
I'm getting createTarFor() issue when backing up ROM

having inspected recovery.log I found out that file /data/anr/traces.txt is causing an issue

I:Error adding file '/data/anr/traces.txt' to '/external_sd/TWRP/BACKUPS/TA39101OD8/2016- 11-01--14-00-22_aicp_clark-userdebug_7.1_NDE63P_d0b52ef5ed//data.f2fs.win002'

I tried to adb shell and delete the file

but I get I/O error when doing anything with this file,

Any suggestions?
[Nexus 6 Q&A, Help & Troubleshooting] yugotprblms:
For anyone else that had this issue, at least with the addon.b causing the error,I seem to have overcome it. Bear in mind though, I am on a Oneplus 3, with a CM13 ROM. I assume it should be fairly similar though.

I was getting the error with the stupid addon.b file/folder. If I deleted it while in android, it would come back on reboot. I could not delete it through TWRP, as it seemed to not know how to handle it. So, in android, I renamed it to addon.test.b, rebooted to TWRP, where it recognized it as a file instead of a folder, and I could delete it. The back up then went fine, as it had not rebooted and created another one.

Then, out of curiosity, I booted into android. The addon.test.b was created again. So I rebooted into recovery, restored the backup I just barely made, and booted into android. No addon.test.b or addon.b. Rebooted again. Still, neither showed up. So I will count this as a success.

Here are the steps I took. Test at your own risk. I made a Titanium Backup of everything just in case, prior to all this.

Use a file explorer to rename "addon.b" to "addon.test.b" while in android

Reboot to TWRP

Make sure System is mounted in TWRP

Delete "addon.test.b" in the TWRP file manager

DO NOT REBOOT YET

Make a full nandroid

If/when that succeeds, boot into android, see if file is there.

If it is, restore backup you just created.

Boot into android.

If file is not there, reboot a few times to check.

I think it works fairly similarly to this, just without having to restore an older backup.
[Nexus 6 Q&A, Help & Troubleshooting] :
Not everyone's backup fails on the same file. Good info, but it's not universal... If you look at my other replies in this thread, you'll see where I direct people to look at their recovery.log files to get the name of the errant file.

Also, it sounds like you had a startup script creating that file on boot?
[Nexus 6 Q&A, Help & Troubleshooting] yugotprblms:
That's why I bolded the part about it being for the addon.b, or .d, whatever.

As far as I know I had no script creating it. I do not know what would be doing it. It's especially odd, because after I renamed it to addon.test.b, then deleted it, it would come back as that name after boot. Addon.test.b.
[Nexus 6 Q&A, Help & Troubleshooting] duhsquid:
twrp backup error 255

:D Thanks for mentioning this here on the BEST SITE!. I have made a good nandroid backup after five attempts.

Thanks again,
[Nexus 6 Q&A, Help & Troubleshooting] brisinger08:
Mine was failing on a random file in /data/data...i uninstalled the app that was saving the file causing the error (pocket) and cleaned out the app data. After that I booted back to TWRP to try another backup and according it failed on a different file (also in /data/data). Since the issue seems to go away if you disable compression I think there is a bug in the tar binary that TWRP is using but I'm not a dev so that's just a guess :)

Some custom roms add that (or other) folders at boot. That's definitely weird tho that it would come back named incorrectly...might want to check with the ROM dev on that :eek:

Glad it worked for you :good:

Cheers
[Nexus 6 Q&A, Help & Troubleshooting] IparryU:
For those who have the addon.d issue, go to terminal in TWRP

cd /system
rm addon.d

Backup works.
[Nexus 6 Q&A, Help & Troubleshooting] Bontropi:
I really thank you for this. [emoji1]

Tried so many times to solve it, I had headache all week long.

This method really worked and solved my strange issue in just a second.

Thank you so much, my friend.

Inviato dal mio Pixel XL utilizzando Tapatalk
[Nexus 6 Q&A, Help & Troubleshooting] srk05:
When will the TWRP folks fix this? By chance I had not enabled compression, and the backup worked. Enabled it, then the backup failed.
[Nexus 6 Q&A, Help & Troubleshooting] injuhneer:
I too am experiencing this particular variety of Android Ownership Joy.

Mine is failing on what appears to be a file in /system/app named AndroidPay.

Trying to delete the file causes reboot. Tried remount to r/w in TWRP terminal, adb, root browser, ESFileExplorer, ROM Toolbox. No joy.

HTC A9, Marshmallow, S-OFF, SuperSU, TWRP.
[Nexus 6 Q&A, Help & Troubleshooting] CZ Eddie:
Thanks. This was the first thing that came up in my Google search. :good:

Added this to my post in TWRP for my device:
[Nexus 6 Q&A, Help & Troubleshooting] pastorbob62:
It seems that you are all making this a lot harder than it needs to be. I ran into this on my Moto G4 and all I did was dirty flash my lastest ROM and OpenGapps. Rebooted into system to be sure it was all kosher, then I rebooted into recovery and WALLA!! I was able to do a new backup without any problem at all.
[Nexus 6 Q&A, Help & Troubleshooting] Disgustip8ed:
Gotta agree here. I just dirty flashed an updated ROM to the latest RR, did a Titanium Backup and now a full TWRP backup and all is well.
[Nexus 6 Q&A, Help & Troubleshooting] C114:
That worked for me. The addon.d file is not there anymore.

Xiaomi Redmi Note 3 Kenzo

Resurrection remix Official Nightlies 7.1.1 2017/04/14 build TWRP 3.1.0-0
[Nexus 6 Q&A, Help & Troubleshooting] Aniket.t20:
/data/misc/profiles/cur/0/foreign-dex/@system@app@Chrome@Chrome.apk

Is the file causing trouble for me on my OnePlus 3T.

Couldnt delete it through twrp and ADB shell and file manager+root. Any other way to remove this??
[Nexus 6 Q&A, Help & Troubleshooting] C114:
Maybe try to rename and then delete.
[Nexus 6 Q&A, Help & Troubleshooting] dikosty:
Hi everyone. I have a strange bug on my sony xperia z1 compact, 5.1.1.

TWRP 2.8.7 doesn't create a backup of data. I tried to create a general backup and separately for the data. It creates a backup of system, but not data. Indicates that TWRP recorded about 30%, then device turns off and reboots to system. And I have "0kb" of file of data.

I changed USB flash drive, OTG cable, tried to recorde to SD card phone.

Everything was fine 2 months ago.

I don't know how to find the problem.

There is no way to record a log of bugs?﻿

Now I tried to turn on "Enable compression" and

"Skip MD5 generation during backup" and I got error=255

UPD: Sorry, I did not see that tread is for Nexus 6

UPD 2: Restoring default settings in TWRP helped me.
[Nexus 6 Q&A, Help & Troubleshooting] Edozullo:
Hey, i've this problem: When starting a Backup it crash immediantly after Backup system the process createTarFork() is crash with errore 255. Help me
[Nexus 6 Q&A, Help & Troubleshooting] ktmom:
Did you read this post from earlier in the thread?
[Nexus 6 Q&A, Help & Troubleshooting] Jituv1996:
Thankyou! This worked for me :):good:
[Nexus 6 Q&A, Help & Troubleshooting] wmir10:
I was experiencing this same error last night. Right before it completed backing the data partition. I was wondering what could could be causing this error and I didn't feel conferrable deleting any file in /data or /system, being very late at night and I was very tired. From past experience, I learned the hard way not to tinker around in that state of mind as I can make the stupidest mistakes when I'm sleepy. But thanks to you and this forum, I decided to do a backup, this time without compression. It was kind of late and I was to eager to get this done because my last backup was almost 3 weeks old. I made an openrecoveryscript file in /cache/recovery with ES File explorer, took the O out (to disable compression), rebooted into recovery, went straight to sleep, and WALLA! Woke up this morning and found a fresh backup in my SD card. Thank You So Much for that idea! You guy are Awesome!

Though, It was taking over 8GB of space but I much rather deal with less storage then a possible bricked phone. I just wanted to thanks. You all are lifesavers. This site save my butt (and my phone) more often than I can count.
[Nexus 6 Q&A, Help & Troubleshooting] droidzer1:
In my case a file named AnglerLayout was in the /system/app folder where there are nothing but folders. It was the only file. I'm guessing it got put there by Substratum and/or the Navbar enabler as that is the only two things installed since the last successful TWRP backup. I moved the file (and made sure it was deleted from /system/app and then immediately booted into TWRP and did a successful backup. The file AnglerLayout seems to get recreated upon reboot so I didn't even need to move it back.
[Nexus 6 Q&A, Help & Troubleshooting] Char_G:
No problem with backups on my shamu with TWRP 3.1.1-0
[Nexus 6 Q&A, Help & Troubleshooting] Git226:
I got the same error and was eventually able to get the backup to work. I first deleted any apps that I had installed after my last successful Nandroid Backup, and then used SDMaid's SystemCleaner and AppCleaner tools. Hope this helps.
[Nexus 6 Q&A, Help & Troubleshooting] rocketrazr1999:
Yoinx reply perfect

Lol, doesn't everyone look at the logfile first before posting a request for assistance? FYI, try disabling MTP if backing up to a thumb drive, twas my easy fix numerous times. And TY Yoinx
[Nexus 6 Q&A, Help & Troubleshooting] Flasher8:
thanks, this method worked for me. ! :D
[Nexus 6 Q&A, Help & Troubleshooting] Drod101:
during TWRP backup process I get error 225 my phone errors on /data/misc/bluedroid/T

entire entry from the recovery.log file

Error adding file '/data/misc/bluedroid/T,unIAEkzPDTb6OZmBDRvD'

I couldn't do adb pull so i exported the file to a notepad and went through it until i found the error

I tried to remove it but got access denied

C:\Users\drpch\Downloads\adb-fastboot-tool-2016>adb shell

HWMHA:/ $ rm /data/misc/bluedroid/T

rm: /data/misc/bluedroid/T: Permission denied

based on my google search this file is part of Bluetooth, any advice on what I should do?

I would appreciate the help I want to do a system back up of the phone before I try to re brand it as i'm trying to change ROM version from Chinese to international on my Mate 9 and just in case anything goes wrong I want to be able to go back quickly restore.
[Nexus 6 Q&A, Help & Troubleshooting] drieg:
Hi

facing the same issue, with this error:

I:Failed to load image from indeterminate013

no compression..anyone knows why is this happening\what to do? I do not wish to flash another rom.

Thanks in advance!
[Nexus 6 Q&A, Help & Troubleshooting] Sirguda:
It tells me that "No such file or directory", this is weird, whereas I can see it in Solid Explorer (but not in TWRP file manager).
[Nexus 6 Q&A, Help & Troubleshooting] C114:
Can you give more details?
[Nexus 6 Q&A, Help & Troubleshooting] Sirguda:
In TWRP Terminal, I do cd /system, which gives no error. Then the command shown above, rm addon.d, and it then tells "No such file or directory". But when I explore system folder in Solid explorer, there is a addon.d file, that I can't delete with Solid Explorer (-rw-r-r- permissions).
[Nexus 6 Q&A, Help & Troubleshooting] :
I was getting error 255s, so I deleted my previous backup. Now I can't go back... :(
[Nexus 6 Q&A, Help & Troubleshooting] leodelacruz:
I found solution by my self. From pc i remove the folder called backups inside twrp folder. And i remove .twrps file too. Next i dirty flashed new version of aicp rom (Witch im using) and wipe dalvik cache and cache. Again on main twrp screen go to backup and now you can see. Works :)
[Nexus 6 Q&A, Help & Troubleshooting] s3korn:
Had the 255 error during a backup, used Google and found this thread.

Copied the log to SD card an found the corrupted folder in system/app.

Can't open the folder by twrp file manager to delete, but finally deleted with this twrp terminal comand > cd /system/app > rm xyz.bad.folder

Thank you for this hint, so works with any other folders too. Just read copied logfile ;o)

--

sent from mobile device
[Nexus 6 Q&A, Help & Troubleshooting] JeffXT:
This worked on my Nexus 6p, 7.1.2 (N2G48C, Aug 2017)!! If you can't adb pull, just copy the log file to your internal storage. Be patient - the file can be huge and take a while to open in Notepad. Once you find out what file is causing the issue, try deleting or, if it's a system app like mine, do this:

Solution: Restore ONLY system partition from an older nandroid backup, reboot to recovery again, backup.
[Nexus 6 Q&A, Help & Troubleshooting] CarlosRDonXDA:
Solution... (I think)

Hello friends, I think I have found a solution to this problem ...

After having read almost all POSTS in this TREAD, I could understand the reason for this error. TWRP tries to read only folders in "/ system / app" and if TWRP finds any file that is outside the application folders, that's when the error comes.

Particularly we (you) talked about the file "addon.d", but in my case it was the file "PacProcessor". I did create a folder with the first name that occurred to me and move to that folder all the files (not folders) that were on "/ system / app", restart in recovery mode, select the backup option and ... what do you think happened? ?? Backup without problems.

I must say that I did this procedure on my HTC-10 pme, S-OFF, with TWRP 3.1.1.0

Do you want to try???

Regards…
[Nexus 6 Q&A, Help & Troubleshooting] Zoltair Wright:
I had the same issue. after the backup failed I ran from terminal:

adb shell cat /tmp/recovery.log | tail -20

the interesting part:

I:addFile '/data/system_ce/11' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/11' - 'af54a20024c9ea92'
I:Error adding file '/data/system_ce/11' to '/data/media/0/TWRP/BACKUPS/731a173a/2017-11-12--12-56-52/data.ext4.win004'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.

'/data/system_ce/11' is the directory created for my work profile using Island. so if you have a work profile, you may have to change permissions/delete it in order for you Nandroid to complete

EDIT: or maybe it was for the other user on my phone? anyway there was more than one /foo/bar/11 folder that needed to be deleted, I got a different '11' directory error which caused another error after I deleted the first one
[Nexus 6 Q&A, Help & Troubleshooting] abalam:
Just dirty flash the ROM, reboot the device, reboot to twrp again. Now you can backup again.
[Nexus 6 Q&A, Help & Troubleshooting] Madman.01:
boot into your twrp recovery go to mount and disable data. this will solve. ;)
[Nexus 6 Q&A, Help & Troubleshooting] fontomas:
I have an error during backup, here's the recovery.log content

I:Backup Name is: '2018-01-03--12-02-08'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08'
I:Calculating backup details...
* Total number of partitions to back up: 5
* Total size of all data: 12759MB
* Available space: 97309MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08
Backing up Boot...
I:Reading '/dev/block/sde19', writing '/data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/boot.emmc
I:Restored default metadata for /data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/boot.emmc.win
* Generating digest...
I:SHA2 Digest: e87cb0358f437689e295df369ada19ed4b40b592e5a65ddff0e73361b460f2e2 boot.emmc.win
I:digest_filename: /data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/boot.emmc.win.sha2
* Digest Created.
I:Partition Backup time: 1
Backing up Recovery...
I:Reading '/dev/block/sde22', writing '/data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/recovery.
I:Restored default metadata for /data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/recovery.emmc.wi
* Generating digest...
I:SHA2 Digest: b8bbc0e66d88769fafd3667c26706e433f43c0b84996bdfa9d955f2c3e009c49 recovery.emmc.win
I:digest_filename: /data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/recovery.emmc.win.sha2
* Digest Created.
I:Partition Backup time: 0
Invalid encryption mode 'ice:aes-256-cts'
Backing up System...
Invalid encryption mode 'ice:aes-256-cts'
Error opening: '/system/app/DeskClock/oat/arm64' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/da29c9c8/2018-01-03--12-02-08/recovery.log
I:Set page: 'action_complete'
I:operation_end - status=1
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'terminalcommand'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set overlay: 'slideout'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0

Any help guys?