TWRP Nandroid backup issues - General Questions and Answers

Hi all, I've been having an issue with TWRP in that my backup size is huge. The data partition takes up about 8gb compressed and over 14 uncompressed. This is an absurdly large amount, does anyone know why it is this big? I tried clearing a lot of apps and space but the difference was negligible.
Also, managed to get just enough space to run a backup but deleting more than I'd have liked to, but then the backup keeps failing because i get the "createTarFork() process ended with ERROR=255".
Can anyone help me address my issues? This is the last step i have before flashing a new rom.
I'm running TWRP 3.0.0 on my LG G3 D850 with CloudyG3 2.2

Related

[Q] Less internal memory after restoring backup

Hi all. Here is my situation.
I was running Ninja716 rom. A fellow xda member had some questions about gingerbeast so i made a backup of my setup and restored my old gingerbeast backup. Later that day(yesterday) i flashed back my backup to Ninja. Noticed that i there was an update for an app and tried installing it. it failed so i went in to manage applications and cleared market cache and that fixed it. But while i was there i noticed that my storage use was higher normal. it was a 70mb difference.
Normally i have about 90mb of internal storage use out of the 1 gb. After restoring the backup it was up to 165mb in use. today i flashed back my same gingerbeast backup to test something checked the storage use and its up even more now up to 182mb. Anyone experience this?
I have tried full wiping before the restore and no difference. I saw this happend a while back with a previous restore but it wasnt a big deal as dill released a new version of gingerbeast and i like clean installs so that took care of it. Its not really a big issue as i still have lot of space left but just wanted to know if anyone has experienced this.
Here is my setup:
current rom:
Ninja 716
Lordmod 6.0.1 BFS kernal
4.11.m2 radio
Gingerbeast 2.1.2
default kernal
CWR-3.0.2.6

[Q] New tablet owner looking for space...

I installed cm9 on my samsung galaxy tab 2 7 and am really digging it. I'm really new to the whole cyanogenmod and android tablet thing. I have performed a factory reset, but there seems to still be things on the device taking up space.
With only 8 gigs of space to start with space is at a premium, so is there anything i can do to safely wipe the whole thing and start from a fresh install? Is this even possible?
Any space saving advice is welcome.
Brandon
btmullins said:
I installed cm9 on my samsung galaxy tab 2 7 and am really digging it. I'm really new to the whole cyanogenmod and android tablet thing. I have performed a factory reset, but there seems to still be things on the device taking up space.
With only 8 gigs of space to start with space is at a premium, so is there anything i can do to safely wipe the whole thing and start from a fresh install? Is this even possible?
Any space saving advice is welcome.
Brandon
Click to expand...
Click to collapse
I guess you could try before installing, do a factory reset in Stock ROM, that will format your Sdcard and give you more space... Don't forget to do a TB backup...
I have only 1.5 gigs on my Fascinate, but I am only using about 800mb. Android apps do not take up very much space at all. Also, forgive me if I misinterpret your question, but the space is taken up by your /system and /data partitions, which eat into the 8 gb.
focasam said:
I guess you could try before installing, do a factory reset in Stock ROM, that will format your Sdcard and give you more space... Don't forget to do a TB backup...
Click to expand...
Click to collapse
Um... In my haste I did neglect to do a backup. Fortunately everything seems to be in working order. I am using CWM to do a backup now.
Is there a reason I should use TB to do a backup instead of CWM?
I'm still really new to this, I'm just glad I didn't screw anything up on my first try.
As long as you use it only, TB backup should be functionally equivalent to a CWM NAND backup. But if you upgrade to another TAB, only TB backup could be easily transferred to thew new TAB. CWM NAND backup could note be used on the new TAB.

System Data too Large - Fix

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

Help with TWRP and Nandroid Backup?

Hi all, I've been having an issue with TWRP in that my backup size is huge. The data partition takes up about 8gb compressed and over 14 uncompressed. This is an absurdly large amount, does anyone know why it is this big? I tried clearing a lot of apps and space but the difference was negligible.
Also, managed to get just enough space to run a backup but deleting more than I'd have liked to, but then the backup keeps failing because i get the "createTarFork() process ended with ERROR=255".
Can anyone help me address my issues? This is the last step i have before flashing a new rom.
I'm running TWRP 3.0.0 on my D850 with CloudyG3 2.2
My backup is also above 8 gb.that's normal.
Try to create at least 10 gb before restoring.use otg to have backup on flash drive.it would help you.

Titanium Backup error 3 when flashing "update.zip" from TWRP!

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.

Categories

Resources