Hello All,
I had the dreaded System Data too large problem....it took up 1.2G of my 1.5G data partition and I could no longer install or update any new apps. This is what I did to fix it: 1) Performed a Nandroid Backup, 2) Used a root capable file explorer (Yaffs in my case) and deleted all files from my dalvik cache (/data/dalvik-cache), 3) Rebooted the phone, but it was not working properly afterwards, so I restored the previous nandroid backup. After restoring the backup, the System data was only 30MB and the phone is working fine. It seems as though over time the dalvik cache fills up with junk from all apps you have installed/uninstalled/earlier versions, etc., so its a good idea to flush it periodically. I looked for many hours trying to find a solution to this and this it what worked for me.
Best,
Jon
hey bro this work for lg g3 d855p? my g3 has 5.05 gb took by "system daga" which is undeletable. it is crazy becouse one hour ago my "system data" was about 4.97gb. can you make a video o something more pratical? thanks broo
Related
I've been having a problem as of late and I was hoping maybe someone could offer some explanation, advice, etc.
Last Friday, after a full wipe, I flashed Liquid Gingerbread 3.0 after running 2.6 forever. I use My Backup Pro to backup and restore app data. I do not use it for anything else (no system data, etc.). I installed all my Apps from apks I had, then restored app data with My Backup Pro.
I then proceeded to move apps to sd with Apps2sd like I usually do. Everything seemed to be okay until I noticed a while later that apps moved to the card started disappearing, but the app data was remaining on the sd and the coms were still listed as installed. I uninstalled Apps2sd and reinstalled the apps, noticing that large apps (10 + mb) were installing directly to the sd. I checked the settings and made sure internal was set for app installations and tried again. Large apps were still installing directly to the sd.
Thinking that maybe I didn't wipe properly (lol) I did another full wipe (system, data, cache, davlik) and reflashed LGB 3.0. I did the same process as above with installing and restoring app data. I rebooted my phone to find that large Apps were still installing directly to the sd, and still disappearing and still leaving behind data on the sd.
I thought it was a ROM issue at this point so I did another full wipe and flashed iBolt 0.9. Still having the same problem so I know it's my phone.
I have a few ideas of what is happening but I don't know how to fix it. Is there something on my sd card that is affecting the way apps are installed? Is there a cm7 setting I'm missing somewhere that is affecting it? Are my wipes somehow leaving behind remnants? I know this is long but I was trying to be as specific as possible in hopes of some feedback. If someone has any ideas as to what is happening I'll try anything to see if it fixes it.
My apologies if there is a thread about this already here but Tapatalk search is seriously lacking.
Drunk texted from my Thunderbreaded Bolt
The problem is below you. Lock your apps or DC will take your apps 2 !!
notgnihsaw+esuoh+etihw= Thieves&Crooks
Hello ... I did something incredibly stupid and am on here as a last resort for help.
Have a rooted (but still locked) TF300t on Jelly bean 4.2.1. Using Titanium Pro. Did a backup apps + data a few hours ago. Had been downloading a lot of apps lately, tablet was feeling sluggish, decided to do a cold boot. Got distracted by somebody talking to me, didn't notice that instead of selecting the little green android to reboot, I selected "wipe data". Brilliant, I know.
So I downloaded Titanium from Play again, and tried to do a restore. But there doesn't appear to be anything for it to restore. The Titanium folder on my microSD just has a small XML file in it.
So... is there any chance of getting my apps and data back? Or is it all totally wiped and unrecoverable? And even with OTA Rootkeeper, have I lost root (I assume, since SuperSU is gone too)? Any advice welcome.
Also - any tips to use Titanium more effectively so that next time I do something this dumb, I can actually restore?
Ok - so my initial fear that the wipe data had somehow wiped my microSD is totally off the mark.
It looks like when I copied the Titanium backup from internal to microSD, there was an error and it didn't actually copy. It was confusing at first since I have nothing else stored on my microSD so it looked like it had been wiped except for the titanium licence xml file.
So - anybody have any ideas other than going to Google Play and re-downloading every app and saying goodbye to all of my previous data?
SOLVED - I just reinstalled all the APK, automatically linking them on the SD card. The data was still on the EXT4 partition, so everything was found by the apps.
--------------
Hi,
Link2SD was working really nice, until randomly, I kept getting errors saying it cannot links the apps...
So I've fulled backed up my EXT4 partition on my computer (Just drag and dropped the folders. Not sure if this was correct), powered off the phone, reformetted the EXT4 partition with GParted, copied the files back in with Linux, put the SD card back in the phone, power it ON;
But now, Link2SD does not detect the apps that I've copied back on the card - although it can link the apps again.
The apps that were restored simply doesn't appear anywhere (But are on the partition).
Is there any way I can restore the full EXT4 backup I've took ?
GameX2 said:
SOLVED - I just reinstalled all the APK, automatically linking them on the SD card. The data was still on the EXT4 partition, so everything was found by the apps..
Click to expand...
Click to collapse
Your solution didn't work for me because it just gave an error whenever I tried to reinstall one of the previously linked apps. Likely because of the excess files leftover from the original because it would let me install new apps but not the missing ones. I tried to delete some files manually for an app or two, but that didn't work either. I found an easy solution though that works.
SOLUTION:
Just open Link2SD. Click the top left corner for the menu. Then click on "Clean up the 2nd partition". When I did it said it needed to delete 104 unused files, so I said ok. Afterwards, actually all but 2(out of 32) of my apps were restored with data automatically and those two I just restored from Titanium Backup.
NOTE FOR ANYONE TRYING THIS:
If it's still not working after that, then just try to reboot and see if they reappear. If you do lose some apps, at least you can reinstall or restore them from a backup after that. Again I only lost 2, but the other 30 missing linked apps were restored.
Hi, 2 days ago with the help of App Inspector and MiXplorer i was debloating my phone from all those useless apps like Huawei ID, HiCare, Swiftkey, ecc. and while I was doing it i took the chance to remove some other service packages that I'm sure I'd never used in future, like Geofence, Mapcon, Fido client, ecc. Everything worked nice in the phone, overall because obviously i paid an extreme caution while removing packages since that we're talking about system files, and i fact i didn't noticed incompatibilities or other issues while using the phone in these 48h.
The only problem that i encountered is that now my TWRP isn't able to restore a nandroid backup without getting a failure accompanied by the error mentioned in thread title.
Code:
[COLOR="red"]extractTarFork() process ended with ERROR: 255[/COLOR]
When i reboot to system however, everything is fine except the theme that i have to set again, the list of previous SMS empty (but i have contacts, system settings, apps, notes, everything else) and a leftover of Swiftkey app that i have to remove again. I tried with 2 different backups: one made before debloating the phone 2 days ago, and the second is a backup took today on the phone already debloated. Anyway making some searches around i found this topic https://github.com/TeamWin/Team-Win-Recovery-Project/issues/964 in which i read that a possible cause could be the amount of free space on the phone, but i have more than 17GB free and I'm restoring the backup from external SD, so i can exclude for sure this cause... Another solution standing by what i read elsewhere could be to unmount the "data" partition on the phone before restoring the backup, but neither that changed a single thing and i keep getting the same error. I think that what could provoke this issue is related to some files linked to missing apks, like data of an app removed but it's the only clue i have about now.
I hope that someone can really help me out on this because TWRP backups for me are essential. Looking forward for your answers guys! Any help will be extremely appreciated!!
EDIT: i can provide logs obviously if someone could be able to detect the error by reading them, i can't so let me know if someone would like to dedicate some minute on reading a log
Other things noticed: i had to reflash again Magisk Modules and even Magisk V14.3 zip to being able to flash modules stored on my SD, even if Magisk was still installed. This is surely due the fact that the restore of data partition started and then it got stopped by fault of error 255, so data partition wasn't fully restored. The thing that i just can't understand is why even the older backup isn't working, maybe I'll have to format data dalvik and cache to get the older backup working..? Damn
Bump. C'mon guys, really no one??
RedSkull23 said:
Bump. C'mon guys, really no one??
Click to expand...
Click to collapse
Haven't seen yet bro
shashank1320 said:
Haven't seen yet bro
Click to expand...
Click to collapse
Dammit that's bad, i known from beginning that it's a complex issue but i thought that someone here could help...
RedSkull23 said:
Other things noticed: i had to reflash again Magisk Modules and even Magisk V14.3 zip to being able to flash modules stored on my SD, even if Magisk was still installed. This is surely due the fact that the restore of data partition started and then it got stopped by fault of error 255, so data partition wasn't fully restored. The thing that i just can't understand is why even the older backup isn't working, maybe I'll have to format data dalvik and cache to get the older backup working..? Damn
Click to expand...
Click to collapse
May be you need to format data, dalvik and cache and then reboot to recovery again from recovery.
I am facing such issue these days and had to opt for this to mount data again. Never understood this concept with huawei phones. my old Yu Yureka was hell easier to flash all these.
shashank1320 said:
May be you need to format data, dalvik and cache and then reboot to recovery again from recovery.
I am facing such issue these days and had to opt for this to mount data again. Never understood this concept with huawei phones. my old Yu Yureka was hell easier to flash all these.
Click to expand...
Click to collapse
The only thing that stops me from trying to solve this by wiping data, dalvik and cache is that if after wiping the issue will persist, other than not being able to restore my backup I'd find myself with a phone where i have to restart from scratch too. And so it could be even worse... I really don't know what to do at the moment, but i must fix this.
RedSkull23 said:
The only thing that stops me from trying to solve this by wiping data, dalvik and cache is that if after wiping the issue will persist, other than not being able to restore my backup I'd find myself with a phone where i have to restart from scratch too. And so it could be even worse... I really don't know what to do at the moment, but i must fix this.
Click to expand...
Click to collapse
May be a twrp backup... once all restored then restore data
So, some day ago i managed to solve my problem trying once again to restoring a copy of a TWRP backup, this time an older one dated 2 weeks ago other than 1 like the previous backup... (for safety reasons i always keep 2 backups, and i overwrite these weekly one after another, by the most recent) and this time it worked. I seriously can't understand why this error happened only on the 1st and more recent backup, since that i started to debloat some system apks and packages only 1 week after the latest backup, and so without system modifications the error shouldn't have to be already present on the backup took exactly 1 week before starting to remove files... but i'm out of this now
TL;DR: How to fix Titanium Backup error 3 while flashing "update.zip" from TWRP?
I have been using Android for more than five years now seriously and it is a bit funny that I did not know I could restore data to newly flashed ROM.
Previously, I would just wipe system and flash new ROM not touching data partition and that worked just fine.
That is past seems.
I have flashed new ROM which is based on stock Samsung Galaxy S9 Plus ROM so I could get official updates. The problem is my phone lost one fifth of its performance according to benchmark and it experiences random reboots (I hope not while I am typing ?)
All in all, by restoring previous data on new ROM some of the files seem not to be overwritten well on new ROM (possibly application versions not getting downgraded well).
LogCat did not help.
I deleted my data (I have backup of course) and my system works normally so it is a data problem.
That is where Titanium Backup came into play.
I made backup of all user applications and an "update.zip".
When I want to flash "update.zip I get error code 3.
Some say it is due system partition but I formatted it in couple of manners and I am still unable to restore.
Is there any other way to restore applications and its data to new ROM?
I have tried backing up the applications and moving the Titanium Backup folder to SD card and moving it back when I flash new ROM. Backup does not get detected.
Thank you in advance!
dedq said:
TL;DR: How to fix Titanium Backup error 3 while flashing "update.zip" from TWRP?
I have been using Android for more than five years now seriously and it is a bit funny that I did not know I could restore data to newly flashed ROM.
Previously, I would just wipe system and flash new ROM not touching data partition and that worked just fine.
That is past seems.
I have flashed new ROM which is based on stock Samsung Galaxy S9 Plus ROM so I could get official updates. The problem is my phone lost one fifth of its performance according to benchmark and it experiences random reboots (I hope not while I am typing [emoji854])
All in all, by restoring previous data on new ROM some of the files seem not to be overwritten well on new ROM (possibly application versions not getting downgraded well).
LogCat did not help.
I deleted my data (I have backup of course) and my system works normally so it is a data problem.
That is where Titanium Backup came into play.
I made backup of all user applications and an "update.zip".
When I want to flash "update.zip I get error code 3.
Some say it is due system partition but I formatted it in couple of manners and I am still unable to restore.
Is there any other way to restore applications and its data to new ROM?
I have tried backing up the applications and moving the Titanium Backup folder to SD card and moving it back when I flash new ROM. Backup does not get detected.
Thank you in advance!
Click to expand...
Click to collapse
When switching ROMs, restoring data from a previous ROM causes issues, especially when the data contains system data and apps from the previous ROM, user apps and their data usually restore fine, but the system stuff doesn't.
Sent from my SM-S767VL using Tapatalk
Solved using Migrate.