Error when doing TWRP backup, `recovery.log` shows nonexistent folders

Asked Jan 26 '22 at 08:26

Active Jan 28 '22 at 20:13

Viewed 439 times

The device is Samsung Galaxy A40 with Android 11, rooted with Magisk. I followed the suggestions contained in TWRP createTarFork() error 255 when backing up data.

In the first recovery.log, this folder appears: /data/tombstones/Zde6fQiwYL9jsduZ4MuTrD; so I deleted it. I relaunched the TWRP backup and, this time, the folder /data/vendor/M6TyZoh48zRvZQ97YG++eA/ZIaJXVgostztDsV2y4OuqC/GZ3BaraBTRfTO9HxQbjcqA/+TJ7GPVoY48 appears in the relative recovery.log, but it is non-existent.

Some idea?

edited Jan 27 '22 at 16:43

Andrew T.

15,988
10
74
123

asked Jan 26 '22 at 08:26

Fritz T

Does this answer your question? copy encrypted internal storage to pc ( in twrp mode ) – alecxs Jan 26 '22 at 08:44
maybe, but I don't know – Fritz T Jan 26 '22 at 20:24
Some newer devices running TWRP exhibits this problem, honestly you shouldn't use that backup feature, dd is good enough for backing up. – Tipz Team Jan 28 '22 at 09:33
Forgive my ignorance. What is dd? – Fritz T Jan 28 '22 at 20:13
your /data partition is encrypted. no matter what kind of backup you try it's all just garbage (like you see). what you are trying to do is pointless. you can 'adb pull /dev/block/bootdevice/by-name/userdata' but that file is useless (except for restoring to phone as is). if you wanna backup your apps go for Migrate – alecxs Jan 28 '22 at 21:05

Error when doing TWRP backup, `recovery.log` shows nonexistent folders

0 Answers0