Процесс updater завершился с ошибкой 255 ошибка при установке zip файла twrp
In this guide, we will show you two different methods to fix the TWRP createTarFork Error 255 Backup Failed error. When it comes to custom development, there’s no denying the fact that a custom recovery is perhaps the best tool that a tech enthusiast could have at its disposal. And when we talk about custom recoveries, TWRP is right there at the top. It beholds quite a few noteworthy features, but two of its most useful ones are the ability to flash ZIP/IMG files and take a backup of all the partitions on your device.
The latter one is also known as Nandroid Backup and usually, it is the first prerequisite that you should straightaway check-mark off the list. However, not everyone is able to do so. There have been numerous complaints from concerned users that they aren’t able to create a Nandroid backup via TWRP. While trying to do so, they are being greeted with the following error message:
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder
So what is the reason for this error? Well, it tends to happen when you are using Parallel Apps. This feature allows you to create two different instances of an app, both of which will be completely in isolation from one another. For example, you could create two copies of WhatsApp and log in via two different numbers.
However, this Parallel Apps functionality tends to conflict with the creation of Nandroid Backup. Fortunately, there do tend to exist two different methods through which you could fix the TWRP createTarFork Error 255 Backup Failed error. And this guide shall make you aware of just that. So without further ado, let’s check them out.
Table of Contents
Расшифровка и устранение ошибок TWRP
Нередко при работе с TWRP у пользователей возникают различные ошибки. Все они сведены в таблицу ниже и для каждой ошибки предложен вариант устранения.
Проведя процедуру прошивки можно приступать к изменению настроек смартфона. Стоит аккуратнее относиться к настройкам устройства, поскольку большинство проблем, приводящих к необходимости прошивки, возникают именно из-за некорректной эксплуатации телефона.
После настройки прошивки и установки только самых нужных программ, советуем сделать полный бэкап прошивки, таким образом вы всегда сможете произвести восстановление смартфона.
При восстановлении раздела данных он достигнет 79%, а затем произнесет E:extractTarFork() process ended with ERROR=255 . Я пробовал это несколько раз с тем же результатом. К сожалению, я явно не могу попытаться создать новую резервную копию. Все остальные разделы восстанавливаются без проблем.
Согласно файлам журнала, причиной проблемы является //data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex .
Что я могу сделать? Я думал, что это может помочь удалить файл, так как Dalvik Cache — это просто кэш, который будет воссоздан, но как мне удалить файлы или папки из Nandroid Backup?
Method 1: Via File Explorer
- Download and install a File explorer app that supports root, such as Solid Explorer.
- Then launch the app, tap on the hamburger menu situated at the top left, and select Root.
- A Magisk request will now appear, tap on Grant.
- Now once you are within the Root directory, go to the following folders and check if any of them have a folder named 999 or not. If you find any such folder, then delete it right away.
That’s it. This should fix the TWRP createTarFork Error 255 Backup Failed error via File Manager. Let’s now make you aware of the second method to carry out this task.
Похожие вопросы
5 Резервное копирование /восстановление NANDroid зашифрованного устройства CM11 после очистки 4 Восстановление .bz2 Mysql Backup? 4 Может ли Titanium Backup успешно выполнять резервное копирование и восстановление Google Authenticator между ПЗУ? 4 BACKUP не удалось выполнить команду BACKUP DATABASE 17 Восстановление данных — восстановление поврежденных /форматированных файлов на карте HD Micro SD 7 Пользовательское восстановление Cyanogenmod не может выполнять резервное копирование, восстановление или применение обновления! 7 Как NANDroid для телефона без ClockWorkMod? 5 Извлечение данных приложения из резервной копии Nandroid /CWM 8 Любая разница между резервами, сделанными Titanium и Nandroid? 29 Какова связь между ROM Manager, ClockworkMod и Nandroid? Какие мне нужны? 9 Нужно ли мне что-то стереть, прежде чем восстанавливать полную резервную копию nandroid? 18 Есть ли способ сделать резервную копию Nandroid непосредственно на ПК, а затем восстановить ее прямо с ПК? 5 MySQL Server Backup 4 Akeeba BackUp: Безопасно ли использовать? 5 Titanium Backup Dropbox синхронизация 7 Бесплатные альтернативы «Titanium Backup Pro» 16 Windows 7 Backup Disk Full 8 Удаление файлов из rdiff-backup 4 Как установить каталог Drush Backup 7 Как сделать резервную копию Titanium Backup?
Алгоритм работы с TWRP для Xiaomi устройств
Итак, когда TWRP уже установлен на устройстве Xiaomi, а также, естественно, разблокирован загрузчик, можно приступать к процедуре. Важно при этом еще иметь и файл прошивки в .zip формате, который под каждое конкретное устройство скачивается на официальном сайте производителя или на тематических форумах, если пользователю больше приглянулась неофициальная сборка.
Выполняется установка прошивки через TWRP recovery следующим образом:
- Смартфон перезагружается со входом в TWRP recovery mode. Для этого нужно его выключить, а затем запустить посредством зажатия «качельки» громкости в положении вверх и кнопки включения смартфона. Результатом зажатия данной комбинации станет надпись «recovery» на экране и, как результат, вход в нужное меню.
- Теперь нужно выполнить сброс всех данных за исключением SD и OTG. Для этого переходим по разделам Wipe – Advanced Wipe и отмечаем следующие пункты: Dalvik Cache, System, Data, Internal Storage, Cache. Устройство будет полностью очищено!
- Затем нажимаем назад, выбираем Reboot recovery и подтверждаем действие (обычно нужно протянуть переключатель по экрану вправо).
- Предварительно на устройстве должен быть размещен файл прошивки.
Рекомендуется размещать .zip файл на SD|OTG карте памяти, поскольку в этом случае системная информация на устройстве будет занимать значительно меньше места, но не менее 200 мегабайт. Подобным образом стоит размещать и резервные копии, создаваемые через TWRP.
- Если нужные файлы загружены и все предыдущие этапы выполнены правильно, то можно нажимать «Install» и подтвердить действие (также по стандарту свайп вправо). Процедура прошивки может никак не отображаться на экране: нужно просто долго ждать.
- Когда прошивка через TWRP будет завершена, нужно выбрать раздел Wipe cache/dalvik, а затем Reboot System.
- Успешное проведение процедуры приведет к тому, что при первой перезагрузке три точки под логотипом производителя (Xiaomi) будут «перемигиваться» около 10 минут, а потом устройство запустится.
How to Fix TWRP createTarFork Error 255 Backup Failed
There are two different methods to carry out the aforementioned task- using TWRP Recovery or via File Explorer that has root capabilities. We have shared both the methods below, you may try out the one that you find more comfortable to deal with.
TWRP и с чем его «едят»
Изначально стоит понять, что такое TWRP, а потом уже говорить о том, как установить нужную прошивку, используя его. На самом деле все достаточно просто, если прочитать расшифровку данной аббревиатуры: TeamWin recovery. Фактически это неофициальный рекавери, которым можно заменить стандартное ПО любого смартфона, работающего на платформе Android. Еще TWRP называют кастомным и большинство пользователей, которые имели дело с ним и со стандартным рекавери, считают, что TWRP более эффективен, функционален и удобен в эксплуатации, к тому же он позволяет устанавливать помимо кастомных прошивок еще и ядра, модемы и прочие системные составляющие прошивки.
Далее будет представлена более подробная для TWRP recovery инструкция, при помощи которой можно будет установить прошивку на любое устройство от Xiaomi (инструкция имеет общий вид, поскольку системные файлы для разных моделей часто различаются).
Сразу стоит сказать, что для установки кастомной прошивки рекомендуется удалить все данные с телефона, а значит нужно сделать их резервную копию для последующего восстановления на устройстве с чистой системой. Также важно разблокировать загрузчик смартфона (bootloader). О том, как мы устанавливаем TWRP, уже говорилось в одной из статей, а потому сразу перейдем к информации о том, как перепрошить устройство с помощью TWRP своими руками.
Method 2: Via TWRP Recovery
- To begin with, boot your device to TWRP Recovery. You may use the hardware key combinations or the adb reboot recovery command.
- Once booted to TWRP, go to Advanced > Terminal. Now type in the following commands in the terminal window: (explanation given below, do read it):
Once all the 999 folders have been deleted, the issue stands rectified. On a side note, the TWRP method is exactly the same as the File Explorer one. It’s just that we are accessing each folder and deleting the folder named 999 via the commands in the TWRP Method whereas we did so by navigating through the folders in the File Explorer method.
So with this, we round off the guide on how to fix the TWRP createTarFork Error 255 Backup Failed error. If you have any queries concerning the aforementioned steps, do let us know in the comments section below.
Популярные теги
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
You will successfully be able to backup!!
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
then restore your backup!
simo6
Senior Member
Im using the newest blu_spark with my phone OEM unlocked rooted with magisk running the 5.01 OOS.
Click backup have 'createTarFork() process ended with ERROR=255'. copied log and found :
data/system/999
data/system_ce/999
data/misc/999
data/misc_ce/999
data/user/999
data/user_ce/999
Were unable to be backed up. so after deleting these folders through TWRP terminal i can backup without error.
However i cannot restore, as i keep getting the 'extractTarFork() process ended with ERROR=255' error on restoring. why cant our recovery just work? Ever since oreo launched on OP its been nothing but headaches. Every update triggers my encryption and forces me to totally wipe the phone and start from fresh install. (no matter how many of these xda update guides i follow). Ive been rooting and "modding" phones since the G1 and ive never had so many issues.
krumbman0wnz
Senior Member
How can you delete these folders when restoring? there is nothing on the phone besides the backup file folder. literally nothing.
simo6
Senior Member
How can you delete these folders when restoring? there is nothing on the phone besides the backup file folder. literally nothing.
Once u are in twrp u open file manager and delete manually the 999 folders since the system recreates them at every reboot
krumbman0wnz
Senior Member
Once u are in twrp u open file manager and delete manually the 999 folders since the system recreates them at every reboot
Bradl79
Senior Member
Amrut Parmar
Senior Member
krugm0f0
Senior Member
Im using the newest blu_spark TWRP with my OP5 OEM unlocked rooted with magisk running the 5.01 OOS.
BACKUP
Before running a backup do the following in TWRP/Advanced/Terminal
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
You will successfully be able to backup!!
I'm using latest by_ibe twrp and it's not working. No 999 folders found. Backup fails at system partition with error 255.
Will try bluspark twrp.
Sc4r3Crow
Senior Member
after some struggle I was able to restore my backup. When I selected reboot system, my phone was stuck on the oneplus scree. so I powered it off, started recovery and dirty flashed rom to be able to boot. It booted normaly with restored settings, layout and stuff. But then I recognized that some data was missing. I have 2 apps with important (personally important for me) statistical data, but the data is lost.
Is there a possibility to restore this data somehow?
When I've created the mentioned backup, I've checked every point, so everything should have been stored.
Thanks in advance.
pmbonea
Senior Member
Sorry but the only permanent solution for these errors while backup or restore is to factory reset your device and never touch the parallel app in setting. so far that's what solve my problem and now i can make backup and restore without any problem!
randy.turker
Senior Member
larpoux
Senior Member
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
- Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
- Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
- On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
- On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
- On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
- On others devices . you must find all parameters that create those unwanted users.
- If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
exgtigsr
Senior Member
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.
murcianista
Member
hello i have the Oneplus6T with OxygenOs and i having the same problem, i cant do a nandroido backup from twrp having the same problem 255, i have deleted the parallel app and the account but there is no luck at the moment.
any other advice ?
vargapirot
Senior Member
I deleted all folders mentioned above, deleted all parallel apps. It's not working for me.. I am getting same error when trying to make a backup.. :/
akeshma
Senior Member
Im using the newest blu_spark TWRP with my OP5 OEM unlocked rooted with magisk running the 5.01 OOS.
BACKUP
Before running a backup do the following in TWRP/Advanced/Terminal
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
You will successfully be able to backup!!
(enter exactly into terminal, if 999 'doesn't exist' move on to the next)
cd /data/system/
rm -r 999
cd data/system_ce/
rm -r 999
cd data/system_de/
rm -r 999
cd data/misc/
rm -r 999
cd data/misc_ce/
rm -r 999
cd data/misc_de/
rm -r 999
cd data/user/
rm -r 999
cd data/user_ce/
rm -r 999
cd data/user_de/
rm -r 999
then restore your backup!
hachamacha
Senior Member
I just ran into this too. I'm looking here after the fact and the way I fixed it and don't see what I did so this is it:
- for me, it was the presence of multi-user directories in numerous places. I don't use multi-users on pie so not sure why they're there, but it hurts nothing to delete them.
- if I only deleted 999, that'd not have worked for me
- First: I read the recovery.log file after rebooting after the failed backup. It's a big file, so I transferred it to a laptop and used notepad+ --
- Look in there for the error (tarfork) and then look for the file/directory that began the chain of errors. Mine happened to be /data/vendor_ce/10
- Go to your /data/ folder in root explorer (or equiv):
- Do an ls */10 to find out all the places the 10 user occurs or you'll then get the error on the next 10 file. For me it was 5 other dirs.
- All you should have for user number directories in those places is 0 (unless you use multiple users and then I don't know).
- delete each one. I did it all from adb on a booted op5. so like this: "rm -r /data//xx" where is where you found the 10 11 whatever, and xx is user-numbers other than 0
- when you've got them all gone, reboot directly into recovery so you have no chance of the system recreating them (so for me: adb reboot recovery)
- Backup. Mine worked no errors and was actually faster too because the errors take time to timeout.
- reboot system
Careful when using 'rm -r' that you only delete what you want to or you can mess up your phone. - cheers.
Edit: Twrp Version: Probably should mention SW versions: Twrp, latest 991 blu_spark twrp, OS: 9.0.3 Pie, Other: xXx noLimits Rom/Module
-
koreyb
Member
whatnoww
Member
How to fix error 255 twrp oneplus 5
I just ran into this too. I'm looking here after the fact and the way I fixed it and don't see what I did so this is it:
- for me, it was the presence of multi-user directories in numerous places. I don't use multi-users on pie so not sure why they're there, but it hurts nothing to delete them.
- if I only deleted 999, that'd not have worked for me
- First: I read the recovery.log file after rebooting after the failed backup. It's a big file, so I transferred it to a laptop and used notepad+ --
- Look in there for the error (tarfork) and then look for the file/directory that began the chain of errors. Mine happened to be /data/vendor_ce/10
- Go to your /data/ folder in root explorer (or equiv):
- Do an ls */10 to find out all the places the 10 user occurs or you'll then get the error on the next 10 file. For me it was 5 other dirs.
- All you should have for user number directories in those places is 0 (unless you use multiple users and then I don't know).
- delete each one. I did it all from adb on a booted op5. so like this: "rm -r /data//xx" where is where you found the 10 11 whatever, and xx is user-numbers other than 0
- when you've got them all gone, reboot directly into recovery so you have no chance of the system recreating them (so for me: adb reboot recovery)
- Backup. Mine worked no errors and was actually faster too because the errors take time to timeout.
- reboot system
Careful when using 'rm -r' that you only delete what you want to or you can mess up your phone. - cheers.
Edit: Twrp Version: Probably should mention SW versions: Twrp, latest 991 blu_spark twrp, OS: 9.0.3 Pie, Other: xXx noLimits Rom/Module
-
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
Sachin
Recognized Contributor
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
andreymixmax
Senior Member
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
nilanko
Senior Member
I am stuck with the same problem. Can you link me to your answer to him or just again tell me what's the solution?
Firmware was 90MB before, after trying to restore it, TWRP wiped it and now it's 23MB.
Sachin
Recognized Contributor
I am stuck with the same problem. Can you link me to your answer to him or just again tell me what's the solution?
Firmware was 90MB before, after trying to restore it, TWRP wiped it and now it's 23MB.
The answer is to just restore system, data and boot. That's the way to go.
Sent from my mido using XDA Labs
mfadh29
Senior Member
phyowaidd
Senior Member
From my experience, i think it is because of miui rom??
After trying many time, I used this method .
1. first wipe everything
2. flash original zip rom
3.then flash your backup
4. Flash lazyflasher
It will show error though but you will get radio working
AmanBhagat
New member
Firmware Problem "extractTarFork process ended with ERROR 255"
In My case Firmware is not restoring
shoiwing error "extractTarFork process ended with ERROR 255"
so to solve it
1.Wipe data dalvik cache and system
2.Just flash the new rom which u had earlier.
for exp. i had lineage 14.1
3.After installing it ask for wipe dalvik and cache do it then dont wipe it from the main menu.
4.just restore the backuped file without ticking the firmware
Note-Firmware must be untick while restoring
5.done Problem of fingerprint scanner and network problem also solved by this
Note-Dont restart in between
sohanaw
Senior Member
In My case Firmware is not restoring
shoiwing error "extractTarFork process ended with ERROR 255"
so to solve it
1.Wipe data dalvik cache and system
2.Just flash the new rom which u had earlier.
for exp. i had lineage 14.1
3.After installing it ask for wipe dalvik and cache do it then dont wipe it from the main menu.
4.just restore the backuped file without ticking the firmware
Note-Firmware must be untick while restoring
5.done Problem of fingerprint scanner and network problem also solved by this
Note-Dont restart in between
ramping
Senior Member
Hello ..
Someone help me.
i Took Backup from Official TWRP but when i am trying to restore it giving me error=255 . How i fix this.
it happens when i am trying to restore FIRMWARE partition.
any solution . anyone facing this issue.. ?
That happened to me twice, loosing the imei.
To fix it, just restore or flash any rom you want, and follow this steps:
- Extract NON-HLOS.bin file from official ROM.
- Copy extracted NON-HLOS.bin to the adb/fastboot folder.
- Boot your device into fastboot mode.
- Connect your device to PC
- In the folder with adb/fastboot tools press “Shift” key + right mouse button and select “Open command window here”.
- Enter these commands in order:
sohanaw
Senior Member
That happened to me twice, loosing the imei.
To fix it, just restore or flash any rom you want, and follow this steps:
- Extract NON-HLOS.bin file from official ROM.
- Copy extracted NON-HLOS.bin to the adb/fastboot folder.
- Boot your device into fastboot mode.
- Connect your device to PC
- In the folder with adb/fastboot tools press “Shift” key + right mouse button and select “Open command window here”.
- Enter these commands in order:
modem is okay i am able to flash that.
but for me persist is showing 0mb in twrp and i am unable to flash persist i have tried fastboot miflash none worked for me .
please if you have any other method then share.
DonEHogan
New member
Go back to StockROM with the help of Xiaomi's tools
Had the same problem. The methods above didn't work for me, either.
I went back to StockROM with the tools provided on the Xiaomi website, the process will re-flash the firmware, too and all described problems will be solved. Make sure you'll untick "firmware" on the next time when trying a restore
XavierBrian
Senior Member
That happened to me twice, loosing the imei.
To fix it, just restore or flash any rom you want, and follow this steps:
Extract NON-HLOS.bin file from official ROM.
Copy extracted NON-HLOS.bin to the adb/fastboot folder.
Boot your device into fastboot mode.
Connect your device to PC
In the folder with adb/fastboot tools press “Shift” key + right mouse button and select “Open command window here”.
Enter these commands in order:
Well what can i said??u really save my poor soul last night!!been 2 days searching for solution after error 255 on my redmi 5 plus,ur solution work perfectly n thank you brooooo.
Sent from my Redmi 5 Plus using XDA Labs
gvovs
Member
well this is weird.
I'm having error 255 on firmware partition restore, no matter what I do (redmi note4x snapdragon global, nandroid backups from stock miui8.5-9.2 and LAOS15.1)
samarium
Senior Member
I had this problem on a Redmi Note 3 Pro/Qualcomm recently. It seems to me to be loosely correlated to the /data backup size, and seems to manifest just below 4GB, looks suspiciously like some 32bit counter/offset . but . in my case this seems to happen only in the first tar/win file which much < 2GB uncompressed anyway.
Interestingly, not all tar binaries are equal. The binary from LineageOS 14.1 crashes reading win000 files often if I try to test this from a terminal session when the phone is booted normally, however tar from TWRP does work and doesn't crash. Using tar from ubuntu 18.04 I can see all the files, however there are numerous reports of
Maybe this tar crash is also what is happening for the TWRP GUI using it's internal tar? Although this seems to be crashing when the recovery is nearing 4GB, however my tar crash seems to happen on the first segmented win000 file? Maybe it is related in some way to pigz which seems to be used by the TWRP GUI to compress/uncompress and it does multi-threading. I haven't looked at TWRP code.
I tried TWRP 3.1.1-0, and downloaded the latest 3.2.3-0 from twrp.me. Both failed in the same way.
I inspected some of the backups I had, finding decrypted /data space usage less /data/media:
Irrespective of the actual failure mode, I was able to restore the other backups manually.
Interestingly when I examine the .win and .win000 files with
I find that the single .win file backups need to be restored while current directory is /data whereas the multipart backups need to be restored while current directory is /.
- Backup everything to storage external the phone, and then backup the backup.
- Wipe /data. I prefer to format /data while also wipes /data/media = /sdcard as this guarantees /data is clean, however if your backups are stored in /sdcard/TWRP then you are going to need to either not format /data or restore them from your PC, or not store them in /sdcard/TWRP and store them on an external sdcard or external USB OTG drive. Actual location may vary depending on TWRP build. Determine the b= lines below appropriately.
- Connect using adb shell. You could type this in using the TWRP Advanced Terminal, but error prone.
- Make sure you have enough free space on /data to do the restore. You should have, but this is the manual process so cross check.
- Restore the .win0?? files with tar.
Any ideas? I've tried TWRP 3.1.1.0 and 3.2.1.0 but it just reports back "updater process ended with error 255" and terminates?
TheFixItMan
Senior Member
Any ideas? I've tried TWRP 3.1.1.0 and 3.2.1.0 but it just reports back "updater process ended with error 255" and terminates?
You are using the 32bit twrp to try and install a 64bit rom
My official twrp does not support 64bit roms - if you read the faqs in my twrp thread you would know this
Note - I do not support the unofficial 64bit twrp as I did not build it
junglebungle
Senior Member
You are using the 32bit twrp to try and install a 64bit rom
My official twrp does not support 64bit roms - if you read the faqs in my twrp thread you would know this
Note - I do not support the unofficial 64bit twrp as I did not build it
grwalker
Senior Member
Hi all,
when i use the 64 bit version i cant see any folders other than root folders. So i cant find the zips to flash. Any thoughts please?
riyan65
Senior Member
Hi all,
when i use the 64 bit version i cant see any folders other than root folders. So i cant find the zips to flash. Any thoughts please?
grwalker
Senior Member
I did that. I see the root folders but nothing in internal storage. And the size of internal storage shows as 0MB
Attachments
TheFixItMan
Senior Member
I did that. I see the root folders but nothing in internal storage. And the size of internal storage shows as 0MB
Scroll down
Select storage folder
Select something like emulated then 0
If you don't see emulated than 0 or the folder is empty then internal storage isn't mounted - check the mount section of twrp or try using a different twrp
To check external storage it's the same as above but you select emulated then the folder with the sdcard hex value as its name which is different with every sdcard
grwalker
Senior Member
Scroll down
Select storage folder
Select something like emulated then 0
If you don't see emulated than 0 or the folder is empty then internal storage isn't mounted - check the mount section of twrp or try using a different twrp
To check external storage it's the same as above but you select emulated then the folder with the sdcard hex value as its name which is different with every sdcard
Thanks for the post.
Unfortunately no luck. I cant see anything in the storage folder.
I have tried to mount internal storage also with no luck. Internal storage shows as 0MB
Attachments
TheFixItMan
Senior Member
Thanks for the post.
Unfortunately no luck. I cant see anything in the storage folder.
I have tried to mount internal storage also with no luck. Internal storage shows as 0MB
Looking at your phone it doesn't look like a moto g5
It looks more like a g5 plus or g5s
What is your device xt name eg xt1676 - if it's not a moto g5 codename cedric you are in the wrong device forum and using the wrong twrp
grwalker
Senior Member
Looking at your phone it doesn't look like a moto g5
It looks more like a g5 plus or g5s
What is your device xt name eg xt1676 - if it's not a moto g5 codename cedric you are in the wrong device forum and using the wrong twrp
Yes it is a G5. Here's a photo from bootloader
FYI. when i flash 32bit TWRP i can see internal storage. But, of course, i cant flash custom roms from there because they are 64bit. Tried with lineage and Res remix. Error255 results
Attachments
TheFixItMan
Senior Member
Yes it is a G5. Here's a photo from bootloader
FYI. when i flash 32bit TWRP i can see internal storage. But, of course, i cant flash custom roms from there because they are 64bit. Tried with lineage and Res remix. Error255 results
If you can't mount internal storage your only option might be to format it
This will delete everything in the internal user data - pictures music documents etc - backup first!
Wipe - format data (option on the right)
Restart back to recovery
If it's not mountable wipe advanced wipe data and internal storage
Note if you didn't decrypt data (if asked) when launching twrp you need to format data anyway to remove encryption in order to be able to mount it
Also some 64bit twrp don't support encryption so it might not even ask for decrypt - the one I posted above should support encryption but you still need to format data if flashing a new rom
grwalker
Senior Member
If you can't mount internal storage your only option might be to format it
This will delete everything in the internal user data - pictures music documents etc - backup first!
Wipe - format data (option on the right)
Restart back to recovery
If it's not mountable wipe advanced wipe data and internal storage
Note if you didn't decrypt data (if asked) when launching twrp you need to format data anyway to remove encryption in order to be able to mount it
Also some 64bit twrp don't support encryption so it might not even ask for decrypt - the one I posted above should support encryption but you still need to format data if flashing a new rom
Thanks, those steps worked.
Interesting on first install i didnt get a question about decrypting.
After reformat the only folder i saw in /sdcard was TWRP. So i dropped the rom and gapps zips in there. No problem flashing from there
2 ответа
У меня была похожая проблема, оказалось, что мне не хватило места на телефоне.
Хорошей альтернативой может быть восстановление с USB-устройства или SD-карты.
ответил maximus 19 июля 2016, 05:49:04
«» При восстановлении раздела данных он достигнет 79%, а затем произнесет E: процесс extractTarFork () завершился с ОШИБКОЙ = 255 , Я пробовал это несколько раз с тем же результатом. К сожалению, я явно не могу попытаться создать новую резервную копию. Все остальные разделы восстанавливаются без проблем. «»
Я думаю, что самое простое решение этой проблемы, если оно падает на данные. Попробуйте стереть dalvic и кеш, затем отформатировать память после восстановления резервной копии с SD-карты. Если у вас есть резервная копия TWRP во внутренней памяти телефона, переместите ее на внешнюю карту памяти, чтобы не потерять ее.
ответил Nick 1 августа 2018, 19:15:15
About Chief Editor
Sadique Hassan
A technical geek by birth, he always has a keen interest in the Android platform right since the birth of the HTC Dream. The open-source environment always seems to intrigue him with the plethora of options available at his fingertips. “MBA by profession, blogger by choice!”
В некоторых случаях устройства Xiaomi начинают давать сбои, подглючивать или вовсе некоторые из основных функций выходят из строя, что делает невозможным их нормальную эксплуатацию. Для устранения любых проблем кардинальным, но при этом эффективным способом, всегда можно перепрошить устройство. В статье речь пойдет о том, как производится прошивка через TWRP и чем данный способ лучше альтернативных ему (с подробной инструкцией по реализации).
Читайте также: