TWRP , extracttarfork() process ended with error=255, How to Fix.. ? - Xiaomi Redmi Note 4 Questions & Answers

Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

FurqanHanif said:
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
Click to expand...
Click to collapse
Answered you in the TWRP thread. Check again.

---

FurqanHanif said:
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
Click to expand...
Click to collapse
Just restore system, data,and boot , don't forget flash frimware..Done , solved.

---

sachin n said:
Answered you in the TWRP thread. Check again.
Click to expand...
Click to collapse
I am stuck with the same problem. Can you link me to your answer to him or just again tell me what's the solution?
Firmware was 90MB before, after trying to restore it, TWRP wiped it and now it's 23MB.

---

nilanko said:
I am stuck with the same problem. Can you link me to your answer to him or just again tell me what's the solution?
Firmware was 90MB before, after trying to restore it, TWRP wiped it and now it's 23MB.
Click to expand...
Click to collapse
The answer is to just restore system, data and boot. That's the way to go.
Sent from my mido using XDA Labs

---

I just restore system and data, but problem was occur like that. Any solution?

---

From my experience, i think it is because of miui rom??
After trying many time, I used this method .....
1. first wipe everything
2. flash original zip rom
3.then flash your backup
4. Flash lazyflasher
It will show error though but you will get radio working

---

Firmware Problem "extractTarFork process ended with ERROR 255"
In My case Firmware is not restoring
shoiwing error "extractTarFork process ended with ERROR 255"
so to solve it
1.Wipe data dalvik cache and system
2.Just flash the new rom which u had earlier.
for exp. i had lineage 14.1
3.After installing it ask for wipe dalvik and cache do it then dont wipe it from the main menu.
4.just restore the backuped file without ticking the firmware
Note-Firmware must be untick while restoring
5.done Problem of fingerprint scanner and network problem also solved by this
Note-Dont restart in between
if it helps you
Subscribe to My Youtube Channel youtube.com/AnonymAb

---

AmanBhagat said:
In My case Firmware is not restoring
shoiwing error "extractTarFork process ended with ERROR 255"
so to solve it
1.Wipe data dalvik cache and system
2.Just flash the new rom which u had earlier.
for exp. i had lineage 14.1
3.After installing it ask for wipe dalvik and cache do it then dont wipe it from the main menu.
4.just restore the backuped file without ticking the firmware
Note-Firmware must be untick while restoring
5.done Problem of fingerprint scanner and network problem also solved by this
Note-Dont restart in between
if it helps you
Subscribe to My Youtube Channel youtube.com/AnonymAb
Click to expand...
Click to collapse
does not work for me. do you have any other method?

---

FurqanHanif said:
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
Click to expand...
Click to collapse
sohanaw said:
does not work for me. do you have any other method?
Click to expand...
Click to collapse
That happened to me twice, loosing the imei.
To fix it, just restore or flash any rom you want, and follow this steps:
Extract NON-HLOS.bin file from official ROM.
Copy extracted NON-HLOS.bin to the adb/fastboot folder.
Boot your device into fastboot mode.
Connect your device to PC
In the folder with adb/fastboot tools press “Shift” key + right mouse button and select “Open command window here”.
Enter these commands in order:
Code:
Fastboot devices
Fastboot.exe erase modem
Fastboot.exe flash modem NON-HLOS.bin
Fastboot.exe reboot
Check your IMEI. It should be restored now.

---

ramping said:
That happened to me twice, loosing the imei.
To fix it, just restore or flash any rom you want, and follow this steps:
Extract NON-HLOS.bin file from official ROM.
Copy extracted NON-HLOS.bin to the adb/fastboot folder.
Boot your device into fastboot mode.
Connect your device to PC
In the folder with adb/fastboot tools press “Shift” key + right mouse button and select “Open command window here”.
Enter these commands in order:
Code:
Fastboot devices
Fastboot.exe erase modem
Fastboot.exe flash modem NON-HLOS.bin
Fastboot.exe reboot
Check your IMEI. It should be restored now.
Click to expand...
Click to collapse
modem is okay i am able to flash that.
but for me persist is showing 0mb in twrp and i am unable to flash persist i have tried fastboot miflash none worked for me .
please if you have any other method then share.

