Hey there,
My brother was trying to install a custom ROM on his phone but it was having issues so he went to restore a TWRP backup of an AOSP ROM he had before. Unfortunately, it was a backup of every partition, including the Firmware partition. When it got to restoring Firmware, it formatted the existing firmware partition, but then immediately failed at restoring the old Firmware partition backup with the following showing in the recovery.log:
Code:
I:Extracting uncompressed tar
==> extracting: /firmware//image/ (mode 40550, directory)
tar_extract_file(): failed to set permissions on /firmware//image/ !!!
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/QV7013TG03/Firm/firmware.vfat.win'
Error during restore process.
extractTarFork() process ended with ERROR: 255
After this, any attempts to start the phone result in a bootloop. We can still get into recovery but every time we try to restore the TWRP backup it fails at firmware again. Any ideas on how to get the phone working?
EDIT: Fixed!
I fixed this a while ago but if I recall correctly, we ended up flashing the stock firmware files with Flashtool. Basically go to this thread follow the steps under Part 2 and Part 2.5, then once you've created the firmware, flash it using Flashtool --> Lightning Button --> Flashmode --> Choose the firmware you made --> Wipe Userdata (not sure if we did this or not, try without it, if it doesn't work then wipe userdata) -->Flash. That should fix it.
I have never managed to restore backup on this stupid phone. Always errors with making backup or restoring backup or not detecting storage or some other crap. Sick of it
Hello,
I use an stock android 9 ROM. When 8 try to backup this Rom I get this issue.
```
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1237
```
```
I:Error adding file '/data/vendor_ce/11' to '/data/media/0/TWRP/BACKUPS/FA6AD0307055/2018-08-28--15-30-48_PPR1180610009/data.ext4.win003'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/FA6AD0307055/2018-08-28--15-30-48_PPR1180610009/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/FA6AD0307055/2018-08-28--15-30-48_PPR1180610009/recovery.log
```
I can't make any backup.
What version of TWRP? Have you tried uninstalling and reinstalling Magisk? Have you tried backing up to an external drive, such as through a USB-OTG?
post-mortem said:
What version of TWRP? Have you tried uninstalling and reinstalling Magisk? Have you tried backing up to an external drive, such as through a USB-OTG?
Click to expand...
Click to collapse
I have the latest available version if TWRP installed. Why I must try to uninstall and reinstall Magisk? No external drive is available
Update here:
I flashed the complete firmware again, then installed TWRP and it works.
This is a Flashable Zip for restoring backups created from different recoveries. No more problems with checksums, checksums will be ignored.
- Android system recovery <3e>
- CWM
- TWRP
- ADB Backup
- MIUI Backup
This is a alpha release, in this state you can test it for Android system recovery <3e> only!
I need testers for proof of concept. If you have a Mediatek Phone with encrypted userdata_20160823_100259.backup, please try to restore with bckp2raw.zip from TWRP. Please give feedback if failed or vote :good: if worked.
bckp2raw.zip (v1.0.3) 32-bit
bckp2raw.zip (v1.0.5) universal
(other backup formats following soon, feel free to request)
TUTORIAL - under construction
aIecxs said:
TUTORIAL - under construction
Click to expand...
Click to collapse
Is this solves problem of Android 7 stock recovery backup?
I got second phone stock recovery problem for 7 version
stock recovery do not want to recover his backup. complains - "it is corrupted, please reset your phone"
I install twrp recovery and try to install this .zip
bit it give error 134 (or something like that)
sorry this project is abandoned. in generally, backup can not restored to other device because of the checksum mismatch. Thats where this zip comes in game. If you upload recovery.log right after installing this zip i will try to fix the errors..
aIecxs said:
sorry this project is abandoned. in generally, backup can not restored to other device because of the checksum mismatch. Thats where this zip comes in game. If you upload right after installing this zip i will try to fix the errors..
Click to expand...
Click to collapse
I meant - I got another (second) phone looped reboot, same as in 2018. And try to stock recovery backup (55Gbyte and ) restore.
BTW - first phone is still waiting to restore 11Gbyte stock recovery backup!
last file: userdata_20191106_110350.backup27
Android 7 again same as in topic: https://forum.xda-developers.com/showthread.php?t=2528969&page=7
I copied lines from recovery.log:
I: operation_start: 'Flashing'
Installing zip file '/external_sd/bckp2raw.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/bckp2raw.zip
inflating: bckp2raw.sh
Archive: /external_sd/bckp2raw.zip
inflating: busybox-arm
Archive: /external_sd/bckp2raw.zip
inflating: tar-arm
CANNOT LINK EXECUTABLE "/system/bin/sh": "/system/lib/libc++.so" is 32-bit instead of 64-bit
Aborted
Updater process ended with ERROR: 134
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/external_sd/bckp2raw.zip'
Dont want to boring and get you, if you would give help - you can save many people with same problem with android-7
ah i see, script does not even start. i don't have a x64 device for testing, i assume twrp is not able to run mksh from /system. i have added paths please try this one instead...
update-binary
Code:
LD_LIBRARY_PATH=/system/lib64:/system/vendor/lib64:/system/lib:/system/vendor/lib
bckp2raw.zip (v1.0.5) universal
for those who want to quickly convert TWRP ADB backup.ab into data.ext4.win
usage for unpacking files (don't do this on windows disk)
Code:
bash twab.sh backup.ab
cd 20*
mkdir data
sudo tar --ignore-command-error --numeric-owner --selinux --xattrs -xpf data.ext4.win -ivC data 2> /dev/null
data partition is encrypted
Hi , I've been trying a lot of methods to get my data back from my .backup files. All with no results. Your bckp2raw script seems to be one of the most successfull , but it ends by a " data partition is encrypted" ... Do you think I can still recover my files ... The original phone is actually working but it has been factory wiped ...
that message just means that your current /data partition is encrypted (message for encrypted backup is different)
- do a backup of metadata partition (just in case)
- do a backup of /sdcard to PC (adb/mtp)
- format userdata partition
- reboot TWRP
- check userdata partition is unencrypted
- restore userdata*.backup from zip
- restore metadata partition from backup
- restore /sdcard backup
the restoring process will deny if userdata is not empty. please note if backup is encrypted it is most likely useless without corresponding backup of metadata partition
aIecxs said:
that message just means that your current /data partition is encrypted (message for encrypted backup is different)
- do a backup of metadata partition (just in case)
- do a backup of /sdcard to PC (adb/mtp)
- format userdata partition
- reboot TWRP
- check userdata partition is unencrypted
- restore userdata*.backup from zip
- restore metadata partition from backup
- restore /sdcard backup
the restoring process will deny if userdata is not empty. please note if backup is encrypted it is most likely useless without corresponding backup of metadata partition
Click to expand...
Click to collapse
Thank you very much for your quick reply. Ok so I tried it , the restoring part worked , but when I rebooted it asked me for my code and said "password is correct but data is corrupted" ....
Do you have any idea for me to get my data back .... at least my pictures ...?
sounds like the backup is encrypted, can you confirm? more important is this the source phone of this backup? or do you try to restore on other device?
aIecxs said:
sounds like the backup is encrypted, can you confirm? more important is this the source phone of this backup? or do you try to restore on other device?
Click to expand...
Click to collapse
I'm pretty sure it is encrypted. Yes the phone is the source phone of the backups
encryption should work in theory, but you need a copy of metadata partition from the day you created backup. you most likely don't have it, therefore your data is lost forever
aIecxs said:
encryption should work in theory, but you need a copy of metadata partition from the day you created backup. you most likely don't have it, therefore your data is lost forever
Click to expand...
Click to collapse
Yes I don't have the metadatas from that day, is there a chance that they have been backup with the android backup ?
Thanks for your help anyways, I'm sad
no, nothing you can do. even a old metadata from the first day when you buyed this device would probably do it. metadata partition is formatted on factory reset.
for some devices the crypto footer is not located at separate partition, but at the end of userdata partition instead. But this is not the case for your device, otherwise this zip would have restored. you can double check, search with hex editor in last -16384 bytes of last file for string aes-cbc-essiv:sha256 (or aes-xts)
aIecxs said:
no, nothing you can do. even a old metadata from the first day when you buyed this device would probably do it. metadata partition is formatted on factory reset.
for some devices the crypto footer is not located at separate partition, but at the end of userdata partition instead. But this is not the case for your device, otherwise this zip would have restored. you can double check, search with hex editor in last -16384 bytes of last file for string aes-cbc-essiv:sha256
Click to expand...
Click to collapse
Cannot find anything like this but i'm not used to HEX reading .... Is there a chance that the metadata is on the SD card i was using for (external) storage on the phone (not the ones for the backups) ?
Hello there and thanks for creating such a productive thread, just what I needed for my current situation. so am trying to retrieve .backup files on cxAir android 7.0 after root through twrp but apparently, when running the script from the zip file you've shared I get the Error: data partition not mounted.
I'm still new in the dev world but am totally excited about it and I may not understand a lot of things but am willing to work my ass off to figure out the most of what I can so please I'd really appreciate it if I could get some help on this one, thanks in advance
mount data partition and try again?
I'm trying to install LineageOS and then GAPPS on my Pixel XL from TWRP recovery. I'll try to `Advance Wipe` the `/systems` directory and `Format Data`, but I continue to get multiple errors:
Code:
Failed to mount '/system' (Device or resource busy)
Code:
Failed to mount '/vendor' (Device or resource busy)
And
Code:
Unable to wipe 'System'
Code:
Unable to wipe '/system'
If I just continue with `adb sideload lineageos.zip` most of the time it stops about halfway (PowerShell shows `47%`) through and then TWRP shell shows:
Code:
Installing zip file '/sideload/package.zip'
Step 1/2
Step 2/2
I then try to `sideload` the `gapps.zip` file and get another error saying `/system` doesn't have enough space. I've tried sideloading several different gapps versions including their smallest `pico` zip fie of `91.39 MiB`.
I am able to then boot into LineageOS, but no GAPPS show and I'm not able to run any new apps installed via APK without them crashing.
My assumption is that I need to fully wipe `system` and format it, but I've been trying for two days now and still get the above `(Device or resource busy)` errors. Any help would be much appreciated!
Make sure you have the latest tools.
Latest TWRP for marlin is 3.3.0-0
Latest platform-tools is 29.0.1
Not sure what's the cause of this, but if you want to wipe and start fresh I think the best option is reflash the stock factory image that completely wipes everything and restores everything stock.
Then, you can retry wiping the device using the latest TWRP (currently, marlin is 3.3.1-0, the zip is 3.3.0-0, try just boot it and don't flash the zip), flash LOS and then gapps.
Also, as pointed by @post-mortem, make sure you are using the latest adb version when flashing the factory image, just to avoid any potential issue.
Don't use 3.3.1-0. Try 3.3.0-0. I had the same issue.
Why doesn't TWRP Team provide an answer as to why this happens? It appears to affect everyone with the latest official Pixel ROM.
Twrp is for Android pie and has trouble mounting stock Android 10. They have announced this on their website. This shouldn't matter since you're installing lineage. You don't need to wipe system before installing lineage because it installs into the inactive slot. You need to sideload lineage then reboot into recovery to switch slot's. The instructions are on the lineage website.
Did OP manage to solve this issue?
Galaxy S20 Ultra G988B XSA Z3S
LineageOS 18.1
TWRP 3.5.0_10-A11_6
Magisk 23.0
Attempt to create backup results in:
Error opening: '/data/bootchart' (Permission denied) [Repeat this line about 40 times with different folder names]
* Total number of partitions to back up: 13
* Total size of all data: 11256MB
* Available space: 106427MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/"filename"
Can not create '/data/media/0/TWRP' folder (Invalid argument).
Failed to make backup folder
Click to expand...
Click to collapse
I have a pin on my phone, twrp does not ask for it. Removing the pin does not alter the result. The folders are not encrypted, I can navigate them and view most files/folders. One thing in particular I can not open is /sdcard/, it just refreshes to the top.
My uneducated guess is that TWRP doesn't have root access to all partitions?