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.
Related
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
it seems like i have a 30% chance of creating a proper nandroid backup (as in, maybe 3 out of 10 i have made in the past month seem to work, and the rest either give me errors when trying to restore, or they'll just sit on the splash screen upon rebooting, or they'll just "restore" me back to out of the box new.
am i doing something wrong when i'm creating my backups? i'm using TWRP 2.4.3.0. it seems to mess up on both restoring to the SD card and restoring to internal storage.
either way, i tried restoring a nandroid today and it is "completing" but it's really just failing. TWRP says "restoring data...data done 0 seconds...restoring cache...cache done 2 seconds, restoring boot...boot done 1 second" and the whole thing is "completed" in 60 seconds. when i reboot, it just sits on the jelly beans splash screen and i have to pull the battery.
i'm now dreading the thought of having to re-flash the ROM and set everything up again. any help would be most appreciated. thanks!
Whats the size of the back up? Did you format the system partition before restoring the back up? Also this might be a good time to update twrp to 2.5.0.0.
Surge1223
The only time I have seen this occur is when my SD card was going bad or already dying. I just had another SD card fail so I don't think its all that uncommon. I believe that TWRP will create md5 files during the backup process, if you took the time you could probably use those to verify.
Surge1223 said:
Whats the size of the back up? Did you format the system partition before restoring the back up? Also this might be a good time to update twrp to 2.5.0.0.
Surge1223
Click to expand...
Click to collapse
sometimes the backup is 1.2 GB, sometimes 1.5 GB, sometimes 1.6 GB, sometimes 2.1 GB.
could it be that sometimes i'm creating a backup with only ~3 GB free (either internal or external SD card)?
i'm back and running because i found a nandroid from two weeks ago that works, and it was right after a fresh flash of Jelly Beans B14. i cleared off a lot of space and now i'm creating nandroids with 8+ GB free, so we'll see if that helps.
CrustyMcLovin said:
The only time I have seen this occur is when my SD card was going bad or already dying. I just had another SD card fail so I don't think its all that uncommon. I believe that TWRP will create md5 files during the backup process, if you took the time you could probably use those to verify.
Click to expand...
Click to collapse
the card isn't going bad, and sometimes a nandroid to internal storage still goes funky.
if i try to verify the md5 before restoring, i get an error every time. what could that be a symptom of?
frescagod said:
the card isn't going bad, and sometimes a nandroid to internal storage still goes funky.
if i try to verify the md5 before restoring, i get an error every time. what could that be a symptom of?
Click to expand...
Click to collapse
What are you using to verify the md5 and what error are you getting?
Hei guys, I own a Chinese handphone. Tweaked it so much, soft bricked it numerous times, but I got the stock rom at my disposal anyway so it doesn't matter much. It's cheap so I can actually do some experiments or tested non Play Store, or even suspicious apps on it.
However, going back and forth to stock then reconfigure everything is rather tedious task to do.
I did installed a CWM recovery and did a full nandroid backup. But it's seem that CWM backup didn't overwrite the old one so when I do a second one it failed, saying I'm out of space? I still got about 2 GB on internal storage, and 8 GB on external storage. It's said my folder (I forgot which, it's /data if I'm not mistaken) don't have space left. This is one funny thing about my phone, it doesn't use the internal storage at all. I cannot move the apps to the internal storage as well, only to the external SD card.
I'm out of space probably also because I move so many app as system. This way when I do a factory reset I got all my updated apps within, without the need to reinstall it.
So, the questions :
Is there any way to make CWM to actually update a backup, instead of creating a new one? Which partition I should wipe from CWM if I want to create an updated backup? It is convenient to do the restore directly from CWM, but I cannot update the backup, with that space problem.
How about creating a full custom ROM flashable image of my phone on which I can save to my PC instead?
How about going on fetching the nandroid backup CWM generated? Is it flashable using SP Tool? But I can't find the files anywhere in my system.
Any help would be appreciated.
Thank you!
Found some stuffs on CWM backup.
I'll update this thread when I've worked it out.
I'm an idiot. I can actually save the CWM backup into the internal SD. It's visible on any file manager within the folder "clockworkmod".
Sorry I did have experience with CWM, but never use it for backup, only to flash patches.
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
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.