Ошибка 255 twrp при бэкапе data

asked Sep 26, 2017 at 15:30

For me, the error was related to the I/O or file corruption issue.

To find what has happened, browse to the backup location (usually /external_sd/TWRP/BACKUPS/backupfolder) and find the recovery.log file. Open the file, and at the bottom lines, read what folder caused backup failed.

Delete the corrupted folders using TWRP File Manager, delete the old backup folder, and try to do a backup again. Consider that this may occur for different folders, so you need to read the log file every time.

Tom HaleTom Hale

4072 gold badges5 silver badges16 bronze badges

I think I found the solution!

1. In TWRP, go to «Wipe» and swipe to factory reset
2. Download:
   • OnePlus Recovery: oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
   • OxygenOS: oxygenos.oneplus.net.s3.amazonaws.com/OnePlus5Oxygen_23_OTA_015_all_1708252353_e6d7756780064352.zip

3. Rename the recovery image as recovery.img, boot phone into fastboot, plug into the computer, run these commands on the computer:

   fastboot devices
   fastboot flash recovery recovery.img
   fastboot boot recovery.img
   

4. Open recovery on the phone

5. Select «Forgot Password», this will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select «Install over ADB» or «Install Over USB» or something similar and plug the phone into the computer.
7. Run adb sideload oxygen-os-filename on the computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probably isn’t, so don’t shut it off or unplug USB.
9. Download Bluspark TWRP

10. Reboot into fastboot, plug into the computer and run these commands on the computer:

    fastboot devices
    fastboot flash recovery bluspark-twrp-filename-location.img
    fastboot boot bluspark-twrp-filename-location.img
    

11. Success (hopefully)

TWRP has some compatible problems with OnePlus 5. I have the same error using TWRP 3.1.1-1 with LineageOS 7.1 nightly build, but I finally work out with this:

1. Reboot into recovery, TWRP
2. Go to the terminal in «Advanced»
3. Type cd /system to change the path to the system folder
4. Type rm addon.d to remove the addon file
5. Type exit to quit from the terminal

Now back to TWRP home, try backup/restore again, it should works.

Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won’t mess up the filesystem.

asked Sep 26, 2017 at 15:30

For me, the error was related to the I/O or file corruption issue.

To find what has happened, browse to the backup location (usually /external_sd/TWRP/BACKUPS/backupfolder) and find the recovery.log file. Open the file, and at the bottom lines, read what folder caused backup failed.

Delete the corrupted folders using TWRP File Manager, delete the old backup folder, and try to do a backup again. Consider that this may occur for different folders, so you need to read the log file every time.

Tom HaleTom Hale

4072 gold badges5 silver badges16 bronze badges

I think I found the solution!

1. In TWRP, go to «Wipe» and swipe to factory reset
2. Download:
   • OnePlus Recovery: oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
   • OxygenOS: oxygenos.oneplus.net.s3.amazonaws.com/OnePlus5Oxygen_23_OTA_015_all_1708252353_e6d7756780064352.zip

3. Rename the recovery image as recovery.img, boot phone into fastboot, plug into the computer, run these commands on the computer:

   fastboot devices
   fastboot flash recovery recovery.img
   fastboot boot recovery.img
   

4. Open recovery on the phone
5. Select «Forgot Password», this will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select «Install over ADB» or «Install Over USB» or something similar and plug the phone into the computer.
7. Run adb sideload oxygen-os-filename on the computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probably isn’t, so don’t shut it off or unplug USB.
9. Download Bluspark TWRP

10. Reboot into fastboot, plug into the computer and run these commands on the computer:

    fastboot devices
    fastboot flash recovery bluspark-twrp-filename-location.img
    fastboot boot bluspark-twrp-filename-location.img
    

11. Success (hopefully)

TWRP has some compatible problems with OnePlus 5. I have the same error using TWRP 3.1.1-1 with LineageOS 7.1 nightly build, but I finally work out with this:

1. Reboot into recovery, TWRP
2. Go to the terminal in «Advanced»
3. Type cd /system to change the path to the system folder
4. Type rm addon.d to remove the addon file
5. Type exit to quit from the terminal

Now back to TWRP home, try backup/restore again, it should works.

Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won’t mess up the filesystem.

