Since you have your device rooted, could you try using ClockWorkMod (cwm)? I don't trust TWRP very much. Also Titanium Backup is very good for rooted devices.
Last edit: dragomerlin 2018-01-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No. I would have loved to try this, but the screen was broken and I managed to pull out a backup with TWRP. As I thought I had a backup, I proceeded to dissassemble the phone in a try to fix it and it is now in parts waiting for repair.
Ok, I don't know what kind of backup you did, but I just tried today with twrp-3.2.1-0 and it just generated simple tar files, provided that you don't choose compression or something like that. The file list for my device is:
TWRP makes a raw backup of the ext4 filesystem, which has nothing to do with the real "adb backup" which is a tar filesystem. If you want to restore the TWRP backup you need to root the destination device, you can't use adb restore because Google's adb doesn't allow direct modification of the filesystem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Twrp seems to add some rows.
$ java -debug -jar "/home/jonathan/Downloads/Android Backup Utilities/Android Backup Extractor/android-backup-extractor-20171005-bin/abe.jar" unpack backup.ab backup.tarInvlaid Magic: TWRPtwstreamheader¨G+TWRPtwfilename h?fs”/external_sd/TWRP/BACKUPS/88f12f77/2018-01-22--10-32-14_onyx-userdebug_7.1.2_NJH47F_4cb9ee3dc1/system.ext4.winTWRPtwdatablockDÝíº/addon.d/00407550000000000000000000000062132311571050011257xustar rootroot50 RHT.security.selinux=u:object_r:system_file:s0Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)Caused by: java.lang.RuntimeException: java.lang.IllegalArgumentException: Invalid Magic TWRPtwstreamheader¨G+TWRPtwfilename h?fs”/external_sd/TWRP/BACKUPS/88f12f77/2018-01-22--10-32-14_onyx-userdebug_7.1.2_NJH47F_4cb9ee3dc1/system.ext4.winTWRPtwdatablockDÝíº/addon.d/00407550000000000000000000000062132311571050011257xustar rootroot50 RHT.security.selinux=u:object_r:system_file:s0 at org.nick.abe.AndroidBackup.extractAsTar(AndroidBackup.java:502) at org.nick.abe.Main.main(Main.java:128) ... 5 moreCaused by: java.lang.IllegalArgumentException: Invalid Magic TWRPtwstreamheader¨G+TWRPtwfilename h?fs”/external_sd/TWRP/BACKUPS/88f12f77/2018-01-22--10-32-14_onyx-userdebug_7.1.2_NJH47F_4cb9ee3dc1/system.ext4.winTWRPtwdatablockDÝíº/addon.d/00407550000000000000000000000062132311571050011257xustar rootroot50 RHT.security.selinux=u:object_r:system_file:s0 at org.nick.abe.AndroidBackup.extractAsTar(AndroidBackup.java:332) ... 6 more
Skipping them helped but I don't get all data from an extraction. Help would be really appreciated :-)
Check your file:
$ head backup.ab
Twrp has added some things in the beginning. Skipping those with:
$ dd if=backup.ab bs=512 skip=3 | head
Got me to a semiworking extraction.
$ dd if=backup.ab bs=512 skip=3 | tar -x
Since you have your device rooted, could you try using ClockWorkMod (cwm)? I don't trust TWRP very much. Also Titanium Backup is very good for rooted devices.
Last edit: dragomerlin 2018-01-30
No. I would have loved to try this, but the screen was broken and I managed to pull out a backup with TWRP. As I thought I had a backup, I proceeded to dissassemble the phone in a try to fix it and it is now in parts waiting for repair.
Another project with this issue:
https://github.com/julien-lang/twrp-adb-backup-extractor
Ok, I don't know what kind of backup you did, but I just tried today with twrp-3.2.1-0 and it just generated simple tar files, provided that you don't choose compression or something like that. The file list for my device is:
It looks like your TWRP did a weird kind of .ab file. Never happened to me before.
Last edit: dragomerlin 2018-01-30
screen was broken so the only option left was backup from adb:
https://twrp.me/faq/openrecoveryscript.html
twrp produces his own backup.ab, which is just a normal data.ext4.win with a 1536 bytes header:
TWRP makes a raw backup of the ext4 filesystem, which has nothing to do with the real "adb backup" which is a tar filesystem. If you want to restore the TWRP backup you need to root the destination device, you can't use adb restore because Google's adb doesn't allow direct modification of the filesystem.