[Q] Clockworkmod recovery backup not working properly - General Questions and Answers

Hi gents. I am trying to restore my phone to a recent clockworkmod recovery backup but several of the latest backups won't restore the downloaded programs of the time, nor do they seem to be restoring the general Android settings. Older backups are working perfectly, however, and I can't think of any significant or unusual changes I made to the system that could stop it working properly. Also, I have been backing up and restoring the same way.
I'm using Revolutionary CWM v4.0.1.4, HTC ICS 4.0.4 (w/ older HBOOT for S-OFF), HTC Desire S.
I find this very strange, and unsettling that clockworkmod's backup may be unreliable. Has anybody experienced this?
Another thing, I have also been backing up the entire SD card data in the later backups (just copying to computer via card reader), thinking it may be best to restore backups with this data, but it seems to not make a difference whether this is done, or the data left as-is, or the card cleared. What's best practice in regard to the Android data that's put on the SD card?
My phone is up the creek. Help!?

i am having the same problem restoring CWM v4.0.1.4 backups on my galaxy s2: older backups restore perfectly and newer backups restore incompletely (some settings and SMSs, but no apps and no contacts).
i believe this is an issue with large nandroid images (containing >10,000 files) being unable to restore properly. this implies the backup itself is intact, luckily.
read this:
http://forum.xda-developers.com/showthread.php?t=1154892
to rebuild my phone i started by using unyaffs on my PC to access the files on the CWM nandroid image and restore my contacts, call logs, etc:
http://forum.xda-developers.com/showthread.php?t=1370349
you can find additional file locations listed in this thread:
http://forum.xda-developers.com/showthread.php?t=969650
i then used appextractor (available in the play store) to manually restore my apps and app data from the CWM nandroid image. some needed to be redownloaded.
it's a schlepp but better than losing everything entirely.
i've read that TWRP is a more reliable way to backup and restore. i'm certainly not using CWM again.
regarding your second question, the data on your internal and external SD card is irrelevant to the function of the OS, but some apps may rely on that data. for example large apps install on the SD card.

Thanks so much for that matey. I searched and searched but hadn't come across the 10,000 files limitation. How annoying!
Anyhoo, before I saw your post I ended up restoring the latest working backup and reinstalled apps, configured things, got the device mostly up to speed.. but there were some sentimental Messages I wanted to restore. I got that unyaffs exe, the 10,000 file fix one, and managed to extract the mmssms.db just fine..
But I soon learnt it seems to be a nightmare to get it back into ICS because the SQLite db is in full-vacuum mode or some such, meaning it is cached and rewritten to help avoid fragmentation or some such. So I overwrite the mmssms.db, set permissions and ownership, reboot, and it's overwritten with the current one. Argh. I tried clearing cache. Tried running SMS backup/restore apps while the 'good' mmssms.db was in place, but they seem to look at the db cache/temp data, not the mmssms.db.
For those facing my situation and want Messages from CWM/nandroid backups in ICS, I found a great tip just posted on one of the threads N-acetyltransferase linked;
RichAP said:
I did this yesterday using Titanium Backup for my SMS/MMS
You need to go into Preferences and check the *Migrate system data [Experimental] option
Then you go to More - Extract from nandroid backup
There it is listed as Dialer Storage
Click to expand...
Click to collapse
I had tried using TiBu to restore Messages from nandroid backup (no success), but Dialer Storage!? How annoying. Anyhoo it's sorted.
Then I quickly found a good alternative recovery and quickly bought the premium version of 4EXT. It's very good, but get this, it actually recovered my latest CWM recovery backup no drama, just like that! Ahh well I didn't need those hours of my life anyway. I've often thought the Desire S's codename Saga is rather apt.
In conclusion, TiBu looks damn good and 4EXT is a ripper. I'd recommend it however the Galaxy S2 support is apparently unconfirmed thus far. Maybe look into it nevertheless.
Thanks for the help dude.

Related

[Q] PLEASE Help

