Error creating backup "createTarFork() process ended with ERROR: 255" | Error 255 In TWRP Recovery

Sdílet
Vložit
  • čas přidán 29. 03. 2020
  • Error creating backup "createTarFork() process ended with ERROR: 255" | Error 255 In TWRP Recovery. How To Fix Error 255 In TWRP Recovery, How to fix TWRP recovery ERROR Creating backup !! Easy, How to Create 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...
    NOTE:- "Please, kindly subscribe to this channel as I am providing you quality content."
    NOTE:-
    Always have a copy of your internal storage to some safe place.
    If possible, use memory card to store the backup made from recovery.
    extractTarFork() process ended with ERROR: 255:-
    • Error restoring backup...
    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...
    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
    For Python Tips & Tricks Subscribe to "PyProTricks":-
    / @pyprotricks
    New video every week.
    Pls LIKE, SHARE & SUBSCRIBE to support BoostUpStation...

Komentáře • 49

  • @BoostUpStation
    @BoostUpStation  Před 4 lety +4

    NOTE:-
    Always have a copy of your internal storage to some safe place.
    If possible, use memory card to store the backup made from recovery.

  • @akdmkz9926
    @akdmkz9926 Před 3 lety +5

    there is no "addon.d" in my phone. already removed the fingerprint lock and even the pattern, I dont have parallel apps, I dont have multiple user profile. I dont know what is the cause of this.
    EDIT: I already sovled mine, looking this error at the bottom of the recovery log "Error adding file '/data/extm' to '/data/media/0/TWRP/BACKUPS/74fca3ed/2021-04-17--12-36-26/data.f2fs.win008'" I just deleted the folder 'extm' which is empty.

  • @patrikpandolfi
    @patrikpandolfi Před 4 lety +1

    Hello, i deleted system/addon.d/ but not solved, error 255 appeared again. So i read recomendations in commentaries below to search for error directory in log. Then i found system/app/Email, i deleted that using video's metod and the backup was succefully. Thanks a lot.

  • @nad1ax2
    @nad1ax2 Před 3 lety +2

    there's no addon.d file either in the /system directory or in /system_root/system, please help

  • @amogh894
    @amogh894 Před 4 lety +1

    Does this work even if you have a parallel apps 999 folder?

  • @asim5703
    @asim5703 Před 9 měsíci +1

    Just tick in TWRP back up - system or system image ( one of them & not both ) & make backup. Hope fully problem will be solved.

  • @whyme2272
    @whyme2272 Před 4 lety +2

    Awesome

  • @CarlosMassam
    @CarlosMassam Před 3 lety

    In my TWRP, there is nothing inside the "system_root" folder and in the "system" folder there is no file named addon.d

  • @schetan006
    @schetan006 Před 4 lety

    Is it not possible to restore encrypted system with lockscreen security? cause i got the same error and it left me no option except format data partition and install fresh rom.

    • @BoostUpStation
      @BoostUpStation  Před 4 lety

      Encrypted system means that the whole data partition, i.e. your internal storage is encrypted
      And to restore that, you need to create an image of your data partition, which will be of the size of data inside your internal storage when backup img is compressed
      and you also need to create an image of the system as well as the boot partitions
      So no one wants to take that headache
      the only option is to encrypt your backup with a password which comes when you take or restore backup via twrp.

    • @schetan006
      @schetan006 Před 4 lety

      @@BoostUpStation and as you demonstrate in above video after taking backup of Data, Boot & System then first install same rom separately and after that restore backup file is it what you mean?

    • @BoostUpStation
      @BoostUpStation  Před 4 lety +1

      Yup, but make sure you have a copy of internal storage data

  • @Mrpublicimagelimited
    @Mrpublicimagelimited Před 4 lety

    Remove your lockscreen password? Do you mean the optional lockscreen you can have on pattern unlock or number unlock? Can you please clarify this? I have always had the lockscreen switched off on my Galaxy S7 and I keep getting this error 255. :(

    • @BoostUpStation
      @BoostUpStation  Před 4 lety

      I mean remove the lockscreen security, all of them

    • @Mrpublicimagelimited
      @Mrpublicimagelimited Před 4 lety

      @@BoostUpStation And how do I remove the lockscreen security? Are you talking about going into settings\security and switching off lockscreen? Or something else? Please be a little more specific.

    • @BoostUpStation
      @BoostUpStation  Před 4 lety

      Ya u got it right

    • @Mrpublicimagelimited
      @Mrpublicimagelimited Před 4 lety

      @@BoostUpStation I've done that, and run through all of the usual fixes, e.g. checking there's only one user, checking for the 999 problem, etc etc. Nothing has worked.
      Also, is it possible getting this error damages one's SD card? I suspect it did in my case.

  • @hehehexpresso
    @hehehexpresso Před rokem

    My twrp doesn't have advance terminal. Is it ok to use the regular terminal?

  • @roderickgaray3667
    @roderickgaray3667 Před 2 lety

    hello friend, in mi twrp not have the addon file. I have the twrp 3.6

  • @peterway8878
    @peterway8878 Před 4 lety

    U turn off the light.great.

  • @tatenoyusha2550
    @tatenoyusha2550 Před 3 lety

    What if there is no addon.d in my folder but instead apex, is it similar?

    • @BoostUpStation
      @BoostUpStation  Před 3 lety +1

      What you can do is, copy the "apex" folder to sdcard for future,
      and now delete it from internal storage and do the process as done in video.
      Now if some error occurs related to "apex" folder, then copy it back to where it was in internal storage.

    • @tatenoyusha2550
      @tatenoyusha2550 Před 3 lety

      @@BoostUpStation Im having ERROR: 1, do you think this has something to do with arbitrary folders in my sdcard? Does it mean it is encrypted?

  • @hinasha8141
    @hinasha8141 Před 3 lety

    Bro pls help me
    I was flashing d8g kernal in my pocof1
    But its not worked
    So I decided to restoring backup
    But that also not working and I'm stack in the middle pls pls
    Pls help me
    I decided to flash corvus rom but its not working it shows error corvus .zip

  • @dilippatidar5627
    @dilippatidar5627 Před 4 lety

    I have same situation but I am not able to find addon.d folder anywhere in system or in system_root.
    please help

    • @BoostUpStation
      @BoostUpStation  Před 4 lety

      pls watch and follow the full video and see if still you ain't able to get it fixed

    • @dilippatidar5627
      @dilippatidar5627 Před 4 lety

      @@BoostUpStation I have done all steps you tell. this folder is not there

    • @BoostUpStation
      @BoostUpStation  Před 4 lety

      Hope you have proceeded further too without deleting that non existent folder
      like removing lockscreen security
      Enabling and disabling compression during backup(1 at a time)
      If possible try to update or change your recovery too
      Also try creating that folder addon.d(if doesn't work, reboot mobile, get back to rec. and now try with deleting that addon.d folder)
      And make sure enough space is there

    • @rsrvado1
      @rsrvado1 Před 4 lety

      @@BoostUpStation He hecho todo, paso por paso, desabilitando las opciones una por una y creando la carpeta addon.d, para luego eliminarla mediante Terminal, dando privilegios a SU y ejecutando la acción rm -rf /system_root/system/addon.d/
      Únicamente puedo hacer un BackUp si no meto en el respaldo data. Así, sin BackUp a data acaba correctamente el BackUp. ¿Por qué puede ocurrir esto? Gracias.
      NOTA: he de decir que estas acciones las he hecho en un Huawei Y7 TRT-LX1 (2017), mediante TWRP Recovery.
      I have done everything, step by step, disabling the options one by one and creating the addon.d folder, then deleting it through Terminal, giving SU privileges and executing the action rm -rf /system_root/system/addon.d/
      I can only do a BackUp if I don't put in the backup data. Thus, without BackUp to data, the BackUp ends correctly. Why can this happen? Thank you.
      NOTE: I have to say that I have done these actions on a Huawei Y7 TRT-LX1 (2017), using TWRP Recovery.

    • @BoostUpStation
      @BoostUpStation  Před 4 lety +1

      You need to look at /tmp/recovery.log while in recovery (adb pull it). Look in it for the last file that it tried to read before it gave the error. Your options are either delete that file or pull it then delete it. However, the file is corrupt in some way and the backup will never finish.
      Restoring an older nandroid(twrp backup to be specific) fixes this because it deletes the existing files and writes your nandroid back over them.
      you need to look at the recovery.log file and figure out whats wrong
      if you are not able to figure it out, upload the file link here
      If still you are not able to backup the data partition, then just install Migrate apk from playstore and take a backup of all the apps which you want with apps data
      this migrate app will create a recovery flashable zip
      then flash those recovery flashable zips via custom recovery after booting your freshly installed rom

  • @vladimirokovic296
    @vladimirokovic296 Před 4 lety

    Can we just delete that folder from root explorer?

    • @BoostUpStation
      @BoostUpStation  Před 4 lety

      Yes, you can
      but it may recreate itself after a reboot
      try deleting it from root explorer and see if its there after a reboot, else you need to do as in the video

  • @roderickgaray3667
    @roderickgaray3667 Před 2 lety

    Hello, i have this problem, but i don't see the video clearly... Can you make again this video? please. I want to install one custom rom, I have a redmi note 10.

    • @BoostUpStation
      @BoostUpStation  Před 2 lety

      right now i don't have the same scenario,
      try following along, try using subtitles.
      Download highest resolution video.
      Try to magnify the video in laptop or mobile to see what's in the video,

    • @roderickgaray3667
      @roderickgaray3667 Před 2 lety

      @@BoostUpStation ok thanks

  • @echosen121
    @echosen121 Před 4 lety

    I accidentally deleted the entire system folder. My path was system/system/addon.d/ and I went to check on the system files and there is nothing in there. Fonts, config all that was there before it gone and now I'm scared to backup or reboot.
    EDIT: the folders came back as soon as I tried to do a backup but I'm sure they are not the same folders. Just defaulted back to the system folders. I don't see the addon.d folder anymore and tried to do a backup with and without enabled compression. Didn't work so I don't know what do at this point so what I did is a flashed my room again without deleting anything and backup was working without 255 error but I lost everything and now my phone is constantly rebooting. I have a OnePlus 5 running Lineage 17.1 Android 10 rooted with Magisk

    • @BoostUpStation
      @BoostUpStation  Před 4 lety +2

      First of all cool down and don't panic
      attach your mobile to a computer
      and copy all your internal storage data to the machine
      so that you don't have to worry about the data anymore
      now see if the system is mounted in mount options of the recovery, if yes then the system partion data is gone and you have to reflash the current rom again without wiping anything, and reboot after flashing the current rom
      if the system is not mounted in the mount options, then mount it, and check if the files are there, if the files are there, then you can reboot, but if the files are not there, then you have to flashing the current rom as stated above.

    • @BoostUpStation
      @BoostUpStation  Před 4 lety +1

      when you have rebooted your mobile successfully, then you can create the backup

    • @echosen121
      @echosen121 Před 4 lety

      @@BoostUpStation I can't even see the files in English anymore all the files have mixed up letters and numbers. I don't know what's going on

    • @echosen121
      @echosen121 Před 4 lety

      @@BoostUpStation it's like it's showing me encrypted files

    • @BoostUpStation
      @BoostUpStation  Před 4 lety +1

      Ya, they are encrypted now
      i also had such an issue in past, and had to format data, which deleted all my internal storage data
      Remove the boot.img file from the current rom zip (use winrar) and flash via recovery as stated in the above comment and reboot to system and see if you can get the original data.
      if still haven't got, then format is the only option

  • @Hussein_Al_Harbi
    @Hussein_Al_Harbi Před 3 měsíci

    Really wonderful thank you and warm greetings from Iraq. 🇮🇶🤍