Hi, when creating a backup in TWRP, extractTarFork () process ends with ERROR: 255 TWRP after a while. It is related to the DATA directory (excl. Storage), when I include it in the backup, it jumps to that error. If I don't include it in the backup, it will happen. Is the backup directory important? How do I remove error 255? Thanks for the help.
dj.jericho said:
Hi, when creating a backup in TWRP, extractTarFork () process ends with ERROR: 255 TWRP after a while. It is related to the DATA directory (excl. Storage), when I include it in the backup, it jumps to that error. If I don't include it in the backup, it will happen. Is the backup directory important? How do I remove error 255? Thanks for the help.
Click to expand...
Click to collapse
Immediately before rebooting to TWRP, use root explorer like MiXplorer to delete /data/extm folder (usually it's empty but nevertheless delete it), or delete that folder from TWRP, Advanced, File manager, before backing up Data
Super thank you very much
zgfg said:
Immediately before rebooting to TWRP, use root explorer like MiXplorer to delete /data/extm folder (usually it's empty but nevertheless delete it), or delete that folder from TWRP, Advanced, File manager, before backing up Data
Click to expand...
Click to collapse
... and if I don't have ROOT is there any solution? I can't use Google Pay with ROOT rights.
dj.jericho said:
... and if I don't have ROOT is there any solution? I can't use Google Pay with ROOT rights.
Click to expand...
Click to collapse
See my previous answer. Use File mngr integrated to TWRP
zgfg said:
See my previous answer. Use File mngr integrated to TWRP
Click to expand...
Click to collapse
clear bug between chair and phone thanks
Related
Tried to view one of my contacts and got a FC on Contacts Storage (motorola.blur.providers.contacts). Do not know whether this has ever worked. Have had this Bionic for a couple days and froze a bunch of Motorola ****. The list isn't very long and I can provide that if necessary, but I'm just assuming this is what has caused my Contacts issue.
On to the actual issue, I uninstalled Contacts Storage (using Titanium Backup) and was going to reinstall it from the backup, but TB just hangs.
Tried all three different "App Processing modes" in TB and it hangs on restore regardless of this setting.
Extracted the apk out of Titanium Backup folder and tried to run it manually and it won't go (using ES File Explorer, mounted System as R/W).
Tried moving it to /system/app/ and running it (still mounted R/W) and it fails.
Will restoring ONLY "System" fix my problem and not delete all my other data that I've been busy setting up? Is there even a way to restore only System, using that FXZ?
If I can just chill and not worry about it until they come out with Clockworkmod Recovery, how do I make a flashable zip with just Contacts Storage in it?
Edit: Tried installing with adb and it fails with Failure [INSTALL_FAILED_DEXOPT]. I see other apps in the /system/app folder have .odex files with them. Am I just missing this one for the contacts (did it get removed by TB?)?
Edit: Got the .odex file from here and it still fails trying to install via Root Explorer.
Edit: Installation via adb with NO switches fails with Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]
Installation via adb with /l switch to Forward Lock it fails with Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
That Forward Lock one was a little past my point of not knowing what the hell I'm doing, so I will just chill and wait for a response. Thanks!
Edit: FXZ'd back to stock, installed CWM Recovery, backed up, restored Data only from the damaged instance via CWM Recovery, wiped cache. Everything is great and I didn't lose any data! Just had to get a fresh /system/ in there...
Hi,
I did backup with Titanium Backup, then I created update.zip. After wiping and installing ROM again, I also install update.zip from TB. All apps installs properly, but their data isn't recovered. Every app looses its settings.
What am I doing wrong?
maybe you need to have the right version --
http://www.androidpolice.com/2012/1...ate-flashable-zips-of-all-your-apps-and-data/
Ran into the same problem as well, turns out you will need TB installed and granted SU permissions before flashing update.zip in recovery so that data restore will work.
1. Install custom ROM
2. Boot into android, complete setup questions
3. Install TB from Google Play
4. Open TB, grant SU
5. Boot into Recovery and flash update.zip
6. Boot into Android, TB will autostart and start restoring data.
Hope that helps!
why restoring via cwm, while u can restore from TB?
thermax04 said:
why restoring via cwm, while u can restore from TB?
Click to expand...
Click to collapse
It's old, but I'm going to answer: the update.zip file generated with titanium backup may have a lot of apps and you can flash the zip file and the will all install at once. Otherwise, if you just boot the device and run TB app, it will ask you if yoy want to install or cancell befor installing, and after, it will let you choose between open new app or job done.
Then if you have like 35 apps to restore, you're like: install - done- install- done - install - done- install- done.............. like crazy.... zip file is just 1 for all and it's done
NOTE: restoring with update.zip is giving me a hard time with a few apps like whatsapp, waze and nikon wifi. You should have the regular TB backup in your sd just in case if you're wiping/flashing a rom.
figo_yjm said:
It's old, but I'm going to answer: the update.zip file generated with titanium backup may have a lot of apps and you can flash the zip file and the will all install at once. Otherwise, if you just boot the device and run TB app, it will ask you if yoy want to install or cancell befor installing, and after, it will let you choose between open new app or job done.
Then if you have like 35 apps to restore, you're like: install - done- install- done - install - done- install- done.............. like crazy.... zip file is just 1 for all and it's done
NOTE: restoring with update.zip is giving me a hard time with a few apps like whatsapp, waze and nikon wifi. You should have the regular TB backup in your sd just in case if you're wiping/flashing a rom.
Click to expand...
Click to collapse
How is creating an update.zip easier than just using the filter/batch function from within TiBU?
scooterbaga said:
How is creating an update.zip easier than just using the filter/batch function from within TiBU?
Click to expand...
Click to collapse
If it would work right, it's way faster, just try next time you wipe your phone.
The problem is that not all apps work properly this way. But via recovery it's just too fast, yet not recommended as the only backup as you might have to uninstall and restore a few apps that don't work right (force close)
It wold be nice to have all methods available working ok, but there's no doubt that the the app works better.
Just learned from experience. Many apps force closed when using update.zip. I'll stick with using TB app despite it taking longer
I can't restore my backup from april. Is it because of a new version? That would help me a lot guys I lost all my contact numbers....but I still have all my backups but titanium backup can't open it...
Salty Wagyu said:
Ran into the same problem as well, turns out you will need TB installed and granted SU permissions before flashing update.zip in recovery so that data restore will work.
1. Install custom ROM
2. Boot into android, complete setup questions
3. Install TB from Google Play
4. Open TB, grant SU
5. Boot into Recovery and flash update.zip
6. Boot into Android, TB will autostart and start restoring data.
Hope that helps!
Click to expand...
Click to collapse
Great guide!
Does TitaniumBackups restores data as well? When I tried to restore, "apps+data" it shows, ""E: Failed to sysmapfile". Does that means TiBackups can ONLY restore apps?
PapaWangsta said:
Great guide!
Does TitaniumBackups restores data as well? When I tried to restore, "apps+data" it shows, ""E: Failed to sysmapfile". Does that means TiBackups can ONLY restore apps?
Click to expand...
Click to collapse
I had same error when trying to apply the update.zip from Titanium backup via TWRP. In my situation the reason was that TWRP seems to have a limit of max. 2GB for an update.zip, as found somewhere in a discussion at XDA.
paarnoutse said:
I had same error when trying to apply the update.zip from Titanium backup via TWRP. In my situation the reason was that TWRP seems to have a limit of max. 2GB for an update.zip, as found somewhere in a discussion at XDA.
Click to expand...
Click to collapse
Yeah, that's what I though. Mine update.zip was 5.4GB. Shoot, that's whole lotta apps+data. Oh haha, looks like TRWP was freakin out and gave up. :laugh:
So.. what do you do if the update.zip > 2 GB? Googling led me to this post, but I'm looking for an answer. I have a 2.6 GB update.zip file and TWRP just gives an 'Error 3' when I try to install it.
Vortran said:
So.. what do you do if the update.zip > 2 GB? Googling led me to this post, but I'm looking for an answer. I have a 2.6 GB update.zip file and TWRP just gives an 'Error 3' when I try to install it.
Click to expand...
Click to collapse
max size 2GB
It's an old thread but did restoring via update.zip as improved? Also, is there still the 2gb limit since we are like 4 years after the last post Thnx for your feedback
Seems not like it. With latest Titanium backup version on 14 November 2018 I can't restore an update.zip bigger than 2GB (haven't tried smaller though).
Error 3 I get in TWRP
i have this maxi problem
the terminal is note4 with alliancerom lollipop and twrp.
the owner says he touched the app permissions in settings but now i have allow all.
I have tried using a root browser to write a file in folder sdcard but it is unsuccessful (failed operation). I would like to bakup chat in whatsapp it up by writing in databases folder does not work. probably there.
I did various tests, with the recovery file manager i can write on memory, I tried reinstalling rom (no wipe to keep the data) but I have not been successful. I think it is a system app that haven't write permissions but maybe I'm wrong.
does anyone have any idea?
thank you
Hi all,
I install magisk manager pro to see what it is, but my rooted oneplus 5t(with magisk v14.0) won't boot now. I see the boot logo of oneplus during about 5 secondes and reboot on twrp.
What must I do to recover it.
Thanks
Magisk Manager Pro? From the Play Store or some website? Uh-oh... Fake Managers not provided by @topjohnwu. Who knows what they'll do to your device...
From the release thread:
The Magisk and Magisk Manager Github releases are the ONLY official places to download Magisk!
NEVER trust 3rd party sources, don't go to scammy websites!
Click to expand...
Click to collapse
Best thing would probably be to restore your backup.
I have installed "magisk manager pro 2019" by the playstore
I reflash the rom and magisk but same result
Don't install anything not provided by @topjohnwu. It's just fake apps trying to monetize on Magisk's success. Worst case they'll even harm your device...
You might be able to manually remove the app, by navigating to its location in the TWRP file manager and delete it. Other than that, restoring a backup or wiping your device might be the only way to go.
ok thanks for your reply.
Did you know how to find the correct folder to delet this app ?
I download the .apk file of this app but don't find any folder.
May be I found an uninstall.sh in the .apk can I run it in twrp ?
wholehog2 said:
ok thanks for your reply.
Did you know how to find the correct folder to delet this app ?
I download the .apk file of this app but don't find any folder.
May be I found an uninstall.sh in the .apk can I run it in twrp ?
Click to expand...
Click to collapse
Kindly Do The Following
- Uninstall Magisk By Flashing Magisk-Uninstaller-20180328.zip Via TWRP
- Install Magisk Again
Dreamer(3MF): same issue
wholehog2 said:
Dreamer(3MF): same issue
Click to expand...
Click to collapse
Did You Grant The Installed App The Root Privilege?
I have install the app and reboot to see the changes, but I don't grant root privilege.
Maybe this is the problem ?
wholehog2 said:
ok thanks for your reply.
Did you know how to find the correct folder to delet this app ?
I download the .apk file of this app but don't find any folder.
May be I found an uninstall.sh in the .apk can I run it in twrp ?
Click to expand...
Click to collapse
You'll likely find files in /data/app, /data/data and /data/user_de/0 (and possibly other places) that are related to the app. Look for folders with the name bfd.app.poy.com.xss (the package name of the app) and delete those.
wholehog2 said:
I have install the app and reboot to see the changes, but I don't grant root privilege.
Maybe this is the problem ?
Click to expand...
Click to collapse
Anyway Try The Following
- Install Magisk
- Go To TWRP --> Advanced --> File Manager --> Data --> App --> Delete The Folder Of The Installed App
- (UP A Level) --> Data --> Delete The Folder Of The Installed App
- Clear DalvikCache & Cache Via TWRP --> Wipe --> Advanced Wipe --> Select Only Dalvik/ARTCache & Cache --> Swipe To Wipe --> Reboot
Didgeridoohan: I delete all folders bfd.app.poy.com.xss that I found in the folder you write, I reflash full rom and magisk but same issue.
Have you other ideas?
wholehog2 said:
Didgeridoohan: I delete all folders bfd.app.poy.com.xss that I found in the folder you write, I reflash full rom and magisk but same issue.
Have you other ideas?
Click to expand...
Click to collapse
Did you do anything else except install the app? It sounds strange that it would cause this kind of big issue. Does your device start if you don't install Magisk? Did you also install any modules that might be incompatible with your device? Etc...
Like I've said before, your best option might be to restore your backup (but by this time I'm assuming you don't have one).
If you can't get things figured out, the easiest solution is likely to wipe your device and start over. In TWRP you can choose to do an advanced wipe. Wipe everything except for internal storage (and external storage as well, of course) and then reinstall your system.
Don't forget to make regular backups once you get everything up and running again.
Didgeridoohan:
No I don't install other app or module. I install magisk manager pro 2019 and try to restart.
I have a backup a twrp backup but she is a little old. If there is only this solution I will do that.
Maybe is it possible to restaure ony the boot of twrp backup ?
Thanks.
How can I overwrite the apk in the system?
tobos said:
How can I overwrite the apk in the system?
Click to expand...
Click to collapse
You will need root and unlocked bootloader.
kamalaggi said:
You will need root and unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
It is already rooted with bootloader unlock and magisk.
Can I do so afterwards?
tobos said:
Thanks for the reply.
It is already rooted with bootloader unlock and magisk.
Can I do so afterwards?
Click to expand...
Click to collapse
Yep. Either Uninstall using titanium backup or remove apk from wherever the system apk is. Then push (or copy) to destination and set permissions to 755
I can't overwrite it.
iArvee said:
Yep. Either Uninstall using titanium backup or remove apk from wherever the system apk is. Then push (or copy) to destination and set permissions to 755
Click to expand...
Click to collapse
Thanks for the reply.
The titanium backup allows me to disable the app, but not to delete it.
It also says Root Explorerde permissions change failed.
Is there any other way to do this?
tobos said:
Thanks for the reply.
The titanium backup allows me to disable the app, but not to delete it.
It also says Root Explorerde permissions change failed.
Is there any other way to do this?
Click to expand...
Click to collapse
FWIW I'm having the same issue. Titanium Backup Pro says it can't find the APKs and Remove System Apps app thinks it does and then really does nothing. I even tried Lucky Patcher, which does the same thing.
Root File Browser shows everything in System/App and System/Priv-App as being 755, but if I try to change it to 777, it says it fails. If I try to delete anything, it looks like it does it, but then nothing changes.
If I try to change permissions through ADB, it tells me that the file system is Read-only, and if I tried to run ADB as root, it tells me it cannot run as root in production builds.
Edit:
Solution: Install any terminal emulator, and the Debloater module from Magisk to remove system apps systemlessly (see Debloater module official thread here)
Edit 2: There are three apps, Call of Duty, Tidal 3 month free trial, and Linked in, which are located in /oem/app and they cannot be removed by this method. I do not know how to remove them...