Hello everyone, for starters im a complete newb at rooting phones and have never before tonight so please excuse my ignorance. I just rooted my phone which went fine, downloaded titanium backup and backed up everything, and then moved a zip of m1 cm10 and gapps onto my ext sd card. then i followed a video on how to install these. i was running clockwork recovery and did a factory reset/clear. in the video, the next screen had an option for "choose zip from sd", all mine had was something like update from external so i clicked that and it brought up my sd card files, including the cm10 and gapps files. i clicked on them (i tried each more than once) and they both stgarted to install then said failed. Im literally here freaking out because none of the apps i downloaded to restore my stuff are on my phone anymore, and when i downloaded them from the play store they said i had not backed anything up. somebody please help me, im legitimately having a nervous breakdown because i lost everything and dont know what to do.
Ok first things first. What was the fail error that CWM produced? I dont understand what you mean by none of the apps you downloaded to restore your stuff are on the phone anymore. Where did they go? If you didnt delete them they should still be there. Did you boot up after the failed attempt, and are now at a factory state OS? Perhaps titanium isnt pointed to the correct location of the backups you made. Please provide more info.
Edit: Ok I misunderstood a point. The apps I take it are gone from the factory reset, but I still dont understand why the backup data cant be restored.
Sounds like CWM didn't flash. That sounds like stock recovery. Flash factory image via Odin, reroot, and reinstall CWM. Download an app called EZ Recovery from the market and follow the instructions. You will be fine.
Sent from my SCH-I535 using xda premium
Just a side note as far as using CWM goes:
I've noticed that with CWM, the backup file sizes are way too small. Hence a possible corrupted backup folder. TWRP seems to work better with our device as far as backups go.
It's always a good idea to check the size of a backup afterwards before proceeding with any risky procedures like low level flashing. Luckily there is always ODIN.
With my device backup sizes range between 2.0GB and 2.34GB.
tekrhino said:
Just a side note as far as using CWM goes:
I've noticed that with CWM, the backup file sizes are way too small. Hence a possible corrupted backup folder. TWRP seems to work better with our device as far as backups go.
It's always a good idea to check the size of a backup afterwards before proceeding with any risky procedures like low level flashing. Luckily there is always ODIN.
With my device backup sizes range between 2.0GB and 2.34GB.
Click to expand...
Click to collapse
You've got to remember that CWM backs up differently now. It backs up data separately in blobs in a different folder. So your backups in clockwork are naturally smaller. Also, I've heard nothing but bad things with TWRP on this device. I'd stay away from it and stick with non touch CWM.
mustbepbs said:
You've got to remember that CWM backs up differently now. It backs up data separately in blobs in a different folder. So your backups in clockwork are naturally smaller. Also, I've heard nothing but bad things with TWRP on this device. I'd stay away from it and stick with non touch CWM.
Click to expand...
Click to collapse
This!
apacseven said:
Ok first things first. What was the fail error that CWM produced? I dont understand what you mean by none of the apps you downloaded to restore your stuff are on the phone anymore. Where did they go? If you didnt delete them they should still be there. Did you boot up after the failed attempt, and are now at a factory state OS? Perhaps titanium isnt pointed to the correct location of the backups you made. Please provide more info.
Edit: Ok I misunderstood a point. The apps I take it are gone from the factory reset, but I still dont understand why the backup data cant be restored.
Click to expand...
Click to collapse
When I open titanium backup and try to restore, it tells me no backups have been performed. Before trying to flash cm10, I moved the backup to my external sdcard and it is still there, yet I still can't restore it and when I try to do something with the files on my card it says no application can perform this task. Ive gotten my contacts back through tha app I backed them up on so I'm at a loss for why tb Isnt working.
levibernhardt said:
When I open titanium backup and try to restore, it tells me no backups have been performed. Before trying to flash cm10, I moved the backup to my external sdcard and it is still there, yet I still can't restore it and when I try to do something with the files on my card it says no application can perform this task. Ive gotten my contacts back through tha app I backed them up on so I'm at a loss for why tb Isnt working.
Click to expand...
Click to collapse
Launch titanium and hit menu/preferences. From there you can change the backup location to wherever you moved it to and it should see them.
Also for your contacts... If you are planning on flashing roms do yourself a favor a migrate your contacts off your phone and on to Google. That way you just log back in to your Google account after a re flash and they are all resynced. Plus you can access them from anywhere at contacts.Google.com
Sent from here using this
Relentless D said:
Launch titanium and hit menu/preferences. From there you can change the backup location to wherever you moved it to and it should see them.
Also for your contacts... If you are planning on flashing roms do yourself a favor a migrate your contacts off your phone and on to Google. That way you just log back in to your Google account after a re flash and they are all resynced. Plus you can access them from anywhere at contacts.Google.com
Sent from here using this
Click to expand...
Click to collapse
Did this ^ in titanium and the files show up, but it still says there is nothing to restore.
Also, could someone tell me/point me to a good method of flashing M1 cm10 onto a us cellular gs3?
mustbepbs said:
You've got to remember that CWM backs up differently now. It backs up data separately in blobs in a different folder. So your backups in clockwork are naturally smaller. Also, I've heard nothing but bad things with TWRP on this device. I'd stay away from it and stick with non touch CWM.
Click to expand...
Click to collapse
I agree 100%, the non-touch version of CWM works perfectly. I could care less about touch/non-touch/color of the app etc. ALL I care about is the capability to do a sucessful restore & CWM has never failed me for that.
I did a restore from it last night & it worked perfectly. The ONLY thing I have ever had to do after a CWM restore is clear data in GMAIL to get it to send.