---

Go back to StockROM with the help of Xiaomi's tools
Had the same problem. The methods above didn't work for me, either.
I went back to StockROM with the tools provided on the Xiaomi website, the process will re-flash the firmware, too and all described problems will be solved. Make sure you'll untick "firmware" on the next time when trying a restore

---

ramping said:
That happened to me twice, loosing the imei.
To fix it, just restore or flash any rom you want, and follow this steps:
Extract NON-HLOS.bin file from official ROM.
Copy extracted NON-HLOS.bin to the adb/fastboot folder.
Boot your device into fastboot mode.
Connect your device to PC
In the folder with adb/fastboot tools press “Shift” key + right mouse button and select “Open command window here”.
Enter these commands in order:
Check your IMEI. It should be restored now.
Click to expand...
Click to collapse
Well what can i said??u really save my poor soul last night!!been 2 days searching for solution after error 255 on my redmi 5 plus,ur solution work perfectly n thank you brooooo!!!???
Sent from my Redmi 5 Plus using XDA Labs

---

well this is weird.
I'm having error 255 on firmware partition restore, no matter what I do (redmi note4x snapdragon global, nandroid backups from stock miui8.5-9.2 and LAOS15.1)
However using (at least some of) my backups with firmware unticked and then installing firmware from TWRP package does the trick, like this one below:
https://forum.xda-developers.com/re...irmware-firmware-miui-9-china-stable-t3697976

---

I had this problem on a Redmi Note 3 Pro/Qualcomm recently. It seems to me to be loosely correlated to the /data backup size, and seems to manifest just below 4GB, looks suspiciously like some 32bit counter/offset ... but .... in my case this seems to happen only in the first tar/win file which much < 2GB uncompressed anyway.
Interestingly, not all tar binaries are equal. The binary from LineageOS 14.1 crashes reading win000 files often if I try to test this from a terminal session when the phone is booted normally, however tar from TWRP does work and doesn't crash. Using tar from ubuntu 18.04 I can see all the files, however there are numerous reports of
Code:
tar: Malformed extended header: missing equal sign
Maybe this tar crash is also what is happening for the TWRP GUI using it's internal tar? Although this seems to be crashing when the recovery is nearing 4GB, however my tar crash seems to happen on the first segmented win000 file? Maybe it is related in some way to pigz which seems to be used by the TWRP GUI to compress/uncompress and it does multi-threading. I haven't looked at TWRP code.
I tried TWRP 3.1.1-0, and downloaded the latest 3.2.3-0 from twrp.me. Both failed in the same way.
I inspected some of the backups I had, finding decrypted /data space usage less /data/media:
Code:
$ ls -1
2018-09-06--12-41-18_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
2018-11-10--11-08-53_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
2019-01-10--10-01-22_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
2019-01-26--16-04-54_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
$ grep Data.backup.size */recovery.log|uniq|sed 's/\// /;s/--[^ ]* / /;s/:/ /'
2018-09-06 recovery.log I:Data backup size is 3464MB, free: 14062MB.
2018-09-06 recovery.log I:Data backup size is 3464MB, free: 11552MB.
2018-11-10 recovery.log I:Data backup size is 4622MB, free: 11065MB.
2018-11-10 recovery.log I:Data backup size is 4622MB, free: 7576MB.
2019-01-10 recovery.log I:Data backup size is 4041MB, free: 11284MB.
2019-01-10 recovery.log I:Data backup size is 4041MB, free: 8192MB.
2019-01-26 recovery.log I:Data backup size is 652MB, free: 24414MB.
$
I could restore 2018-09-06 and 2019-01-26 using TWRP GUI while the other 2 failed with error=255. Of the backups I could restore with the TWRP GUI, both backups are easily < 4GB. 2019-01-10 is just below, still no idea if it is related to 4GB. In each case I formatted /data before hand, so /data/media was empty, so there was 24GB of free space, so there was always at least 2 times, sometimes 5 times, the actual space required for the recovery available.
Irrespective of the actual failure mode, I was able to restore the other backups manually.
Interestingly when I examine the .win and .win000 files with
Code:
tar tvf file | sed 5q
I find that the single .win file backups need to be restored while current directory is /data whereas the multipart backups need to be restored while current directory is /.
Manual restore process from TWRP recovery shell :
Backup everything to storage external the phone, and then backup the backup.
Wipe /data. I prefer to format /data while also wipes /data/media = /sdcard as this guarantees /data is clean, however if your backups are stored in /sdcard/TWRP then you are going to need to either not format /data or restore them from your PC, or not store them in /sdcard/TWRP and store them on an external sdcard or external USB OTG drive. Actual location may vary depending on TWRP build. Determine the b= lines below appropriately.
Connect using adb shell. You could type this in using the TWRP Advanced Terminal, but error prone.
Make sure you have enough free space on /data to do the restore. You should have, but this is the manual process so cross check.
Restore the .win0?? files with tar.
Code:
... # PS1="# " # optional
# cd /location/TWRP/BACKUPS/serialnumber/2019-01-10* # location: sdcard sdcard1 usb-otg
# pwd # verify backup directory
/location/TWRP/BACKUPS/.../2019-01-10--10-01-22_...
# b=$(pwd) # remeber backup folder location
# ls -l data.*.win000 # verify backup file exists
-rw-rw---- 1 root sdcard_rw 1109681843 2019-01-26 11:02 data.ext4.win000
# for m in data*md5; do md5sum -c $m; done # verify md5 checksums of each tar/win file.
data.ext4.win000: OK
data.ext4.win001: OK
data.ext4.win002: OK
# cd /
# for w in $b/data*win0??; do echo recover $w; tar xpvf $w > $w.rec; echo; done
recover /.../data...win000
tar: removing leading '/' from member names
recover /.../data...win001
tar: removing leading '/' from member names
recover /.../data...win002
tar: removing leading '/' from member names
# cd $b
# wc -l data*rec # verify recovery of reasonable number of files
29346 data.ext4.win000.rec
343 data.ext4.win001.rec
1831 data.ext4.win002.rec
31520 total
# df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/dm-0 25667344 15051056 10599904 59% /data
#
Reboot