This issue is also present when no encryption is used.

I’m using official twrp 3.2.3-1 and can reproduce the error with several builds of Liquid Remix and Lineageos after a fresh install with the following procedure:

• factory wipe
• install rom & twrp
• reboot system
• add user (whether or not the new user is configured does not make a difference)
• reboot recovery
• try to backup

Rebooting into system and removing the added user lets backups from within twrp be created normally.

I experience the same problem with my device (Chiron) using both the latest and previous TWRP versions.
When I decrypt the device in TWRP there are still some encrypted folders:

• /data/user/10
• /data/misc_ce/10
• /data/system_ce/10
  These folders belong to a second user profile (in my case created by the app cloner ‘Island’)

Besides deleting the second user with pm remove-user [user_id], is there any other workaround for this issue? This affects any phone/ROM that uses android’s FBE when creating a new profile (pretty much all of them), and has been ongoing for quite some time (almost an year that I remember).

Is it too hard to just skip all the other profile’s directories (or everything that’s file-based encrypted for that matter) when using TWRP to backup and restore?

this happens on harpia as well, with old and most recent twrp, with no additional users.

looking at the recovery.log revealed this error message:
Error opening: ‘/system/addon.d’ (Not a directory)

so i fixed this issue by simply creating that directory:

1. boot into recovery twrp
2. go to advanced > terminal
3. in terminal, type:
   cd /system
   rm addon.d
   exit
4. go back to the main menu and try backup again. it should work.

So what is actually the issue that’s holding back TWRP from supporting multiple user profiles?

Time. Time for the TWRP devs to review the relevant patch on Gerrit. Be patient.

The problem still exists in Android 10 with multiple users.

I have FBE and only a single user.

I had this error (ERROR: 255) when trying to restore the data partition from a TWRP backup. After trying it several times, the data partition got corrupted: TWRP couldn’t decrypt it anymore.

This meant that the internal storage was gone and the backup was gone because TWRP stores it on the internal storage. Therefore it’s important to manually backup the internal storage beforehand. This can be done via adb pull /sdcard my-sdcard-backup (where my-sdcard-backup is a folder that doesn’t exist yet) and must be done before such a bug happens.

I had such a backup of my internal storage and was finally able to restore the TWRP backup (without ERROR: 255) like so:

