[Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe] Muad.Dib:
Dear [MENTION=6042178]theimpulson[/MENTION],

I would like to kindly report some issues I am having with lastest version of OFFICIAL TWRP twrp-3.4.0-0-begonia.

I am on an EEA device running stock EEA MIUI 11.0.2.0 P and I am rooted.

I recently switched to the latest recovery release because it was the latest release I could find and I was eager to try the new features added like multiple user support and decryption.

So I started to do some testing.

On a device without lock screen password atm I simply enabled dual apps for a few apps (creating user 999).

Backup went fine without error, when before it could not go one as soon as it encountered a 999 folder. That's progress.

Making a backup is a good thing, but only worth if you can restore it.

So I formatted data (and internal storage) and went back to stock image (same version) without modification, and then tried to restore my previously made backup.

It failed on first 999 folder not being able to find key to decrypt almost at the very beginning of data restore (few %).

So I decided to do initial setup of the stock image till the end. Then rebooted back to recovery to try flashing Data again.

It failed on first 999 folder not being able to find key to decrypt almost at the very beginning of data restore (few %).

Since it was failing to find keys still I had idea to pick a few apps and enable dual apps just for them. Went back to recovery and tried to flash Data again.

That time it went further not encountering any decryption problem for user 999, apparently it had found the keys which seems to be the same, after I enabled dual apps again.

That process for restoring, not describe anywhere afaik, is not select backup, swipe and reboot from the old days, but since many more things are supported on modern phones, I dont really mind, only have to figure out the right way to do it, to make it as efficient as it could be.

However restore could not complete fully. It got stopped at a particular file as being showed by logs, here are the last few lines including those before error for a bit of context:

restoring policy 1DK > '7be9502e064d5287' to '//data/vendor/mtklog/aee_exp/temp/'
==> extracting: //data/vendor/.tp/ (mode 40775, directory)
restoring policy 1DK > '7be9502e064d5287' to '//data/vendor/.tp/'
==> extracting: //data/vendor/secure_element/ (mode 40770, directory)
restoring policy 1DK > '7be9502e064d5287' to '//data/vendor/secure_element/'
==> extracting: //data/vendor/trusty/ (mode 40775, directory)
restoring policy 1DK > '7be9502e064d5287' to '//data/vendor/trusty/'
==> extracting: //data/vendor/dumpsys/ (mode 40775, directory)
*** using existing directory
I:Setting archive type
I:Extracting gzipped tar
I:eek:pening gzip compressed tar...
==> extracting: //data/vendor/dumpsys/mrdump_preallocated (file size 6081740800 bytes)
tar_extract_file(): failed to extract //data/vendor/dumpsys/mrdump_preallocated !!!
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/SOVWEUK7CQTOQWPR/2020-07-27--18-06-18_PPR1180610011_PHASE2/data.ext4.win004'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/SOVWEUK7CQTOQWPR/2020-07-27--18-06-18_PPR1180610011_PHASE2/data.ext4.win004' 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

begonia:/data/vendor # ls -lah dumpsys/
total 2.8G
drwxrwxr-x 2 system system 4.0K 2020-07-21 20:33 .
drwxrwx--x 39 root root 4.0K 2020-07-28 13:19 ..
-r-------- 1 root root 5.6G 2020-07-28 10:00 mrdump_preallocated

By any chance would you know what is this file is for exactly, and if I could simply delete it (I am root) either before making backup or from the backup archives themselves? It is quite huge and besides making my restores fail to complete taking a lot of space in backup itself.

Judging by it size, almost 6G, I am wondering if it is not something like a ram dump, or like the windows hibernation file, would you know by any chance if that's safe to delete?

One small addition, besides restore failing to complete stopping on that file, fortunately file being close to the end (vendor folder) restore had worked and I found back my system like it was at last reboot minor a few configuration which probably were stored in internal storage.

Hope this helps.

Regards and again thanks for your hard work for this device support!

Cheers!