Has anyone encountered error 255 in TWRP? I've just had to reflash the whole rom, because it wouldn't let me restore my nandroid backup. Restoring just stops at 96% with an error: 'createTarFork() process ended with ERROR=255'. It seems to happen only in some backups, because my older nandroid restores just fine. Do you know how to fix it, or at least prevent it from affecting backups?
Related
I just booted into recovery to try and do a full nandroid backup of current miui system and then restore my checkrom backup.
After it completed the backup it finished with the message 'error generating md5 checksum' (or something to that effect). I wasn't too worried but when i tried to restore my checkrom backup it said 'md5 mismatch' (or whatever) and did not restore.
Should i be worried about this and is there anything i can do?
Thanks
The patch attached to my post works with older builds of Galnet Miui that had this problem. I guess it would probably work with other Miui variants. Tho I seriously doubt it will do any harm if you flash it, obviously if you do, you do so at your own risk
Flash it in CWRecovery, reboot into recovery and you should be able to run your backup fine.
the problem is with a missing nandroid-md5.sh script in the recovery image...
Getting below error while restoring nandroid backup...
extracttarfork() process ended with error=255
Any idea how this could be fixed?
Got a Note 4x Mido with twrp 3.1.1-0. Did a full backup, checked every box, and transferred it over to my laptop. Tried some custom roms and wanted to go back to my previous backed up rom. Did a wipe and transferred the backup back to my phone but when I tried to restore it EFS and Firmware were causing error, everything else worked fine, booted up the phone, no wifi, bluetooth, imei gone, provably hard to fix... Tried wiping in all kinds of ways but the EFS and firmware just don't want to be restored.
EFS throws:
Unable to find file system (first period).
Unknown restore method for '/efs2'
EDIT: Tried some different versions of twrp and it worked (only EFS)
Firmware throws:
extractTarFork() process ended with ERROR: 255
Thanks in advance for the help
Try with this procedure and let us know if it worked for you:
https://forum.xda-developers.com/showpost.php?p=73770600&postcount=12
Hello Everybody,
first of all thanks for reading my thread.
I have a problem...tried to flash a custom kernel 2 days ago, and it went wrong. So I had to flash official fw again to come back to Xiaomi.eu then.
Before I tried to flash the kernel, I made a backup with TWRP.
My problem now is, every time I try to restore this backup, TWRP gives me an ERROR 255 when it tries to restore data partition.
Error message says something with "error create fork" or similar.
Have tried different things, also for example to wipe data before, or to format data, but nothing helps.
Device is decrypted on start of TWRP. So that is not the problem, I guess.
Anyone eventually has a clue/a tipp what I can try or what may be the problem?
Or isn't LRTWRP generally not able to restore backups?
Would be grateful for any help... ?
I am on EU Nord 2 and was as firmware .A17 before trying out custom roms. I want to return to stock and I did make a nandroid backup with TWRP. When I try to restore the nandroid backup, it fails with: "extractTarFork() process ended with ERROR: 255" Does anyone know how to get around that?
Alternatively, how can I restore my phone to stock OOS?
You will get this error only when twrp tries to restore data partation so before restorating untick data partation and restore alll the other partation and it's done
jadajada said:
I am on EU Nord 2 and was as firmware .A17 before trying out custom roms. I want to return to stock and I did make a nandroid backup with TWRP. When I try to restore the nandroid backup, it fails with: "extractTarFork() process ended with ERROR: 255" Does anyone know how to get around that?
Alternatively, how can I restore my phone to stock OOS?
Click to expand...
Click to collapse
Try to flash before oxygen same version of nandroid into both slots, format data then boot to system without configuration, now return into twrp and restore nandroid.
There's no A/B slots on the Nord 2
Yes i'm new on Nord 2 and have 7 pro that is A/B partitions.