---

Download latest mido firmware and flash through twrp.

---

If you are on mido here is the solution i used
I flashed the last rom i had ( for my case :miui.eu 10.3 oreo port )
Then wipe data
The flashed the miui 10.1.1.0 for mido
And wait for it to boot up and you will be fine
You can update after to 10.2.3.0

---

The good fix!!!
TWRP always skip data/media in backup or restore. This is a problem!
Restoring procedure "automatic format" skipped data/media folder, only delete other folders. "Wiping data without wiping data/media ..."
To delete data partition completly:
1. Go to Wipe menu
2. Wipe Data
3. Yes (all data, audio, video, etc deleted)
4. Go to Restore menu
5. Restore Data partition
Restore completed without error!

---

samarium said:
I had this problem on a Redmi Note 3 Pro/Qualcomm recently. It seems to me to be loosely correlated to the /data backup size, and seems to manifest just below 4GB, looks suspiciously like some 32bit counter/offset ... but .... in my case this seems to happen only in the first tar/win file which much < 2GB uncompressed anyway.
Interestingly, not all tar binaries are equal. The binary from LineageOS 14.1 crashes reading win000 files often if I try to test this from a terminal session when the phone is booted normally, however tar from TWRP does work and doesn't crash. Using tar from ubuntu 18.04 I can see all the files, however there are numerous reports of
Code:
tar: Malformed extended header: missing equal sign
Maybe this tar crash is also what is happening for the TWRP GUI using it's internal tar? Although this seems to be crashing when the recovery is nearing 4GB, however my tar crash seems to happen on the first segmented win000 file? Maybe it is related in some way to pigz which seems to be used by the TWRP GUI to compress/uncompress and it does multi-threading. I haven't looked at TWRP code.
I tried TWRP 3.1.1-0, and downloaded the latest 3.2.3-0 from twrp.me. Both failed in the same way.
I inspected some of the backups I had, finding decrypted /data space usage less /data/media:
Code:
$ ls -1
2018-09-06--12-41-18_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
2018-11-10--11-08-53_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
2019-01-10--10-01-22_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
2019-01-26--16-04-54_lineage_kenzo-userdebug_7.1.2_NJH47F_02865f
$ grep Data.backup.size */recovery.log|uniq|sed 's/\// /;s/--[^ ]* / /;s/:/ /'
2018-09-06 recovery.log I:Data backup size is 3464MB, free: 14062MB.
2018-09-06 recovery.log I:Data backup size is 3464MB, free: 11552MB.
2018-11-10 recovery.log I:Data backup size is 4622MB, free: 11065MB.
2018-11-10 recovery.log I:Data backup size is 4622MB, free: 7576MB.
2019-01-10 recovery.log I:Data backup size is 4041MB, free: 11284MB.
2019-01-10 recovery.log I:Data backup size is 4041MB, free: 8192MB.
2019-01-26 recovery.log I:Data backup size is 652MB, free: 24414MB.
$
I could restore 2018-09-06 and 2019-01-26 using TWRP GUI while the other 2 failed with error=255. Of the backups I could restore with the TWRP GUI, both backups are easily < 4GB. 2019-01-10 is just below, still no idea if it is related to 4GB. In each case I formatted /data before hand, so /data/media was empty, so there was 24GB of free space, so there was always at least 2 times, sometimes 5 times, the actual space required for the recovery available.
Irrespective of the actual failure mode, I was able to restore the other backups manually.
Interestingly when I examine the .win and .win000 files with
Code:
tar tvf file | sed 5q
I find that the single .win file backups need to be restored while current directory is /data whereas the multipart backups need to be restored while current directory is /.
Manual restore process from TWRP recovery shell :
Backup everything to storage external the phone, and then backup the backup.
Wipe /data. I prefer to format /data while also wipes /data/media = /sdcard as this guarantees /data is clean, however if your backups are stored in /sdcard/TWRP then you are going to need to either not format /data or restore them from your PC, or not store them in /sdcard/TWRP and store them on an external sdcard or external USB OTG drive. Actual location may vary depending on TWRP build. Determine the b= lines below appropriately.
Connect using adb shell. You could type this in using the TWRP Advanced Terminal, but error prone.
Make sure you have enough free space on /data to do the restore. You should have, but this is the manual process so cross check.
Restore the .win0?? files with tar.
Code:
... # PS1="# " # optional
# cd /location/TWRP/BACKUPS/serialnumber/2019-01-10* # location: sdcard sdcard1 usb-otg
# pwd # verify backup directory
/location/TWRP/BACKUPS/.../2019-01-10--10-01-22_...
# b=$(pwd) # remeber backup folder location
# ls -l data.*.win000 # verify backup file exists
-rw-rw---- 1 root sdcard_rw 1109681843 2019-01-26 11:02 data.ext4.win000
# for m in data*md5; do md5sum -c $m; done # verify md5 checksums of each tar/win file.
data.ext4.win000: OK
data.ext4.win001: OK
data.ext4.win002: OK
# cd /
# for w in $b/data*win0??; do echo recover $w; tar xpvf $w > $w.rec; echo; done
recover /.../data...win000
tar: removing leading '/' from member names
recover /.../data...win001
tar: removing leading '/' from member names
recover /.../data...win002
tar: removing leading '/' from member names
# cd $b
# wc -l data*rec # verify recovery of reasonable number of files
29346 data.ext4.win000.rec
343 data.ext4.win001.rec
1831 data.ext4.win002.rec
31520 total
# df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/dm-0 25667344 15051056 10599904 59% /data
#
Reboot
Click to expand...
Click to collapse
Did your instructions. When running the recover command, I have some errors: Cannot remove file: Is a directory / Or "File exists"
When I am finished, I run "df" and 30% of disk is used which seems ok. But when I check /sdcard folder, nothing appears there... It is like it was recovered but somewhere else.
Do you have any clue?

---

Sorry,
today for the first time i must restore a nandroid backup (recovery 3.2.1.2) in my xiaomi mi a1: i meet the exact error of this thread, "extractTarFork process ended with ERROR 255".
How can i restore all my backup without problem?
tnx