• Boot into TWRP.
• Format the data partition (which was corrupted anyways).
• Reboot into system and set up the device.
• Reboot into TWRP.
• adb shell rm -rf /sdcard/*
• adb push my-sdcard-backup/* /sdcard/
• Restore the TWRP backup.

During the last step, the backup was restored without error.

same here: i have twrp 3.3.1-2 & 3.3.1-14 with los/microg tested.
shelter is installed for the second profile.

would be great if this could work!

failed to lookup tar policy for '/data/vendor_ce/10' - '7856242092fbe42a' I:Error adding file '/data/vendor_ce/10' to '/data/media/0/TWRP/BACKUPS/7b55eca1/2019-12-14--07-30-01_lineage_enchilada-userdebug_9_PQ3A190801002/data.ext4.win000' Error creating backup. I:ERROR tarList for thread ID 0 Error creating backup. I:InfoManager saving '/data/media/0/TWRP/BACKUPS/7b55eca1/2019-12-14--07-30-01_lineage_enchilada-userdebug_9_PQ3A190801002/data.info' createTarFork() process ended with ERROR: 255failed to lookup tar policy for '/data/vendor_ce/10' - '7856242092fbe42a' I:Error adding file '/data/vendor_ce/10' to '/data/media/0/TWRP/BACKUPS/7b55eca1/2019-12-14--07-30-01_lineage_enchilada-userdebug_9_PQ3A190801002/data.ext4.win000' Error creating backup. I:ERROR tarList for thread ID 0 Error creating backup. I:InfoManager saving '/data/media/0/TWRP/BACKUPS/7b55eca1/2019-12-14--07-30-01_lineage_enchilada-userdebug_9_PQ3A190801002/data.info' createTarFork() process ended with ERROR: 255

Well, if you’re fine with the data being removed for your dual apps, please try flashing this before trying a backup and/or a restore: RMDAD_v0.0.1.zip

That will remove any 999/10 folders, flashable in TWRP. Please report back.

It is happening also with a single user (only ID 0 user), using TWRP 3.3.1.2 in a Motorola G7, Android 9, trying to do a backup (through USB OTG). External SD is formatted as internal space.

Well, if you’re fine with the data being removed for your dual apps, please try flashing this before trying a backup and/or a restore: RMDAD_v0.0.1.zip

That will remove any 999/10 folders, flashable in TWRP. Please report back.

Removed all work profiles and parallel apps in the OS, but that didn’t work. Flashing the zip worked for me, this is the solution to the thread.

RMDAD_v0.0.1.zip . . . That will remove any 999/10 folders, flashable in TWRP.

This worked for me as well.

I looked at several of those folders and they were all empty. So I assumed they were all empty (and figured the worst that would happen if they weren’t, is all the apps in the dual account, whatever that was, would have their data cleared/reset).

Thanks.

Well, if you’re fine with the data being removed for your dual apps, please try flashing this before trying a backup and/or a restore: RMDAD_v0.0.1.zip

That will remove any 999/10 folders, flashable in TWRP. Please report back.

Did not work for me. Removing users is not the solution for my 255 error because I only have one user (pm list users).

I don’t see why removing users would work. This also happened to me with a single user.
As I posted above:

this happens on harpia as well, with old and most recent twrp, with no additional users.

looking at the recovery.log revealed this error message:
Error opening: ‘/system/addon.d’ (Not a directory)

so i fixed this issue by simply creating that directory:

boot into recovery twrp
go to advanced > terminal
in terminal, type:
cd /system
rm addon.d
exit
go back to the main menu and try backup again. it should work.

@btarazona rm addon.d is not exactly «creating a directory».

In my case, it also happens with no additional users.

It is happening also with a single user (only ID 0 user), using TWRP 3.3.1.2 in a Motorola G7, Android 9, trying to do a backup (through USB OTG). External SD is formatted as internal space.

I think the issue is related to the encryption of the SD: TWRP seems unable to decrypt it; although it says the is it successfully decrypted once I put the correct pattern. Thinking that the problem could be the length of the pattern, I have simplified it to four points, but again, with no success.
My suspicion with the encription comes because the last error I see in the log is:

failed to lookup tar policy for ‘/external_sd/user/0’ — ‘fca0edbb67a976a3’
I:Error adding file ‘/external_sd/user/0’ to ‘/usb_otg/TWRP/BACKUPS/……/2020-01-03—12-47-13/external_sd.f2fs.win000’

That directory exists, but having a look at /sdcard, I notice that data is encripted.

An browsing through the SD, it seems directories and files are encripted.

So, is TWRP unencripting the external SD correctly? I am using the right pattern when asked by TWRP (obviously, I am pretty sure of that, because I am using it continuously), and so TWRP says confirming unencription.

Well, if you’re fine with the data being removed for your dual apps, please try flashing this before trying a backup and/or a restore: RMDAD_v0.0.1.zip

That will remove any 999/10 folders, flashable in TWRP. Please report back.

Thanks a lot! This worked for me. (fajita)

Please stop cluttering the thread by discussing «solutions» that involve removing additional users, profiles, dual apps and/or their data. Issue #1373 specifically concerns multi-user setups.
Thank you.

Not sure if this will work for other people. I noticed that I was getting this error (createTarFork() process ended with ERROR: 255) while creating the backup right after the screen locked. I disabled the screen locking in settings and then my backup completed.

NOTE: I have an encrypted device with work profile using shelter.

Happens for me with Xiaomi MI6 sagit TWRP 3.3.1-2, same error after message
«Backups of data do not include any files in internal storage such as pictures or downloads.» in case that’s relevant

Enabling backup encryption worked, yet I belive it’s using different compression method.

Not sure if this will work for other people. I noticed that I was getting this error (createTarFork() process ended with ERROR: 255) while creating the backup right after the screen locked. I disabled the screen locking in settings and then my backup completed.

NOTE: I have an encrypted device with work profile using shelter.

worked on huawei mate 8 twrp 3.0.1 /no errors after your solution /thank you

Well, if you’re fine with the data being removed for your dual apps, please try flashing this before trying a backup and/or a restore: RMDAD_v0.0.1.zip

That will remove any 999/10 folders, flashable in TWRP. Please report back.

I used this one on my OnePlus 6 after having the 255 error while trying to back up in TWRP. This occured probably, because I once used the parallel apps option but reverded that.
Then I could back up, but had a recovery boot loop afterwards. I used the option of twrp to repair this recovery boot loop problem and could boot into the system again.
Going back into TWRP I had the 255 error again and also it seems that I can’t flash magisk. Tried twice — didn’t stick.

Any help is appreciated. I need a back up of my phone.

I had success by using the terminal:

SU
PM remove-user 999

People, I kindly ask you all to stop suggesting removing other user’s data. This issue is specifically to address multi-user backup not working. Removing a user has been mentioned multiple times already and is not a real solution. Please respect all the people that follow this issue. The people who follow it, do it to know when it’s FIXED.

Nothing from above has actually helped to solve the issue. I have a Mi 9 Pro 5G.
The issues seems to occur when TWRP tries to access and copy the /data/app folder. Immediately it does, error 255 pops-up.

Any suggestions how to solve it all would be greatly appreciated.

I had the same exact error message but finally resolved it when I enabled backup encryption just like @Misiur mentioned. Thanks.

Solved by removing Work Profile (Shelter).

Solved by removing Work Profile (Shelter).

Please explain how the issue at hand is solved by deleting the work profile??

Solved by removing Work Profile (Shelter).

Please explain how the issue at hand is solved by deleting the work profile??

I have no idea why, but i got this advice from OnePlus community.

@linjan

Removing the work profile (or multiple users, etc.) does not solve this issue. The issue explicitly concerns use cases with (!!!) multiple users, work profiles, etc.

It’s like moving a car that won’t start at cold temperatures into a heated garage and claiming that the problem (of the car not starting in the cold) is solved.

@linjan

It’s like moving a car that won’t start at cold temperatures into a heated garage and claiming that the problem (of the car not starting in the cold) is solved.

Yes, but from reading at [https://gerrit.twrp.me/c/android_bootable_recovery/+/1724] it is not clear to me if this patch is working and when it will be released.

Every reasonable modding instruction starts with the advise to make backups before preceding.

Right not I am having a brand-new phone that I cannot setup any further, because i cannot make a backup of my existing configuration.

So I am actually thinking of moving my car to the garage for heating up and equally removing my shelter/work profile. So that i can continue.

It got another phone i did not even start, because i will not be able to backup … Before installing Magisk, before installing XPosed etc.

Not using my phone is not a solution. I will rather discard any additional profiles I made.

I looked at the TWRP source code but i do not know enough to figure out how to blacklist or exclude directories from backup.

And by the way, TWRP maintainer mauronofrio officially tells you there to go to a thread which tells you to delete your work profiles!

@ is-this-a-comma-or-period

This is all very fine and mostly agreeable. However, what people do not seem to realize is that this place is for reporting bugs and discussing actual solutions to them. It is NOT a user forum where workarounds can (and should) be discussed.

Put it in terms of the car:
What is the use of (btw. repeatedly!) reading about how to start the engine in a warm garage when you are the engineer tasked with solving the issue (so that cars can continue to be sold to buyers without heated garages who still have to be able to depend on them starting in the cold)?

Had same issue today trying to backup Data, I have a Xiaomi Mi 9T Pro, making use of the Second Space feature, which creates a user with number 10.

Fix for this has been merged and will be included in the next official TWRP release.

Fix for this has been merged and will be included in the next official TWRP release.

Hello,
When is planned the next release ?
Thanks

Fix for this has been merged and will be included in the next official TWRP release.

Hello,
When is planned the next release ?
Thanks

Soon™

@CaptainThrowback Hello, just to be sure — the new 3.4.0-0 release from June 24 has fixed this issue, correct? When I make a backup with work profiles using this version, there will be no problem restoring them?
If that’s the case, maybe this issue can be marked as fixed.

@CaptainThrowback Hello, just to be sure — the new 3.4.0-0 release from June 24 has fixed this issue, correct? When I make a backup with work profiles using this version, there will be no problem restoring them?
If that’s the case, maybe this issue can be marked as fixed.

TWRP 3.4.0 is able to decrypt secondary user accounts (including work profiles), yes. However, that is dependent on knowing what the password is for such profiles, and we’ve seen a few cases where those profiles were created by a specific application and won’t decrypt automatically. The option to decrypt additional users is under Advanced -> Decrypt Users, but if the password for the work profile is unknown, it will still be unable to properly backup and restore.

This latter case is still being worked on. The idea would be to skip backing up any profiles that aren’t decrypted, but first providing a notification to the user that there is a user account that is still encrypted and will be skipped unless the user chooses to decrypt it at that time. This will prevent the issues with restoring since the work profile will remain unaffected. I believe @noahajac and @chaosmaster were looking into this.

So for now, this issue can remain open until it’s completely fixed.

EDIT: Same applies to this issue, where this is a bit more information: #1256

@CaptainThrowback

TWRP 3.4.0 is able to decrypt secondary user accounts (including work profiles), yes. However, that is dependent on knowing what the password is for such profiles, and we’ve seen a few cases where those profiles were created by a specific application and won’t decrypt automatically. The option to decrypt additional users is under Advanced -> Decrypt Users, but if the password for the work profile is unknown, it will still be unable to properly backup and restore.

Thank you. Does anyone know if the Shelter app is known to put passwords or cause other issues when decrypting?

@CaptainThrowback

TWRP 3.4.0 is able to decrypt secondary user accounts (including work profiles), yes. However, that is dependent on knowing what the password is for such profiles, and we’ve seen a few cases where those profiles were created by a specific application and won’t decrypt automatically. The option to decrypt additional users is under Advanced -> Decrypt Users, but if the password for the work profile is unknown, it will still be unable to properly backup and restore.

Thank you. Does anyone know if the Shelter app is known to put passwords or cause other issues when decrypting?

I have no idea about any of those apps. You’d have to boot up TWRP and see if it decrypts the secondary user automatically or not.

I’ve just tried to restore a backup that was created using TWRP 3.4.0-0 which contained a work profile and a «dual app» profile (Xiaomi). The «dual app» profile gets properly decrypted, the work profile gets ignored when backing up.

However when restoring the backup I’m getting a 255 error when restoring Data (extractTarFork() process ended with ERROR: 255); is there any way to remedy this? Thank you!

Edit: It seems like «offending» folders aren’t ignored (misc/user/non-0; vendor_ce/10; vendor_de/10,11 etc.) inside the backup.

@pannal Please provide the recovery log. It contains the offending files/folders which will be helpful in creating a fix.

https://gerrit.twrp.me/c/android_bootable_recovery/+/2698 will at least warn the user upon doing backups and restores if they have undecrypted users.

Next I’ll look into actually ignoring certain files/directories based on what is and isn’t decrypted. Due to many differences between devices however, a general warning seems necessary.

Restoring Data (excl. storage)... Invalid encryption mode file /data/unencrypted/mode I:InfoManager loading from '/data/media/2021-03-12--09-52-46_PQ3A190801002/data.info'. I:Read info file, restore size is 22596419072 I:Multiple archives Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode Invalid encryption mode file /data/unencrypted/mode I:First tar file '/data/media/2021-03-12--09-52-46_PQ3A190801002/data.f2fs.win000' not encrypted I:Setting archive type I:Extracting uncompressed tar ==> extracting: //data/bootchart/ (mode 40755, directory) restoring policy 1DK > '80c25f2d77000000' to '//data/bootchart/' ==> extracting: //data/misc/ (mode 41771, directory) restoring policy 1DK > '80c25f2d77000000' to '//data/misc/' ==> extracting: //data/misc/recovery/ (mode 40770, directory) tar_extract_file(): failed to extract //data/misc/recovery/ !!! I:Unable to extract tar archive '/data/media/2021-03-12--09-52-46_PQ3A190801002/data.f2fs.win000' Error during restore process. I:Error extracting '/data/media/2021-03-12--09-52-46_PQ3A190801002/data.f2fs.win000' in thread ID 0 I:Error extracting split archive. Error during restore process. extractTarFork() process ended with ERROR: 255

Any idea how to fix this?

Full log https://www.dropbox.com/s/sbqwrko3yoop0wg/recovery.zip?dl=0

I’ve tried multiple suggestions:

• remove all users other than 0
• remove /system/addon.d
• Disable screen lock

They didn’t work. One plausible solution is to format data (and restore it from backup) but it is not corrupted. I’m wondering if I can do something less drastic. The error log might give some hints:

Backing up Data (excl. storage)...
Backups of Data do not include any files in internal storage such as pictures or downloads.
Invalid encryption mode 'ice:aes-256-cts'
I:Creating backup...
I:Creating tar file '/usb_otg/TWRP/BACKUPS/xxxxxx/data.ext4.win'
failed to lookup tar policy for '/data/extm' - 'ffffff'
I:Error adding file '/data/extm' to '/usb_otg/TWRP/BACKUPS/xxxxxx/data.ext4.win'
Error creating backup.

Looks like multiple encryption policies were used because I did not format data when flashing MIUI 12.5 over 12.0.

The directory /data/extm was empty so I removed it. Now the error is gone. 👍

I believe the error message is extremely ambiguous and everyone has a slightly different variation. You really need to look at the recovery.log to get to the problem.

I:Data backup size is 14796MB, free: 88576MB.
...done
I:Backup Name is: '2021-11-04--23-03-31_RP1A200720011'
I:Backup_Folder is: '/external_sd/TWRP/BACKUPS/ifsc7pvk4hmrp7mv/2021-11-04--23-03-31_RP1A200720011'
I:Calculating backup details...
I:Backup_List: /data;
I:backup_path: /data
 * Total number of partitions to back up: 1
 * Total size of all data: 14796MB
 * Available space: 93257MB
[BACKUP STARTED]
 * Backup Folder: /external_sd/TWRP/BACKUPS/ifsc7pvk4hmrp7mv/2021-11-04--23-03-31_RP1A200720011
Invalid encryption mode 'aes-256-xts:aes-256-cts:v1'
Backing up Data (excl. storage)...
Backups of Data do not include any files in internal storage such as pictures or downloads.
Invalid encryption mode 'aes-256-xts:aes-256-cts:v1'
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/external_sd/TWRP/BACKUPS/ifsc7pvk4hmrp7mv/2021-11-04--23-03-31_RP1A200720011/data.f2fs.win000'
I:addFile '/data/bootchart' including root: 1
  ==> set selinux context: u:object_r:bootchart_data_file:s0
failed to lookup fscrypt tar policy for '/data/bootchart' - '5d9d3047000000000000000000000000'
I:Error adding file '/data/bootchart' to '/external_sd/TWRP/BACKUPS/ifsc7pvk4hmrp7mv/2021-11-04--23-03-31_RP1A200720011/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/ifsc7pvk4hmrp7mv/2021-11-04--23-03-31_RP1A200720011/data.info'
createTarFork() process ended with ERROR: 255

I was able to backup after the same error.

1. Run the backup, make it fail
2. Go to advanced menu in TWRP and save log file
3. Restart your phone, open the log (it will be in the internal SD root) and scroll to the end of the log. There will be an error for «failed to look up tar policy for /path»
   For me it was the ‘perboot’ and ‘extm’ folder. Keep in mind twrp stops at the first error and you may need to run backup multiple times to find all these folders. Both the folders were empty so I just deleted them as is. Also keep in mind both of the mentioned folders are recreated upon booting the phone so you have to remove every time you want to do backup.
4. Restart into TWRP and do the backup as usual

I did this on Xiaomi Mi9T Pro (K20 Pro), MIUI 12.6

please try flashing this: RMDAD_v0.0.1.zip

That will remove any 999/10 folders, flashable in TWRP. Please report back.

Thanks a bunch. Tried multiple recoveries (let’s ignore for a moment, that they’re all based on TWRP), 32bit/64bit recovery variants. Didn’t even realize I had multiple users since I was already in fresh install of stock MIUI and custom ROM, and the TWRP log didn’t denote multiple user issue.
From the log:

Error adding file '/data/vendor/DAtS2XqVikNRygA0gBMJdD/hhgYsoZ4iNOjMBOquxuOuD/cPewyqrkf6WPKvfGP0elIB' to '/external_sd/TWRP/BACKUPS/Redmi_8A_DualPro/ELIXIR-2022-06-03--00-50-41/data.ext4.win'
Error creating backup.

Flashing RMDAD_v0.0.1.zip solved the createTarFork() process ended with ERROR: 255