I tried doing a backup and it fails each time on backing up system (either that or finishes it and fails straight after)
The log is attached. (I deleted previous backup info from it so it will fit the allowed size for upload, if its important tell me i'll divide the file)
The error message reads:
E:tar_open error opening ''
E:Error creating tar '' for thread 0
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:createTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
How can I fix this?
[edit]
@xanthrax gave me the solution: enable compression
Related
So im trying to restore CM13 (Temasek's Rom) back onto my phone after flashing the official 6.0.1 india rom and finding it quite basic tbh. For some reason it keeps failing to restore the Data section and ive copied the output below:
==> extracting: //data/app/com.facebook.katana-3/oat/arm/ (mode 40771, directory)
I:Extracting gzipped tar
Ipening as a gzip...
==> extracting: //data/app/com.facebook.katana-3/oat/arm/base.odex (file size 214532528 bytes)
tar_extract_file(): failed to extract //data/app/com.facebook.katana-3/oat/arm/base.odex !!!
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/95f4b792/2016-06-19--07-23-55_cm_kltedv-userdebug_6.0.1_MOB30D_ab649f68a6/data.ext4.win002'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/95f4b792/2016-06-19--07-23-55_cm_kltedv-userdebug_6.0.1_MOB30D_ab649f68a6/data.ext4.win002' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
How can i get around this file? I really need to get my Messages, Social Media data and as much of everything back from the backup.
I cannot complete a full backup. It gets to 98% and fails with the following error
I:addFile '/data/system_ce/0/recent_images/18314_activity_icon_1528351915071.png' including root: 1 ==> set selinux context: ubject_r:system_data_file:s0 I:addFile '/data/system_ce/999' including root: 1 ==> set selinux context: ubject_r:system_data_file:s0 failed to lookup tar policy for '/data/system_ce/999' - 'a502596862cdda88' I:Error adding file '/data/system_ce/999' to '/data/media/0/TWRP/BACKUPS/89b79b75/2018-06-07--01-14-13/data.ext4.win008' Error creating backup. I:ERROR tarList for thread ID 0 Error creating backup. I:InfoManager saving '/data/media/0/TWRP/BACKUPS/89b79b75/2018-06-07--01-14-13/data.info' createTarFork() process ended with ERROR: 255 Backup Failed. Cleaning Backup Folder. I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/89b79b75/2018-06-07--01-14-13/recovery.log
Inside that folder there are screenshots of everything I'm doing on the phone! Lots of sensitive information like my PayPal or email. Is this part of the operating system or some type of Spyware?!
I'm finding many mentions of these folders on various forums and threads but the only hint is that it's related to parallel apps and the user has to be deleted. That still doesn't explain to me why it's taking screenshots of my activities
https://forum.xda-developers.com/showpost.php?p=75342215&postcount=180
I was able to finish the backup by booting back to the os and running the following from a terminal
su
pm remove-user 999
I'd still like to know why the system is screenshotting all of my apps
braschlosan said:
I was able to finish the backup by booting back to the os and running the following from a terminal
su
pm remove-user 999
I'd still like to know why the system is screenshotting all of my apps
Click to expand...
Click to collapse
Probably your phone is hijacked or as you suspect Spyware/other apps.
I would to format your internal storage and every other partition. After a clean installation of your OS check your network usage with glasswire for example to see if something is using your traffic.
braschlosan said:
Inside that folder there are screenshots of everything I'm doing on the phone! Lots of sensitive information like my PayPal or email. Is this part of the operating system or some type of Spyware?!
I'm finding many mentions of these folders on various forums and threads but the only hint is that it's related to parallel apps and the user has to be deleted. That still doesn't explain to me why it's taking screenshots of my activities
https://forum.xda-developers.com/showpost.php?p=75342215&postcount=180
Click to expand...
Click to collapse
Seems like it's AOSP recents feature; https://forum.xda-developers.com/showpost.php?p=70361290&postcount=7641
Hello,
I've got a problem I couldn't find a solution for: Before trying to flash a custom ROM, I wanted to do a Backup of the "original" system (rooted samsung android 4.4.2 KitKat). As listed by the devs of TWRP on their site (https://twrp.me/faq/whattobackup.html), I selected system, data and boot. System and boot were backuped to card without error (when selected without data), but backing up data always fails with error message "createTarFork() process ended with ERROR 9".
I could find threats about error 255, but nothing about error 9. Can you please help me solving this issue so I can create a backup of media as well?
These are the last lines of recovery.log:
I:InfoManager saving '/external_sd/TWRP/BACKUPS/1633cc05/2019-05-15--20-00-46_KOT49HI9301IXCUAOF1/data.info'
Prozess createTarFork() endete mit Meldung: 9 // createTarFork() process endet with message 9
Sicherung fehlgeschlagen, bereinige Sicherungs-Verzeichnis // creating backup failed. cleaning up...
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/1633cc05/2019-05-15--20-00-46_KOT49HI9301IXCUAOF1/recovery.log
Click to expand...
Click to collapse
Hi. I have a Moto G6 Plus (evert) phone and I currently have LineageOS 17.1-20201117 installed on it. Everything works perfectly, however, there are some updates that I'd like to install. I'm not sure whether this will remove/corrupt Magisk (or break something else), so I wanted to back up all partitions using TWRP (3.5.1) just to be on the safe side. When I first booted into TWRP, I noticed that it didn't ask for a password, which it did before I had LineageOS on my phone. But now, nothing. If I attempt to do a backup, I get an error: createtarfork() process ended with error 255. I did some googling and apparently, this could be caused because TWRP can't read some partitions. I tried an older version of TWRP (3.4), but that didn't help.
Here's the recovery.log created while trying to back up:
I:Error adding file '/data/vendor/MFYxVGEouF4EC,7Sj90vJA/JjO3E2T3tbuQVW,frUXMWA' to '/external_sd/TWRP/BACKUPS/ZY322V6SQC/2021-03-13--16-49-49_lineage_evert-userdebug_10_QQ3A200805001_e3/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0 Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/ZY322V6SQC/2021-03-13--16-49-49_lineage_evert-userdebug_10_QQ3A200805001_e3/data.info'
createTarFork() process ended with ERROR: 255 Backup Failed. Cleaning Backup Folder.
Looks like TWRP failed to back up /data/vendor/MFYxVGEouF4EC,7Sj90vJA/JjO3E2T3tbuQVW,frUXMWA. The name looks weird. I booted back into the system and opened Total Commander, navigated to /data/vendor/, and the directory looked "normal" with "normal" subdirectories and everything. So it seems like TWRP is not decrypting the data partition.
I can also see some other errors above this one.
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0 libc: Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb libc: Unable to set property "ro.crypto.type" to "file": error code: 0xb
However, I'm not sure what this means exactly.
Here's the full log: https://pastebin.com/z8cQWQ21
I'm still kinda confused about TWRP not asking for a password. Before I had LineageOS (I was using the stock ROM with encryption enabled) TWRP was asking for a password. I also tried removing the password, but the backup failed anyway (same error). Most likely because encryption is still enabled regardless of whether there's a password/PIN/pattern set up.
br0kenpixel said:
Hi. I have a Moto G6 Plus (evert) phone and I currently have LineageOS 17.1-20201117 installed on it. Everything works perfectly, however, there are some updates that I'd like to install. I'm not sure whether this will remove/corrupt Magisk (or break something else), so I wanted to back up all partitions using TWRP (3.5.1) just to be on the safe side. When I first booted into TWRP, I noticed that it didn't ask for a password, which it did before I had LineageOS on my phone. But now, nothing. If I attempt to do a backup, I get an error: createtarfork() process ended with error 255. I did some googling and apparently, this could be caused because TWRP can't read some partitions. I tried an older version of TWRP (3.4), but that didn't help.
Here's the recovery.log created while trying to back up:
I:Error adding file '/data/vendor/MFYxVGEouF4EC,7Sj90vJA/JjO3E2T3tbuQVW,frUXMWA' to '/external_sd/TWRP/BACKUPS/ZY322V6SQC/2021-03-13--16-49-49_lineage_evert-userdebug_10_QQ3A200805001_e3/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0 Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/ZY322V6SQC/2021-03-13--16-49-49_lineage_evert-userdebug_10_QQ3A200805001_e3/data.info'
createTarFork() process ended with ERROR: 255 Backup Failed. Cleaning Backup Folder.
Looks like TWRP failed to back up /data/vendor/MFYxVGEouF4EC,7Sj90vJA/JjO3E2T3tbuQVW,frUXMWA. The name looks weird. I booted back into the system and opened Total Commander, navigated to /data/vendor/, and the directory looked "normal" with "normal" subdirectories and everything. So it seems like TWRP is not decrypting the data partition.
I can also see some other errors above this one.
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0 libc: Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb libc: Unable to set property "ro.crypto.type" to "file": error code: 0xb
However, I'm not sure what this means exactly.
Here's the full log: https://pastebin.com/z8cQWQ21
I'm still kinda confused about TWRP not asking for a password. Before I had LineageOS (I was using the stock ROM with encryption enabled) TWRP was asking for a password. I also tried removing the password, but the backup failed anyway (same error). Most likely because encryption is still enabled regardless of whether there's a password/PIN/pattern set up.
Click to expand...
Click to collapse
Your current ROM uses File-based Encryption (FBE) and apparently your TWRP build does not support this. Are you using an official TWRP build? Have you seen if in the TWRP thread for your device there are other users with the same problem?
Hi,
I am trying to install the latest Lineage version on my Samsung Nexus 10 via twrp, but so far it always immediately fails with
Error E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-17.1-20220318-UNOFFICIAL-manta.zip'
I tried wiping the entire system, cache and all and I tried both the adb push method and sideloading adb and they all produce the exact same error.
This is my first time doing this type of thing, so any help would be greatly appreciated.
P.S. I am currently running Windows 10, but could boot into a Linux Live Medium if that would be useful.
Edit: I was following this tutorial for the setup.
I'm facing exactly the same issue here with the installation of `lineage-17.1-20220919-UNOFFICIAL-manta.zip` file.
I'm currently on the latest original Google Android ROM flashed with `image-mantaray-lmy49j.zip` and want to update the system to the lineage OS as above.
I'm using TWRP v3.6.2_9.
What I did:
- uploaded `lineage-17.1-20220919-UNOFFICIAL-manta.zip` to `/sdcard` location;
- wiped out `dalvik-cache` and `cache` partitions;
- tried to install `lineage-17.1-20220919-UNOFFICIAL-manta.zip` as a single installation file;
Got this error. Here is an output from recovery.log:
Code:
Installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keysTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/4dd6bf24fbba9cc76c352f5c4cfaed0074be0244
535756800 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 3367 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,225950,228864,229947,230400]
new data receiver is still available after executing all commands.
Patching system image unconditionally...script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Does anyone have any clue on what could be wrong here and why it fails?
unpack zip remove lines, then pack zip and try again. voilla
or utube eroor 7
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Cpluo said:
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Click to expand...
Click to collapse
Not enough space on /system. Resize the partition. After 17.1 is running for me. https://www.hovatek.com/forum/thread-32750.html
Thanks a lot Daniel! I will try your way.