So Ive Searched around the forums, and bing with no luck..
Here's my questions -
What is the difference or significance of " Create image zip " in CWM versus just making a backup ?
Is one of the other a "Nandroid backup", or both ?
Sorry to ask what's probably a silly question, but I've been wondering about this. Luckily, So far, I haven't had to restore any backups. I've not done alot of flashing and this is partly why. I'm not sure if my backups are exactly what I would need if I ran into any sort of problems.
Any responses would be appreciated, Thanks.
From what I can understand from Google searching, I think that an image.zip simply saves a copy of the system you're running. This means non of your personal data will be backed up. It's meant for development use, so once a kernel or rom is set up correctly, it can be saved and shared among the community simply for rom tweaking purposes.
An actual backup saves an image of the system partition along with the data partitions. It differs because your personal data is saved along with your current rom system image.
Making a nandroid is using the backup option, and that's exactly what you need. If you have any problems you simply have to restore the backup and everything comes back the exact way it was when you backed it up. Sometimes I flash a kernel that doesn't play nice with my phone, and using nandroid restores have saved me tons of time getting things back to normal.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
From what I can understand from Google searching, I think that an image.zip simply saves a copy of the system you're running. This means non of your personal data will be backed up. It's meant for development use, so once a kernel or rom is set up correctly, it can be saved and shared among the community simply for rom tweaking purposes.
An actual backup saves an image of the system partition along with the data partitions. It differs because your personal data is saved along with your current rom system image.
Making a nandroid is using the backup option, and that's exactly what you need. If you have any problems you simply have to restore the backup and everything comes back the exact way it was when you backed it up. Sometimes I flash a kernel that doesn't play nice with my phone, and using nandroid restores have saved me tons of time getting things back to normal.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
So creating an image zip would potentially backup everything other than the /data partition then ? I sort of remember making a backup both ways, and the zip was somewhat smaller - so that would make sense.
cjmcsw87 said:
So creating an image zip would potentially backup everything other than the /data partition then ? I sort of remember making a backup both ways, and the zip was somewhat smaller - so that would make sense.
Click to expand...
Click to collapse
That's basically it, however there are some partitions that don't get touched anyway such as your recovery partition.
I would expect your full backup to be larger, how much larger depends on all the app data you have. Anyways, I wouldn't flash an image.zip in any kind of restore attempt.
Sent from my SCH-I535 using Tapatalk 2
Thanks for the response that answers my questions.
Sent from my SCH-I535 using xda app-developers app
Related
I typically use CWM to back up my phone before flashing a new ROM.
I have been reading about Nandroid and dont see an advantage to using that over CWM, however most the devs say to use Nandroid to back up your phone.
Is there a reason/advantage to use Nandroid over CWM that I'm not seeing?
Technically, Nandroid does a little bit better job of backing up absolutely everything, and it would be a good idea to have at least one full, nice backup of your phone for if things go horribly, horribly wrong.
That being said, I just use CWM to backup everything every time I'm going to flash a new ROM, and I never have problems. (I'm a habitual ROM changer) You should be ready to flash CWM with Odin in case your recovery gets corrupted, but I don't see any reason not to trust it.
I thought nandroid backup was backup in cwm. I learn new things everyday. Maybe that's my md5 mismatch problem when I try to restore a backup.
Sent from my SAMSUNG-SGH-I727 using xda premium
GooSe275 said:
I typically use CWM to back up my phone before flashing a new ROM.
I have been reading about Nandroid and dont see an advantage to using that over CWM, however most the devs say to use Nandroid to back up your phone.
Is there a reason/advantage to use Nandroid over CWM that I'm not seeing?
Click to expand...
Click to collapse
Using CWM to back up your phone is a nandroid backup. Are you referring to using Rom Manager to backup your roms? If so, it is still creating a nandroid backup. View the screen as your back up begins and you will see that it is creating a nandroid backup.
Im asking myself the same question ... I use this backup methode: http://forum.xda-developers.com/showthread.php?t=1390771
- Is it also creating a nondroid backup ?
- When I look at my backupfiles, how can I check it ?
- as this backup does not seem to backup all files ... is there another backup doing a real image or at least
Pls see the jpg of the .zip I made from the CWM backup dir on SD card...
gggg said:
Im asking myself the same question ... I use this backup methode: http://forum.xda-developers.com/showthread.php?t=1390771
- Is it also creating a nondroid backup ?
- When I look at my backupfiles, how can I check it ?
- as this backup does not seem to backup all files ... is there another backup doing a real image or at least
Pls see the jpg of the .zip I made from the CWM backup dir on SD card...
Click to expand...
Click to collapse
That certainly looks like an official nandroid backup to me.
Sent via Tapatalk 2
Backups
Just a word of caution that some of the other Senior Devs I have talked to about this say to stay away from using Rom Manager for things if you can. It is better and safer to boot into recovery and do things via CWM or TWRP or whatever your Recovery of choice is...
I know Rom Manager might be good for somethings but trusting your backup to anything other than CWM is not something I would do.
Also, Nandroid Backup and the Backup setting in CWM is the same thing.
Keep in mind it won't backup internal storage. "emmc"
Boot
Recovery
System
Data
Cache
Sent from my SAMSUNG-SGH-I727 using xda premium
i have little Linux knowledge ... is there a way to copy all the missing directories / partition ... eg. using ADB / busybox ???
Scott originally said he liked TWRP better than CWM, so I posted this in his thread (sorry Scott, didn't mean to clutter)....
Ok so here are my concerns... I've always used CWM since my last phone (orig droid inc) so I have been using it on this phone. When I first rooted and installed it I made a backup of my stock rom (on ext SD card) and after I installed this ROM I made a backup of it before installing KCM and dirty tweaks (on internal SD card) (I wanted to see if there was a difference in speed saving to ext vs internal and it seemed internal was faster). At the time I didn't know about blobs and didn't know that I couldn't just move my backup from internal to external (at least I'm assuming I can't), and I like it better when the backups are more portable. Does TWRP have more portable backups than CWM?
Also, is there a way to convert CWM backups to TWRP or would I have to load my backups with CWM then use EZ Recovery to flash TWRP and then re-save them as TWRP? Or would it just be better to keep those 2 backups as CWM (since I can just use EZR to reflash CWM) and just use TWRP for new ones?
Finally, what about Kinda Crap Mods... Since using it, i'm kind of liking it but it doesn't seem to be supported with TWRP, right? But then again I guess I could just use EZ Recovery to flash CWM to install KCM and then flash back to TWRP and there shouldn't be any issues right?
Haha sorry it's so long but I think it's useful info
Click to expand...
Click to collapse
Any answers to my questions above?
So what do you guys like/dislike about TWRP/CWM? Which one works better for you and why? I know it's all a matter of opinion and preference but examples would help others decide which one they want to try.
If you want 100% (for the most part) stability - use CWM.
If you want to play with the newest, easier to navigate recovery, which has been reported to not wipe properly - use TWRP.
I exclusively used TWRP on my Nex. On my S3, I have little bits of other nandroids creeping into my restores - if that makes sense. For example, restoring a TW backup after running CM -- I would find CM apps in my app drawer. Additionally, my phone was running like poo. Went to restore a different backup, only to find they were all corrupted.
That ended my dance with TWRP on the S3. Just MY results....
Sent from my SCH-I535 using Tapatalk 2
I am used to CWM so I don't really think its that difficult to navigate. The only thing that is new for me are these silly blobs... As stated above I did a backup to internal SD and a backup to external SD to see which one is faster, but now I just want to have both of them on my external but with these blobs i'm not sure if that is possible is it?
I've used Clockwork recovery since my OG Droid days, and its never failed me so i've always stuck with it. Never had any major issues with it or any issues at all while using it.
But you have to realize a lot of the 'issues' people post are user error and not the recovery itself. i am NOT calling out anybody, but its true, most errors are user errors, how else could something work perfectly fine for 999 people and only mess up for 1 person.
I used this touch based cwm on my gnex and loved it, it uses Swype gestures and the dev has ported it to the sgs3.
http://rootzwiki.com/index.php?/topic/32975-Touch-Based-ClockworkMod-Recovery
Neverendingxsin said:
I've used Clockwork recovery since my OG Droid days, and its never failed me so i've always stuck with it. Never had any major issues with it or any issues at all while using it.
But you have to realize a lot of the 'issues' people post are user error and not the recovery itself. i am NOT calling out anybody, but its true, most errors are user errors, how else could something work perfectly fine for 999 people and only mess up for 1 person.
Click to expand...
Click to collapse
+1. Have always used cwm an has always done the job.
Sent from my SCH-I535 using xda app-developers app
In Clockwork 6.0.1.2 you can change the backup format to tar to eliminate the "blobs".
Backup and Restore > choose backup format
Not sure about lower versions.
grin0048 said:
In Clockwork 6.0.1.2 you can change the backup format to tar to eliminate the "blobs".
Backup and Restore > choose backup format
Not sure about lower versions.
Click to expand...
Click to collapse
What are the blobs even for?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
What are the blobs even for?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
the blobs folder is where 99% of your data is stored. the reason its stored there is so when you make more than one backup it won't backup data that it already has. Its a way to save space, so instead of having a bunch of huge backups, it'll only backup data that has either changed or was never there. Just don't EVER mess with the blobs folder.
Neverendingxsin said:
the blobs folder is where 99% of your data is stored. the reason its stored there is so when you make more than one backup it won't backup data that it already has. Its a way to save space, so instead of having a bunch of huge backups, it'll only backup data that has either changed or was never there. Just don't EVER mess with the blobs folder.
Click to expand...
Click to collapse
Aight, here's a couple more questions:
1) Why doesn't CWM 6.x properly date the backups? All mine end with the year 1970. My last device, Droid Incredible, dated CWM backups properly. Is renaming them fine in relation to the blobs?
2) Should I only delete backups via CWM since they would theoretically delete the blob files corresponding to them?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Aight, here's a couple more questions:
1) Why doesn't CWM 6.x properly date the backups? All mine end with the year 1970. My last device, Droid Incredible, dated CWM backups properly. Is renaming them fine in relation to the blobs?
2) Should I only delete backups via CWM since they would theoretically delete the blob files corresponding to them?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Absolutely yes on #2. That's what I came in here to say.
CWM hasn't dated a backup correctly in who knows how long. Lol.
And I know scrosler loves TWRP (and we all love scrosler and CleanROM) but I've seen other devs mention the same kind of thing I said about TWRP -- as well as other users.
I personally prefer TWRP, so the fact that I'm recommending CWM means I don't use the former for a reason.
Finally, don't worry about moving backups. Just restore the ones you have on internal, make a new backup to external, then delete the internal one from recovery. Bye blobs, hello sdcard.
Sent from my SCH-I535 using Tapatalk 2
TWRP is a faster and easier recovery, the only bug I have encountered is the faster of my backup being incorrect unless I set a name. I perfer the touch and simplicity of TWRP.
Sent from my Cocaine White S3.
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.
Here is a screen shot of my cwm folder : /sdcard/clockworkmod/backup
can anyone tell me what they are for and why the dates are from 1970? can I delete them? the 4 files are taking up over 6.5gb of my internal storage.
thanks
Those are nandroid backups that you do in recovery. I use TWRP recovery which supports custom naming of backups. Thanks helps easily distinguish one backup from another. What I know about CWM is that it does not record dates when you backup. Unless there is an option to name backups like there is in TWRP, that's the way it is. Six GB looks about right for the four backups. You can delete any that you want but just know you're essentially deleting whatever "safe" rom you have backed up.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Those are nandroid backups that you do in recovery. I use TWRP recovery which supports custom naming of backups. Thanks helps easily distinguish one backup from another. What I know about CWM is that it does not record dates when you backup. Unless there is an option to name backups like there is in TWRP, that's the way it is. Six GB looks about right for the four backups. You can delete any that you want but just know you're essentially deleting whatever "safe" rom you have backed up.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
ok. but how do i know which is the oldest/newest?
cmegalodon said:
ok. but how do i know which is the oldest/newest?
Click to expand...
Click to collapse
Using your file manager (es explorer right?) there should be a Properties tab if you long press any of those folders. I'm willing to guess it's already in order from oldest to newest going left to right based on the naming scheme: "year-month-day" and the second part looks like "hour-minutes." However, you can tell via your file manager.
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