Restoring Back Up

Well since this was my first root I guess I made a mistake or maybe not?
So this is the case :
I have an HTC One S (Rooted using SuperSu Method)
What I did for backup is just copy all the content from the phone (in hard drive mode) to a folder on my pc (which ended up being around 7gigs)
My question is how do I restore all that data\pics\apps\profiles back to my phone?
(Tried to copy past it back into the phones SD-Card and rebooting, The phone doesn't recognize any of the data)
Any way to actually make this work? or is it a lost cause?
Thanks for the help! :laugh:
As far as apps and their data goes, only some info is saved on the sdcard, the rest is saved on the devices internal memory.
Only restoring the stuff saved on the SD card aint gonna bring back any apps. They need to be reinstalled properly.
Goatshocker said:
As far as apps and their data goes, only some info is saved on the sdcard, the rest is saved on the devices internal memory.
Only restoring the stuff saved on the SD card aint gonna bring back any apps. They need to be reinstalled properly.
Click to expand...
Click to collapse
How about all the Contacts \ Messages and ect?
Because I have all the files on my PC (Exactly the same files that have been on the phone before the ROOT\Unblock)
Can I recover those back to the phone somehow?
Messages and contacts are stored on internal memory, unless you export them.
You dont have access to anything except /sdcard/ through the PC, unless you use ADB.
edit: What I mean is, if you have only backed up /sdcard/ (which seems to be the case), you have lost everything on the internal memory (such as messages and contacts etc).
Goatshocker said:
Messages and contacts are stored on internal memory, unless you export them.
You dont have access to anything except /sdcard/ through the PC, unless you use ADB.
Click to expand...
Click to collapse
So basically even tho I copied all the content from the phone itself to the pc, All I copied is squat.
All the raw data I get is pictures.
So no encrypted data can be found on the storage partition and I have to just start over from scratch?
And the next time I root or flash, just use Recovery backup?
You didnt copy all the content. You only copied what was stored on the /sdcard/ (which is more or less the only thing you have access to without root).
Theres a very slim amount of data android uses on the sdcard, unless the user specifically tells it to.
Next time you flash, you should back up all your apps you want to save with for example titanium backup (requires root, which you now have), save all the contacts to the sim card, and export all messages.
Then after you have wiped and flashed a new rom, just restore the backups with titanium backup again, and import contacts from sim.
The backup/restore in recovery backups/restores the WHOLE system, so when you restore it it will be exactly like the way it was when you made the backup. (edit: to clarify, if you flash a new rom, then restore a backup made on another rom, you will return to that rom the backup was made on)
Goatshocker said:
You didnt copy all the content. You only copied what was stored on the /sdcard/ (which is more or less the only thing you have access to without root).
Theres a very slim amount of data android uses on the sdcard, unless the user specifically tells it to.
Next time you flash, you should back up all your apps you want to save with for example titanium backup (requires root, which you now have), save all the contacts to the sim card, and export all messages.
Then after you have wiped and flashed a new rom, just restore the backups with titanium backup again, and import contacts from sim.
The backup/restore in recovery backups/restores the WHOLE system, so when you restore it it will be exactly like the way it was when you made the backup. (edit: to clarify, if you flash a new rom, then restore a backup made on another rom, you will return to that rom the backup was made on)
Click to expand...
Click to collapse
Got it
I actually found some encrypted data such as : Whats up message history, Some Contacts, Specific apps.
And I recovered all my contacts VIA my google account.
Only thing lost is the applications, which I will reinstall in like 30 minutes.
Anyhow I am quite happy I got into the rooting business, Already feel the different abilities and the uncovered raw code + new line of root supported apps waiting to be savaged by me.
Thank you for the help anyways (and the quick reply as well)
And I think the original ROOT tutorial post should have a step which is a "back-up step" which explains how to back up most of the info before rooting, and the ability to back up with root.
Cheers!

[Q] Best use of Titanium Backup

Hi,
I need to do a factory reset (to see if it solves a problem that Asus could not solve) and in anyway I read it's safer to wipe data before sending to factory for repair.. So I'd like to make a full backup before this wipe and before the sending to repair..
I installed free Titanium backup (my tablet is rooted), but I'm confused on what I should do before doing the reset and the tutorials I found on Titanium even confused me more..(if you're aware of a nice tutoriel, link would be welcome, because I found none very explicit on xda and even on the web..)
-first, should I use the Asus tool for backup or Titanium ?
- Should I perform a full backup of apps only or apps+system ? I read that system restore could create issues in case restore is not done on same firmware, and I don't know with which FW my tablet will come back from repair.. so should I use apps+system anyway, or make 2 backups (apps first then system or vice versa ?) I'd prefer to restore my tablet as clsoe as it is today, even if possible with bluetooth pairs and wifi connections..
-Should I backup manually my personal files (videos ,various docs, pictures,..) before using Titanium ? (for instance to save space and make nbackups smaller?) If yes, how do we know which folders are backuped up by Titanium and which are not ?
- My sdcard is already largely used with only a few GB left. Can I ask Titanium to save directly to a PC ? Or should I use another sdcard (but then, what will happen to apps installed on sdcard ?) ?
Thanks a lot for your hints.
Ricorico94
There are several different options for you to choose from but I will share the way I usually back up my tablet. I flash different ROMs frequently and have had to use backups quite a bit.
I usually use Titanium Backup to backup everything but only restore non-system apps and data. You're right that restoring system data can result in problems if restoring to different ROMs, not necessarily firmware. It depends on how much the firmware has changed. Since there might be big enough changes that it might screw everything up then I'd avoid restoring system apps and data. If your tablet is backed up to Google, it will sometimes keep the WiFi and Bluetooth pairings and restore them once you log back into your Google account. Not always though. Also I'm not sure that the free version of Titanium Backup can save any place other than an SD card. The paid version can save to Dropbox and Google Drive.
If you're sending your tablet in for repair, you should move all of your personal files to your computer or SD card, deleting them off the tablet. At least, that's what I'd do.
There is one more option which would make saving a lot easier and that is if you have a custom recovery installed like TWRP or CWM you can create a Nandroid Backup of everything, System, Data and all. With all your pictures, etc the file would be huge but you could move that to your computer and restore it when your tablet comes back. That would keep an exact copy of your system and replace whatever ASUS does to it with what you currently have. If I wanted to keep my tablet as close to how I set it up, this is what I would do. Of course, your tablet has to be rooted and unlocked to do so.
wrynn7 said:
There are several different options for you to choose from but I will share the way I usually back up my tablet. I flash different ROMs frequently and have had to use backups quite a bit.
I usually use Titanium Backup to backup everything but only restore non-system apps and data. You're right that restoring system data can result in problems if restoring to different ROMs, not necessarily firmware. It depends on how much the firmware has changed. Since there might be big enough changes that it might screw everything up then I'd avoid restoring system apps and data. If your tablet is backed up to Google, it will sometimes keep the WiFi and Bluetooth pairings and restore them once you log back into your Google account. Not always though. Also I'm not sure that the free version of Titanium Backup can save any place other than an SD card. The paid version can save to Dropbox and Google Drive.
If you're sending your tablet in for repair, you should move all of your personal files to your computer or SD card, deleting them off the tablet. At least, that's what I'd do.
There is one more option which would make saving a lot easier and that is if you have a custom recovery installed like TWRP or CWM you can create a Nandroid Backup of everything, System, Data and all. With all your pictures, etc the file would be huge but you could move that to your computer and restore it when your tablet comes back. That would keep an exact copy of your system and replace whatever ASUS does to it with what you currently have. If I wanted to keep my tablet as close to how I set it up, this is what I would do. Of course, your tablet has to be rooted and unlocked to do so.
Click to expand...
Click to collapse
Hi,
Thanks a lot for this advice. Do you know if I can still make 2 separate backups, so that I could use system backup if there's no FW change ?
Regarding the TWRP custom recovery, I understood that since I am already with FW 10.4.4.25 (android 4.1.1) and only rooted, there's no way to install customer recovery. Did I understood properly, or is there a way to downgrade to previous versions first, istall custom and upgrade again back to current FW ?
What do you mean by "tablet backed up to Google" ? I have "save my datas" checked under "backup" menu of parameters, but is there a way to check that there's indeed something in their servers already ?
br,
Ricorico94
You could make as many backups as you wanted. Titanium Backup allows you to restore whatever you want it to so you really only have to make one backup. You can restore everything but the system apps and data or everything. You can even use it to uninstall or freeze what you're not using (as long as it's not an integral part of the FW of course). It's not an all or nothing deal. I would still move all of your personal data to a computer or SD card so nothing happens to it.
My understanding is that installing CWM or TWRP require your device to be unlocked using an app that is provided through the ASUS website. Just being rooted isn't sufficient. If you don't want to unlock your device then you're stuck with using the Titanium Backup method. Just make sure it is saving your apps to an external SD card and not the internal one.
And yes, I was referring to the setting that you already have checked about Google backing up your data. It doesn't always restore everything though so you might have to pair everything again anyway.
ricorico94 said:
Hi,
Thanks a lot for this advice. Do you know if I can still make 2 separate backups, so that I could use system backup if there's no FW change ?
Regarding the TWRP custom recovery, I understood that since I am already with FW 10.4.4.25 (android 4.1.1) and only rooted, there's no way to install customer recovery. Did I understood properly, or is there a way to downgrade to previous versions first, istall custom and upgrade again back to current FW ?
What do you mean by "tablet backed up to Google" ? I have "save my datas" checked under "backup" menu of parameters, but is there a way to check that there's indeed something in their servers already ?
br,
Ricorico94
Click to expand...
Click to collapse
I don't think it is a good idea to install a custom recovery if you are about to send the tablet to Asus - I assume for a warranty repair. You would have to unlock your bootloader and that negates your warranty. So just forgettaboutit.
Google backs up some of your data: Calendar and contacts mainly, but also all the apps you have downloaded or bought from the Play Store.
But it is much faster to restore apps with Titanium instead of downloading them from the Play Store.
So backup apps and data in TiBu and move the backup to your PC.
I don't quite understand why you want to backup system data. It's always potentially disruptive to mess with system data yourself. And you are on a pretty old rom and bootloader - so you're due for an update anyway.
Pictures, videos etc, I would just move to an external drive/card or your PC.
When you got everything backed up, do a Factory Reset. That will wipe your data partition.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Thanks to both of you for your help!
berndblb said:
I don't think it is a good idea to install a custom recovery if you are about to send the tablet to Asus - I assume for a warranty repair. You would have to unlock your bootloader and that negates your warranty. So just forgettaboutit.
Click to expand...
Click to collapse
You're right. I was asking this for future, when tablet comes back from repair: at that time, I might want to have a stronger debug/backup using a custom recovery (at least that's what I understood it's very helpful at): I'm soon at warranty end, so I can wait expiration.
It's a good news that the unlock tool of Asus can still be used to allow installation of custom recovery. I'll need to read more on how to do it, etc.
Thanks again !

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.

