Error 255 when restoring a TWRP backup - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Hello,
when I try to restore my TWRP backup of Lineage 17 on my Samsung Galaxy A5 2016 I run into the
extractTarFork() process ended with ERROR: 255​issue, and have tried several methods which I have found when googling for fixes, but none has worked so far.
This is what I've tried:
- unmount the data partition before restoring backup
- just restore system, data and boot, tick off the others
- wiped data/system/cache, flashed rom+gapps, flashed backup with all sections activated (radio, system, data,...)
- wiped data/system/cache, flashed rom+gapps, flashed backup with only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, wiped dalvik/cache after, flashed backup w/ only restoring system, data+boot
- wiped data/system/cache, flashed rom+gapps, reboot, clicking next on every configuration screen, reboot to recovery, restore only data from backup
The issue seems to always occur at the same point in the process, in the progress bar its either at ca 45% or 58%, depending on if only data or everything is supposed to be restored. Restoring everything _BUT_ the data partition works, but the stuff I need to access is the data.
Kind regards

Hello,
I managed to fully restore the backup follwing this guide
Now my phone boots up to the point right after the Lineage logo is shown, where it says "starting the phone" and would probably ask for sim pin if I had a sim card in it. Then it reboots and does the whole thing again.
Does anyone have an idea how to fix this?
Kind regards

Related

Trouble booting device

I tried restoring a nandroid backup on my phone and have been having trouble ever since. Upon restoring my nandroid backup, I restarted my phone but I couldn't get past the Samsung Splash Screen. So I started troubleshooting:
1) I restarted my phone, booted into recovery (TWRP), and wiped Dalvik Cache, System, Data, Internal Storage and Cache. I then tried restoring my nandroid backup again. However, upon rebooting the device, I still couldn't get past the splash screen.
2) I installed Heimdall for Mac (like Odin) and flashed the latest TWRP recovery.img (openrecovery-twrp-2.6.3.1-jfltexx.tar). I tried to restore the nandroid again, but I still couldn't get past the splash screen.
3) I tried doing a fresh install of cm10.2 stable and still nothing.
Please, any help or direction would be awesome

Can't restore stock rom backup from TWRP (SM-G900F)

Hello,
before I played around with getting root and flashing custom roms, I backup everything in Samsung Smart Switch.
After getting root and install TWRP, I backup the whole system (except the recovery partition) to the external sd-card from TWRP.
Now - after getting some experience with custom roms - I will go back to the stock rom from my TWRP-Backup. Set everything to factory default, wipe cache and dalvik and press restore. Select my backup... swipe to flash... everything seems ok. After reboot - no bootloop - a thousands of alert-messages pops up "blabla-app stopped"... Then appears only a black screen.
How can i restore my backup from TWRP? Or is there a stock-rom, so i can backup from smart switch? My System is a LRX21T.G900FXXU1BOJ1
Thanks alot!
Try clearing the caches from recovery and boot again
If it fails, try wiping everything again, then restore all partitions except DATA
See if it boots
If it boots - either reinstall apps etc manually, or use TiBu to restore the DATA partition
I've got it!
I flashed a stock rom with odin and restore with smart switch. Some settings are missing, but i think 90% is restored
Nice job

Help with TWRP Restore !

I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it

Nandroid Backup Fails with extractTarFork() error

Long story short, I tried to install MultiROM on my Nexus 6P, and it failed. So I tried to restore my backup using TWRP 3.0.2.0, and it keeps failing at exactly 7800MB with the error E:extractTarFork() process ended with ERROR=255. I have seen posts talking about checking the log when this happens, but I'm not sure exactly how to do that.
What exactly do I need to do to restore my backup?
I guess I should add some detail. I first tried booting to recovery and restoring the backup. The phone rebooted into a boot loop part of the way through the restore process every time I tried that. Then, I tried flashing the phone completely back to the stock image, and then restoring. I got the error 255 above. Then, I tried flashing back to stock completely, wiping Dalvik/cache, and restoring the backup. I still get the same error message. I tried restoring everything except userdata, and the phone reboots part of the way through the restore.
I could easily reroot, reinstall Xposed, and reflash TWRP if for some reason my system backup partition is corrupted. However, I don't want to lose my data partition at all. That was the whole reason I made the backup in the first place.

Recovery loop after TWRP Restore LineageOS 17.1

Hello there,
I had had LOS17.1 installed on my SGN3. Made a TWRP 3.4.0-1 backup, flashed a stock ROM for a few days and then went for restoring LOS17 again. But restoration wasn't successful.
First "Cannot restore Modem - mounted read only" log show up during restoration. Checking Modem in Mount did not help. So I unchecked modem, which "solved" the issue.
After restore completed, device rebooted but got stuck in what I would call a recovery loop. Black screen -> TWRP splashscreen -> black screen (repeat indefinitely). It can be broken up by entering Recovery (or Download) by appropriate hardware key combo.
But the issue is I cannot get into my system. Installing LOS17 from scratch works but I would like the data.
I tried multiple TWRP versions and fix_rootfs_label.zip I have found here on XDA with no success. Installing fresh LOS17 works and restoring only "data" lets me boot, but the system is not usable (but still trying).
Restoring more than "data" always ended up in the recovery loop.
What was interesting is that when I tried to install GApps to the restored backup, it threw an error saying that this GApps package is for Android 10, while Android 7 (SDK 25) was detected on the system.
Any help?
Thank you!
Did you flash Gapps or no? If yes try nano if no i can't help

Categories

Resources