Error restoring backup "extractTarFork() process ended with ERROR: 255" | Error 255 In TWRP Recovery
Vložit
- čas přidán 10. 01. 2020
- Error restoring backup "extractTarFork() process ended with ERROR: 255" | Error 255 In TWRP Recovery. How To Fix Error 255 In TWRP Recovery, How to fix TWRP recovery ERROR Restore backup !! Easy, How to Restore twrp backup without any errors plus the best way to take twrp backup so that you won't face any errors in the future while restoring the twrp backup in your android mobile...
How to recover your lost data , try Recoverit: bit.ly/2IUzxEM
NOTE:- "Please, kindly subscribe to this channel as I am providing you quality content."
createTarFork() process ended with ERROR: 255:-
• Error creating backup ...
NOTE:- Always have a copy of your internal storage data so that you can paste it back if something goes wrong.
For Python Tips & Tricks Subscribe to "PyProTricks":-
/ pyprotricks
Save Files from any URL to Google Drive with Resume Support:-
• Video
Download any Size Torrent into Google Drive with Resume Support:-
• Video
To Mount Multiple Google Drives:-
• Mount Multiple Drives ...
For Google Drive to Google Drive Transfer:-
• Video
For Shared Drive to Shared Drive Transfer:-
• Video
For Google Drive to Shared Drive Transfer:-
• Video
Unmount Google Drive in Google Colab:-
• Unmount Drive in Googl...
Bypass any url shortner link fast:-
• Video
New video every week.
Pls LIKE, SHARE & SUBSCRIBE to support BoostUpStation...
I was trying to flash evolution x but something went wrong. Every time I tried to restore back up but the error appeared, and every time I flashed a rom, the phone always came back to recovery. thank you man, this video saved my phone :)
That's a good news bro
Hope you did subscribed the channel for sure :)
Hey bro, just want to say you many thanks. Update of Magisk Canary broken my installation, it was always in bootloop, and when i tried to restore the backup,
this shitty error alawys came. I followed your steps, the backup restored and the phone booted up. I think i would not manage to restore it without your video. You saved me, thank you a lot!
Thank you very much, I had this problem and I had already given up using Orange Fox for backups, I was only using it to format, change ROMs or flash things... the Restore never worked, but now I managed to make it work! Everything perfect! In my case I restored the MIUI 12 Andorid 11, I didn't have to do the second step of re-flash the Gaaps. THANK YOU FOR THE EXPLANATION!
Muito obrigado, estava com esse problema e já tinha desistido de usar o Orange Fox para backups, eu estava usando ele somente pra formatar, trocar de ROMs ou flashear coisas... a Restauração nunca funcionado, mas agora consegui fazer funcionar! Tudo perfeito! No Meu caso restaurei a MIUI 12 Andorid 11, não precisei fazer a segunda etapa de re-flash os Gaaps. OBRIGADO PELA EXPLICAÇÃO!
Error' 255 my solusion
1. Restore but don't cechlist data..
2. Done not error'.
3. Back to twrp and restore again your Rom.. and done.. fix..
Brilliant and Perfect instruction my rom was a debloated Stock Rom so the Gapps installation was not need as it is only requuired for Roms which don't include Gapps. I was able to Restore the Rom without a single issue even after nearly 4 years it still works, Keep up the Good Work👍
Thanks Man, every time I watch this video of yours to get the restore done.
Came on your video again for 5th time, because I always forget how to do this whenever I need to do this. Thanks.
In my case I've had a backup of Android 9, wiped the Android 10 installation and faced the 255 error upon trying to restore back to Android 9. Device is a General Mobile Android One (analogue of Wilefox Swift Crackling). Rom was the latter one's. Anyway, your video helped me realize the version difference but I didn't do the entire steps. Just Wiped everything, Installed Rom and Magisk. Even No gapps. After installation of the backed up version., I didn't even exit twrp, just wiped again and restored the backep without problems. :) Thanks anyway.
I really appreciate your solution! Finally I managed to restore my data backup, that was a miracle, cheers! :)
It would be awesome if you subscribe :)
and thanks for the compliment :)
@@BoostUpStation help when i went to install the rom.zip ,appears : updater process ended with error 1 help? before gave error 255 when restoring backup
THAAAAAANK YOOOOOUUUU SOOOOO MUUUUCHHH MAN!!!
This video saved my phone!
You helped me to successfully restore my backup. It worked.
Thanks for saving us man! More subs!
Fantástico, irmão! Você me ajudou a finalmente conseguir restaurar backup no meu oneplus 6T com a maravilhosa rom e/OS 14 baseada no android 9 (a unica 100% funcional sem nenhum app, recurso, bloatware etc da google, portanto uma maravilha pra quem prioriza a privacidade de dados)... Parabens! Se soubesse como, te daria um superlike
My Moto G7+ was failing at the exact same place in the restore as yours did in the video, right after restoring data(excl.storage.) I was able to follow all of your directions except for the last one in file manager. When I went to /data/media/0, there was no android folder, just 34 20+ character folders. When I select my partitions to restore, it lists boot, data(excl. storage), system, and vendor. If I go into backup, the boot and system partitions have 64 and 2334mb respectively, and data(excl. storage) has 0mb.? Also, when I go into mount, the selected partitions are data, system (not read only), persist, persist2, and micro sd card. Should I deselect data(excl s) since it seems to be empty? Should both persist partitions be included? And select storage under mount is micro sd card, should that be internal storage? OK in restore, I deselected the data(ex st) and the restore completed but when i tried to reboot, I get 'no OS installed'. When it boots, it just alternates between the android splash screen and the unlocked warning and in windows explorer it shows micro SD as having 5gb free and storage 10001 (formally internal storage) as being totally full. I'm so screwed, but I hope that this could help someone. BTW, excellent video.
the problem is that your internal storage is encrypted because its showing those 20+ random character folders which is a sign of your mobile's encryption scheme fucked up (it happens when you install a rom which has earlier security patches than the current installed rom)
try to reboot to recovery and see if you have the original folders in the internal storage, if yes then copy them asap into pc via usb cable
and
the only fix to boot into system is to format your data partition, using wipe and click on format data
and then restore your data partition as i showed in the video
and from now on always remove your lockscreen password and fingerprints before doing any recovery ops
also backup your data
and thanks for subscribing the channel :)
and in a couple of days, i'll be sharing a self created script on my channel for downloading all the branches of a github repo in just one click, so stay tuned
@@BoostUpStation Thanks man, I thought that I was boned when Data showed 0 mb. I never heard anyone tell me to remove security before recovery., of course the phone was already not booting when I started so I don't know how to turn it off within twrp. Looking forward to new posts.
Bro, when I went into internal storage, the contents were empty but via TWRP I couldn't detect the file, it was just empty when I entered internal storage file is dissapear, then moved to PBRP recovery, the internal storage file was detected and everything was there, bro?
i even didnt do the whole things, i tried to restore without installing the rom in 2:22 and it worked!!!
I was getting this error lately. I did what you said to do in your video. Reinstalled the Rom and TWRP, rebooted device, skipped thorough all the setup. Booted back into TWRP all my files are now encrypted but I have no screen lock enabled. All my files are also encrypted when I go into a file manager APK. On phone. Any ideas on how to fix this. Phone is a Google pixel XL no SD card.
Sorry to inform you brother but there're only some workaround you are left with, read along
the error you are facing is because of installing older security patched rom over the newer security patched roms, for example- installing january security patch over the rom with feb security patch.
I also had this problem in the past, and i have to format my mobile, and lose all my data
What we gonna do now is rebuilt the encryption by using twrp command or installing other recoveries or some other rom ( we will use the same rom too which you was installed before this prob) , to let the android know, that the internal storage requires password for decryption
One thing you can do is, search for any twrp, or other recovery which supports decryption, and try to see if it prompts for the password on twrp startup
Also try using some recovery which supports decryption, without password, like modded ones
Also try running the command in terminal of recovery:
twrp decrypt 'lockscreen-pass-without-quotes'
As soon as you get the things working, copy your whole internal storage in pc.
If after doing, all the above tactics, you get nothing, before formatting data, try installing the same rom which you had before this encryption problem, after trying that rom if no luck, try installing the latest security patched version of the same rom which you had earlier (if you don't have its latest updates, then try using some other rom of your device which has latest security patch different than the rom you had earlier in the mobile)
If still no luck, then the last option is to format :(
For safety, next time - remove your lockscreen protections before doing any rom related stuff, and do BACKUP DATA
I tried a lot of ways to get rid of the problem you are facing, but nothing got right, otherwise i would have uploaded a video regarding that, but i can upload a video to save you guys in the future though ( let me know if you want to help people not to do a mistake, I will upload a video with all info to save from future calamity)
yeah, man! it works! respect!
Thank you so much bro, im appreciate you! It works!!!!
thank you so much for the help. in my case there's no media folder just deleted all folders inside data folder. and installed the custom rom and restored the back up.
question: Is this the same when i decided to go back to stock rom? i will delete all data folder except media?
do you know a way of backing up presist partition? it isn't showing when i backup in twrp. I'm on realme X. They say it is really necessary to backup the persist partition. i tried mounting it on mount, it didn't showed while backing my rom.
@BoostUpStation when i went to install the rom,appears : updater process ended with error 1 help?
thanks brother u save me from total mess
Awesome!!! Works perfect for restoring Evolution X 4.1 on Mi 9T Pro/REDMI K20 Pro. Do you really need to install the GApps pico? Because Evolution X 4.1 comes already shipped with it. I did it anyhow and worked!!
Not required if you have them already in the rom BUT without gapps you wiil have problems running google play services.
& its BETTER to flash gapps
and thanks for subscribing the channel :)
redmi 7 there, got this error and followed the steps. rm -rf is the most important part, I followed many tutorials, but they don't worked because they omissed to check this option !
the data partition got restored successfully but got a bootloop on mi logo itself
what to do
THANK YOU!!!!!!! This worked for me.
nice bro.. work for my poco f1.. tq very much broo
Thank you bro .
Help custom rom install ha backup restore install par extrack tarfork() process ended with erros signal : 9 errow aha raha sar pless help karo
very thank you
Единственная рабочая инструкция. Всё работает как часы. А главное можно не бэкапить System. Смысл реально, если можно потом просто прошивку накатить и только дату воткнуть. Спасибо за идею
разве можно накатить Data на другую прошивку без ошибок?
@@yes_future он имел ввиду накатить data на ту, с которой она была забэкаплена
Tried Android S and now going back to A11, again i was forced to see ur video for backup process.
Very nice bro thnk you
yours welcome bro
hope you have subscribed the channel
Nice fixed thnxxxxx
Prerooted rom m stock rom backup ko restore krenge to phone automatically unroot ho jayega kya boc mere same 255 error aa rha tha restore krne pr
Very nice bro thnk youuuu
Bro I didn't found the '0' folder in media. What should I do, My system and vendor were wiped out. Please help me 😭😭😭😭😭 I couldn't use my phone 😭😭😔
I have a s7 edge where can I find the apps and ROM for it .? Please help me sir
thanks mister 🙏🙏🙏 work it
Thank you! Bro, how do I restore my stock recovery? Should I just place the stock recovery.img in the sd and install it in TWRP? Thanks in advance!
Take care about vbmeta.
just see how to flash stock recovery for device specific groups on telegram, or check xda pages for the same.
in general process is to just flash stock recovery.img via custom recovery or fastboot.
I dont have the recovery box in twrp to tick during backup does this matter
It doesn't matter
tick others shown in video
thank you man,this is work to my phone :v
Hello sir goodeve, last night i fucked up my phone ended up stuck at boot animation after i restore my back up then delete the lockscreensettings.db at data/system my problem is i tried to restore my backup then im facing this extracttar error then search on youtube and finally see this vid i tried it and do the same procedure but when im on the deleting folders proccess i face error again saying rm -rf "blah.blah.blah" process ended with error: 1 what should i do to fix this?
Hope you can help me sir.
Cant delete even a single file
Can i add you on fb so i can send a message properly sir?
Before doing anything, , make sure you copy all data from your internal storage to pc or external sdcard
Uncheck the option of ''mount partitions in read-only mode'' in the custom recovery
and then they will be deleted
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!
Thaaaaaaaaaaaaaank u Man
Big love ❤❤❤❤
if the eror 255 when restore system???
bro can i ask how to install the stock miui via twrp?
you can
make sure you flash twrp after that to retain twrp
I did follow your step. My phone has come back but my internal storage has been unknown name folder all of the storage. How do I fix it?
You should have had the backup of your internal storage data in some safe place
Now you can't turn back, its all gone
just goto recovery and format data, but before doing this, read comments
BoostUpStation Can I flash the rom again ? Will it turn back ? Because actually my data doesnt has any important file.
Please read all the comments of this video
i have already commented about this problem, which will tell you everything about how this prob occur and current ways to fix it
I was doing exactly what you described in your video but am still getting the error 255 when restoring data :(
I have a Moto G5 with Lineage OS 16 (so Android 9)
Any other ideas on how to fix this stupid error??
Are you restoring the same system version backup (i mean on the same name flashable zip for which you have the backup)
Try to restore the backup on same flashable ROM zip, by date and names matching the system, you flashing before the backup and the one you have data partition backup of.
Try it, subscribe if haven't :)
And reply if doesn't work
@@BoostUpStation thank you. I couldn't get it to work. So I now did a clean install for the update, copied my data manually and set up everything again
@@kleinerwolf3078 great
Hello Friend. Im from Brazil. My name is Márcio, and I'm having this 255 error (extrAct tar forks) when trying to restore a backup using twrp. I'll explain to you from the beginning. I have a Motorola Moto G2 XT 1078 thea, which when trying to downgrade was brick, and to save it I was given a recovery method by fast boot that made things worse. The guy gave me, by mistake, files for the moto G2 XT 1068 Titan, and mine is a moto G2 XT 1078 thea. I tried several times to flash the original stock ROM, but it gives several errors. In short, I managed to make it work by merging files from the ROMs of the 2 models and revived the device. But there were some bugs. I was able to install twrp and install a custom ROM, which is working perfectly. Now we have reached the point of the reason for my contact. I got a device of the same model as mine, same year, version and variant, I made a backup by twrp of the device that is in the original ROM to install in mine, but I'm having this error, extract tar forks 255. Do you have any idea how to proceed ? Thank you for your attention and I look forward to it. Marcio
First of all copy all your data to some safe place like pc, laptop
Also copy the twrp backup to pc or laptop plus in the memory card to restore using memory card in twrp
Now go to twrp on the device in which you want to restore the backup, plug in the memory card, and format everything except memory card
then reboot to recovery
and follow the procedure from video :)
And thanks for subscribing my channel :)
If you have the backup of system partition too, then no need to flash the rom
just direcrly restore all the partitions and reboot to system
But you have to format the device via twrp from twrp(go to wipe, format data, swipe to confirm,
Then goto wipe again, click on advanced, choose - cache, delvik cache, system)
and rebpot to recovery and restore the backup
@@BoostUpStation I thank you, I'll try, then I'll tell you. Thanks
@@BoostUpStationBut in this tutorial you install the ROM similar to the backup you're trying to restore, to eliminate the error when restoring it, right? But in my case the intention of restoring the backup of another device is to recover the original system, the procedure done by you seems to need to install the ROM for later the backup. Doing this tutorial without installing the ROM, will it work? I don't have the original stock ROM to install. Did you understand what I meant? Because as I told you before, I recovered the device by merging files from the ROMs of the Moto G2 models XT 1068 and XT 1078, which resurrected the device, but my model is the XT 1078 that stayed with the XT 1068 system, understand? I managed to backup another XT 1078, totally the same, only the serial number and IMEI are different, am I having this error for being a backup of a ROM with different IMEI? What do you think? Does the tutorial procedure work for my problem?
Just try to restore, only the data, system and boot partitions then
It won't give you the errors, because the imei no. Is not in the system, data, boot partitions
And if still you are facing the problem, get the fastboot img files of your device and flash them through fastboot
I may help you, if you give me your telegram no. (We will make it fast, bz i m busy nowadays)
This error was shown on TWRP as well as Orange fox which i am currently using while backing up DATA. Can you help.
try to do the backup after mounting all the partitions in both recoveries
also try to do the backup after unmounting all the partitions in both recoveries
also update your recoveries if available, and then try
Make sure you have enough space where you are storing the backup
@@BoostUpStation did but shows same issue
@@BoostUpStation shows
createTarFork error 255
send me the recovery.log file or the contents of that file here
the recovery.log file will be in the /tmp/ folder
connect you mobile to pc while in recovery and use the command
adb pull /tmp/recovery.log c:/
and send me the file from c drive
Is this a permanent solution or we have to do this every time we try to restore? Please reply.
Always have a copy of your internal storage for safety
this should not occur again, but if does, then only this is the way
TWRP team must include a fix their update
😎
How do I do this without wiping my current data??? I don't want to delete my data / apps
so i am considering that you have a previous twrp backup
copy your internal storage to pc of security
just take a titanium backup and a "Migrate Backup"(official app an playstore)
now restore twrp backup
now try to restore 1 by of 2 at a time (stop when 1 works for you)
please help me how to fix
i must install magisk ?
No need if you don't want.
agar sirf same rom install krne k bad restore krenge tab bhi ho jayega
Jis rom ka backup h, usi rom ko install karne ke baad restore ho jaayega
agar nahi hota to video ko follow kro
.
@Boostupstation This error 255 is occurring while I'm trying to restore my stock ROM data..I have an internal storage backup too which I can't restore..Kindly give me your telegram id... I tried your method last time but it encrypted my internal storage and after formating I was able to recover it. But still I can't restore my data and internal storage backup
Автор глупый, очистить почти всё как решение. Дизлайк.