Full(!) backup via ADB

Is there a way to perform a full backup via ADB?
Like a script or a line which creates a flashable full copy of one or all of the phones filesystems to PC.
Not(!)
adb backup -all
which backups merely system settings and not a migrate app which a) does not perform a full backup as it omits random files and b) works internal and neither TWRP backup-tool which only works internal.
andy01q said:
Is there a way to perform a full backup via ADB?
Like a script or a line which creates a flashable full copy of one or all of the phones filesystems to PC.
Not(!)
adb backup -all
which backups merely system settings and not a migrate app which a) does not perform a full backup as it omits random files and b) works internal and neither TWRP backup-tool which only works internal.
Click to expand...
Click to collapse
It can backup/restore your data, it can not backup your ROM/firmware, if you are not rooted, you will only be able to backup/restore user data, you will not be able to backup/restore any of your system apps/system app data, or any other part of system data and system settings, that will require rooting the device.
If you want a complete backup of the operating system and everything else on the device, you will need TWRP.
Sent from my SM-S767VL using Tapatalk
I am rooted. I am running TWRP.
I can't copy large amounts of data from inside the phone because something is buggy; this includes TWRPs backup-function. Copying works fine if and only if controlled by connected PC.
andy01q said:
I am rooted. I am running TWRP.
I can't copy large amounts of data from inside the phone because something is buggy; this includes TWRPs backup-function. Copying works fine if and only if controlled by connected PC.
Click to expand...
Click to collapse
Try flashing a newer or slightly older version of TWRP, it might fix the bugs that you are experiencing in TWRP. Is TWRP set to store your backups on external? Or is it set to store backups on your internal storage? Storing backups in internal takes up too much space, it's best to store backups on external.
As for adb...
https://forum.xda-developers.com/galaxy-nexus/guide-phone-backup-unlock-root-t1420351
There are several switches that can be used to be specific about what you want backed up and what you don't.
Sent from my SM-S767VL using Tapatalk
I updated to TWRP 3.4.0-0 (newest version) and backup from within TWRP still always fails between 20% and 30%. The last 30 to 40 backups failed and the only one that did finish to 100% is still broken and can't be read.
I would be thinking hardware-failure if not for the thing that copying anything from within the phone is super buggy, but copying when controlled from a PC works completely fine.
I guess I'll try the simple adb backup with some more parameters and then move on.
andy01q said:
I updated to TWRP 3.4.0-0 (newest version) and backup from within TWRP still always fails between 20% and 30%. The last 30 to 40 backups failed and the only one that did finish to 100% is still broken and can't be read.
I would be thinking hardware-failure if not for the thing that copying anything from within the phone is super buggy, but copying when controlled from a PC works completely fine.
I guess I'll try the simple adb backup with some more parameters and then move on.
Click to expand...
Click to collapse
How much free space do you have on internal storage? If there is less free space than your system, data and cache partitions combined, that may be why it is failing. Clear some space. I say this because when the backup is being created, the data that you want included in your backup is being read bit by bit from their partitions and then written into cache bit by bit and then it is read from cache bit for bit then it is written to its final storage location bit for bit. If there is not enough space to write it all into cache before writing it to its final location, it will fail.
The same rule applies when you move files from internal to external or vice versa, the same rule also applies when you are extracting files. It requires enough free space to write that data into cache before it goes where it is actually going.
Sent from my SM-S767VL using Tapatalk
Oh come on, I appreciate your efforts, but I felt being treated like a little child from your first answer and this tops it very much. Backup fails at 20-30% with 45GB of free internal space, external MicroSD removed and <10GB of data to backup. Aside from that I doubt that if a lack of free space causes the backup to fail, that this will not cause an error message to tell me what caused the fail.
By now I did the backups that I could backup:
That is I manually pulled all folders I deemed important.
Then I used "adb backup -apk -shared -all -system" which created a 7GB backup.
I also used the buggy migrate-app and ticked all boxes to get a 3GB backup.
And I used Googles cloud-service-backup.
In the end plenty of data and configurations were lost; worst is probably the Corona Warn App data as this can't be remedied.
andy01q said:
Oh come on, I appreciate your efforts, but I felt being treated like a little child from your first answer and this tops it very much. Backup fails at 20-30% with 45GB of free internal space, external MicroSD removed and <10GB of data to backup. Aside from that I doubt that if a lack of free space causes the backup to fail, that this will not cause an error message to tell me what caused the fail.
By now I did the backups that I could backup:
That is I manually pulled all folders I deemed important.
Then I used "adb backup -apk -shared -all -system" which created a 7GB backup.
I also used the buggy migrate-app and ticked all boxes to get a 3GB backup.
And I used Googles cloud-service-backup.
In the end plenty of data and configurations were lost; worst is probably the Corona Warn App data as this can't be remedied.
Click to expand...
Click to collapse
I can't help how you feel and you are entitled to feel however you wantl, but, at the end of the day, it is still only how you "feel", that doesn't make anything true or false. Just saying.
I didn't post anything to make you feel any kind of way, I was merely attempting to be as informative as I could because one can never gauge what someone else knows or understands before your interaction with them.
I've seen some other issues with TWRP backups failing and/or being unreadable, the solution is not a singular solution, there are several reasons why it fails and several fixes to solve it. Have you tried doing some google searches for:
"TWRP backups fail at 40%"
That pulls up some information that might apply or may not, you'll just have to peruse what you find to see if any of seems like it might be what you are experiencing and then try some of the solutions that others have tried. You might get lucky, you might not.
I'm more interested in helping you "find" an answer than whether I "know" the answer or "tell" you the answer.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Have you tried doing some google searches for:
"TWRP backups fail at 40%"
Click to expand...
Click to collapse
Yeah, I've done that for an hour or so before starting a thread - obviously b/c that has the chance for much quicker solutions and seems less work for me.
Also I did try several solutions like update TWRP, try smaller backups (the small ones do usually work) and so on. I think I did mention that I tried this over 40 times.
Some of the solutions suggest installing another ROM first, (apparently the ROM can cause Read-errors within TWRP?) but obviously I want the full backup before I try another ROM so I tried other methods to backup my data.
Also moving data via adb has worked completely without fail so far, so I wanted to try that path.
By now I can tell that TWRP full backup doesn't work on other ROMs either.
andy01q said:
Yeah, I've done that for an hour or so before starting a thread - obviously b/c that has the chance for much quicker solutions and seems less work for me.
Also I did try several solutions like update TWRP, try smaller backups (the small ones do usually work) and so on. I think I did mention that I tried this over 40 times.
Some of the solutions suggest installing another ROM first, (apparently the ROM can cause Read-errors within TWRP?) but obviously I want the full backup before I try another ROM so I tried other methods to backup my data.
Also moving data via adb has worked completely without fail so far, so I wanted to try that path.
By now I can tell that TWRP full backup doesn't work on other ROMs either.
Click to expand...
Click to collapse
Flash an older version or newer version of the exact same ROM as what you have but not doing any of the wipes, just flash ROM and that's it. This is called a "dirty flash", it will not wipe any of your data unless you specifically tell it to.
Alternatively, you could just do a backup via TWRP without including system and boot, just data and maybe cache(cache isn't necessary and might even cause issues if you restore it). Then, if you need to restore, flash the ROM the backup was created from then reboot to system, then boot back into TWRP then use "advanced restore" in TWRP to restore data and cache, this "should" give the same result as including system and boot in the TWRP backup along with data then restoring everything from that backup.
Also, can you post a copy of your recovery logs to some hosting site then link it here, someone here might be able to see something in the log that needs addressing, preferably the logs from the failed backup processes, if they errored in different ways, post the differences also. You should be able to find your logs if you haven't wiped the device.
Sent from my SM-S767VL using Tapatalk

Categories

Resources