TWRP Failed to Backup - G4 Q&A, Help & Troubleshooting

I need your help Guys, I am unable to create Nandroid backup from TWRP. I always get error as below;
E: createTarFork( ) process ended with ERROR=255
I tried to create backup with compression and even on SD Card but failed
My phone has 6.0MM (Android HD Now 8.0 http://forum.androidnow.pl/13118-7-hd-8-0-aroma-mm-h815-v20a-22-11-2015-twrp-unlock-bootloader.html) on H815 with latest TWRP

Can Anyone reply me please?

Hello, in recent days also I have the same error during backup by TWRP. I have found that it is because of the partition "system." For if it exclude backup ends well. You have found the solution to this problem?

Related

[Q] Nandroid error - Can't backup

ok guys I'm getting an error and I'm not sure how to fix it.
When I try to make a nandroid backup (through recovery or ROM manager) it starts ok, backs up boot image, backs up recovery image, backs up system and data, but when it starts to backup .android_secure on the sd card I get the error...
Error while making a backup image of /sdcard/.android_secure!
What's going wrong? I've tried rebooting a few times, tried to do a backup about five times, but I always get this error.
Any help much appreciated.
Check recovery.log I think there's an option "move log to SD" in advanced or something.
It should tell you a little more.
Sent from my HTC Desire using XDA App

[Q] data is not able to be mounted

please help!
for some reason, I can not flash or restore anything. I can get into TWRP (2.7.0.2), but when I try to install or restore, the phone errors, stating unable to mount /data. Can I do something from ADB to help this? so I may be able to get something flashed and use the phone?
zosopage said:
please help!
for some reason, I can not flash or restore anything. I can get into TWRP (2.7.0.2), but when I try to install or restore, the phone errors, stating unable to mount /data. Can I do something from ADB to help this? so I may be able to get something flashed and use the phone?
Click to expand...
Click to collapse
To add
verizon M8
twrp 2.7.0.2 (for the M8)
I have tried sideloading, etc.... anyone have any suggestions? are ROMS that use aroma ok to sideload?
when it goes into HBOOT, I see a quick green message stating something about no image...
I have been able to mount system, cache data and micro sd card
when I try to restore from a backup, it states failed when restoring data.
Not sure if total mobile protection will cover this...

TWRP Restore Error 255

Team,
I just recently bought a Google Pixel and was attempting to transfer my contacts and messages and stuff from my HTC One M8 to my Google Pixel. However, my HTC One M8 was still on KitKat (4.4.2) and would not work with the transfer tool. So then I said let me take a TWRP backup of my phone before i start attempting to update it.
I attempted to download a rom to flash via TWRP but it did not work so I naturally tried to restore back to the TWRP backup I took.
Except now everytime I try to restore the backup I took all I get is extractTarFork() process ended with ERROR: 255
I have attempted to google all day with no luck.
Anyone dealt with this and have resolved it?
Thanks!
bef349 said:
Team,
I just recently bought a Google Pixel and was attempting to transfer my contacts and messages and stuff from my HTC One M8 to my Google Pixel. However, my HTC One M8 was still on KitKat (4.4.2) and would not work with the transfer tool. So then I said let me take a TWRP backup of my phone before i start attempting to update it.
I attempted to download a rom to flash via TWRP but it did not work so I naturally tried to restore back to the TWRP backup I took.
Except now everytime I try to restore the backup I took all I get is extractTarFork() process ended with ERROR: 255
I have attempted to google all day with no luck.
Anyone dealt with this and have resolved it?
Thanks!
Click to expand...
Click to collapse
Did you try updating TWRP? I had something like this happen a few years ago with my S3 and updating my recovery fixed it.
xunholyx said:
Did you try updating TWRP? I had something like this happen a few years ago with my S3 and updating my recovery fixed it.
Click to expand...
Click to collapse
yep, I had updated to twrp 3.0.2.0...still no luck
there has to be a way to fix this
so now even more weird. I downloaded Titanium Backup to try and extract from my TWRP backup, and nothing is there!
how the f is that possible!? does this mean my data is forever gone?
NoCall log, you should backup your calls with CALL LOG BACKUP & RESTORE apk from play store.Messages,you should backup with SMS BACKUP AND RESTORE apk from market(witch also can make a backup of all your sms/mms & call log!!!),so it's an one app for all.Both app make folders on your internal/sd memory that contain files selected by name and date,and you can just transfer this folders from M8 to Pixel and download those apps from playstore on your new Pixel phone,and restore calls/sms..About Titanium restore,isn't M8 ARM phone and Pixel is ARM64(or x86,I'm not sure)?so you can't restore those apps in TB cuz they're different versions with diferent screen DPI,and I suppose they won't work or TB gives you error cuz of that.You can only restore data from TB ,and it's very probable that some of those "restore' s" will give you problem due thing I sad in upper text and also cuz of big difference in Android versions(4.4>7.0+).
I hope you understand what I try to say,English is not my language,and I'm just trying to help you.I didn't by Pixel yet,I plan to,and this is what I would use in mind doing those transfers and restore procedure.
I had LGG4(ARM64),I transfered all my TB folder from M8(ARM),and when restoring ARM>ARM64 ,many of them force closed or mail function.But ONLY data restore allways worked on already installed app.
And about your error and problems on m8 with TWRP,yes try with some other and maybe older versions of TWRP(if m8 is on 4.4.4 ,then maybe latest recoveryes have problem to do backup and restore.In the end,try to flash stock RUU for your version on it,then TWRP+superuser,to try to fix all.BUT BEFORE Ruu Move all your TB and other data from internal memory/sd to computer or some other external drive-in case you lost or overwrite your data on phone.
Maybe someone will point you in right direction,maybe someone already had that problem.
Sent from my HTC One M8 [6.0 Gpe]
shawek said:
NoCall log, you should backup your calls with CALL LOG BACKUP & RESTORE apk from play store.Messages,you should backup with SMS BACKUP AND RESTORE apk from market(witch also can make a backup of all your sms/mms & call log!!!),so it's an one app for all.Both app make folders on your internal/sd memory that contain files selected by name and date,and you can just transfer this folders from M8 to Pixel and download those apps from playstore on your new Pixel phone,and restore calls/sms..About Titanium restore,isn't M8 ARM phone and Pixel is ARM64(or x86,I'm not sure)?so you can't restore those apps in TB cuz they're different versions with diferent screen DPI,and I suppose they won't work or TB gives you error cuz of that.You can only restore data from TB ,and it's very probable that some of those "restore' s" will give you problem due thing I sad in upper text and also cuz of big difference in Android versions(4.4>7.0+).
I hope you understand what I try to say,English is not my language,and I'm just trying to help you.I didn't by Pixel yet,I plan to,and this is what I would use in mind doing those transfers and restore procedure.
I had LGG4(ARM64),I transfered all my TB folder from M8(ARM),and when restoring ARM>ARM64 ,many of them force closed or mail function.But ONLY data restore allways worked on already installed app.
And about your error and problems on m8 with TWRP,yes try with some other and maybe older versions of TWRP(if m8 is on 4.4.4 ,then maybe latest recoveryes have problem to do backup and restore.In the end,try to flash stock RUU for your version on it,then TWRP+superuser,to try to fix all.BUT BEFORE Ruu Move all your TB and other data from internal memory/sd to computer or some other external drive-in case you lost or overwrite your data on phone.
Maybe someone will point you in right direction,maybe someone already had that problem.
Sent from my HTC One M8 [6.0 Gpe]
Click to expand...
Click to collapse
Thank you for your reply; I wish I had asked before attempting.
Here is what I see from the bootloader screen in case it helps --
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.18.0.0000
RADIO-1.09.20.0702
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.21.605.2
eMMC-boot 2048MB
Aug 7 2014,20:26:27.26992
--
I took the full backup of my M8 using some version like TWRP v2.8.0.? I tried to restore the backup and it kept throwing me that error. So I said, lets try to flash the latest version of TWRP and that is what I did. I attempted restoring through the latest TWRP but still I get the same error. I have also tried to extract the backup using Cygwin with no luck. Titanium Backup also does not see it as a valid backup.
I am still on Android 4.4.2 (I had a backup from 2014 I was able to restore to in the meantime and is rooted).
The only place the data from my M8 is, is in the TWRP backup file which refuses to restore. All data on the phone was formatted and overwritten as I tried to flash a newer rom on it with no success. I have not tried to restore the data to my pixel and will not do so. All I need to do is restore the M8 backup to the M8 and try the methods you listed but I cannot get past this TWRP error. Or, get the backup to extract properly without throwing errors so that I can get the appropriate .db files from within
I am sure there is a fix involved with TWRP or is my wishful thinking sore out of luck?
I had this problem and it took me two days to resolve it. I had a good backup and I know it was good because I had used it several times and it worked. But then after doing some system installs I got the error 255. I tried several things to fix it and nothing worked and I really did not want to lose my backup. What did work for me was to use TWRP wipe function to FORMAT the phone. Wiping or factory reset did not work. I lost the contents of my internal SD card but I was able to transfer most to my external SD card. You could also connect the phone with a cable to a computer and use the pull command in ADB to backup the contents f the internal SD card. Given the choice between losing the SD card and the data files I come to lose some of the SD card. Anyway, a FORMAT worked when nothing else did. I read that this error is caused by a lack of space. When I checked the log it seemed that the restore was failing with a particular file which misled me to thinking I had to remove the corrupt file, but since after the format I was able to restore without any problem, it would seem that there was no corrupt data. Hope this helps someone.

TWRP Errors Trying to do a Backup

I'm trying to do a nandroid backup in TWRP and get the following errors:
E:backup file : 'data/media/0/TWRP/Backups/LGUSUE869a98D/2018-10-31--18-10-37_Lineage_h812-usu=userdebug_810_OPM617101903/system.ext4.win000' not found!
Backup failed. Cleaning backup folder.
Eror upening: 'data/media/0/TWRP/Backups/LGUSUE869a98D/2018-10-31--18-10-37_Lineage_h812-usu=userdebug_810_OPM617101903
I have backed up several times before, but all of a sudden I have this problem.
I have attached a portion of the recovery log.
Help is appreciated.
jjcdennis said:
I'm trying to do a nandroid backup in TWRP and get the following errors:
E:backup file : 'data/media/0/TWRP/Backups/LGUSUE869a98D/2018-10-31--18-10-37_Lineage_h812-usu=userdebug_810_OPM617101903/system.ext4.win000' not found!
Backup failed. Cleaning backup folder.
Eror upening: 'data/media/0/TWRP/Backups/LGUSUE869a98D/2018-10-31--18-10-37_Lineage_h812-usu=userdebug_810_OPM617101903
I have backed up several times before, but all of a sudden I have this problem.
I have attached a portion of the recovery log.
Help is appreciated.
Click to expand...
Click to collapse
Sorry folks, I fixed this myself. I reinstalled TWRP and it backed up successfully.
Its curious that I was able to backup to an external SD card prior to reinstalling TWRP.
jjcdennis said:
Sorry folks, I fixed this myself. I reinstalled TWRP and it backed up successfully.
Its curious that I was able to backup to an external SD card prior to reinstalling TWRP.
Click to expand...
Click to collapse
Ok great next time:
1) best is to use the official TWRP support thread
2) attach the full recovery log not only a bit of it and use http://bpaste.net and a long time period to provide it
Besides that I'm glad it works for you now.
Sent from my LG-H815 using XDA Labs
steadfasterX, FYI. I had the error happen again and it was caused by the same thing the original error was caused by. I had been creating multiple nandroid backups and wanted to clear them out and get the latest one ready for a recovery if needed. So I deleted them via Windows 10 Explorer. When I went back in to create the new nandroid backup I got the TWRP error. I also tried pasting a nandroid recovery from an external SD card to see if this would resolve the error, but it did not. This happened twice. Reinstalling your latest TWRP image fixed the problem.

TWRP firmware restore error 255

Hi, I tried to restore a full image with TWRP including firmware. Everything went smooth, only with the firmware I got the message "extractTarFork Process ended with error 255." My system (Resurrection 7.02) boots, but finger reader, Wi-Fi and Bluetooth don't work. What can I do?
tempe222 said:
Hi, I tried to restore a full image with TWRP including firmware. Everything went smooth, only with the firmware I got the message "extractTarFork Process ended with error 255." My system (Resurrection 7.02) boots, but finger reader, Wi-Fi and Bluetooth don't work. What can I do?
Click to expand...
Click to collapse
I solved like this:
copied twrp backup onto computer, used winrar to unpack firmware.vfat.win -> firmware.vfat -> image folder
phone booted into TWRP, enabled MTP, copied image folder to sdcard
mount system and firmware partition in TWRP and copy image folder from sdcard to /firmware folder using file manager from TWRP
I recommend to backup and to restore EFS partition also when sim problem after flashing ROM. I had this problem flashing crDroid.
Keep in a safe place outside your phone persist/modem/firmware/EFS backups for the future.
I worked for a week only to get out from a bootloop generated because "extractTarFork Process ended with error 255." on firmware partition.
Rebooted and everything was fine.
I have now crDroid 5.3 working on a2 lite.

Categories

Resources