Develop Bugs

Titanium Backup: Restore app data from zip file?

I have downloaded an app + data (so it seems), from a friend. He made a backup for me and told me I could restore it using Titanium Backup.
It's a zip file and it contains a .tar.gz of the data, a .apk.gz (app) and a .properties file.
The .properties file seems to contain Titanium Backup information.
So I assume there should be some way of importing this zip file using Titanium Backup. But I can't find that option.
What I can find is "Backup" (which creates a backup of an app and stores it *somewhere*) and "Restore", where I can't specify a path or anything.
How can I restore the data inside this zip?

Extract that .zip file to /sdcard/TitaniumBackup/ folder. If you installed app which you want to restore go to Titanium Backup app and just restore it :good:

D0GuKaN said:
Extract that .zip file to /sdcard/TitaniumBackup/ folder. If you installed app which you want to restore go to Titanium Backup app and just restore it :good:
Click to expand...
Click to collapse
Can someone please help me? I have all of my backed up info on Google Drive from TB. I moved that info from Google to my phone and have tried to batch restore, but it keeps showing 0 files. Please help as I have a lot of apps and data backed up and I don't care to start over. I purchased the TB Pro app for just such an occasion and now I can't use it.

SmoothTrickle said:
Can someone please help me? I have all of my backed up info on Google Drive from TB. I moved that info from Google to my phone and have tried to batch restore, but it keeps showing 0 files. Please help as I have a lot of apps and data backed up and I don't care to start over. I purchased the TB Pro app for just such an occasion and now I can't use it.
Click to expand...
Click to collapse
Did you solve your problem?

buu1152 said:
Did you solve your problem?
Click to expand...
Click to collapse
No. I never received a response so I just gave up and started over.

D0GuKaN said:
Extract that .zip file to /sdcard/TitaniumBackup/ folder. If you installed app which you want to restore go to Titanium Backup app and just restore it :good:
Click to expand...
Click to collapse
This works indeed.
I selected a batch operation for backing up apps and system data. Downloaded it via the TB Webserver and thought I was okay.
Tried restoring by uploading it to my Nexus via TB Webserver anddd it's gone. Not in the Titanium Backup app, nor to be found on the Nexus with a file browser.
Uploaded the zip manually using an usb cable to the emualted sd andddd no,option in Titanium Backup to say "its here!".
Downloaded an unzip thingie in the Play Store, unzipped the shizzle and let the files in the zip -one level down- being unpacked in the TitaniumBackup folder.
Restarted TB and yay, it can see again. Batch restored everything and... it works. Kinda. Stuck on Swiftkey as we speak. But this is the best I could come up with.
Sigh.

1. Is there any method to update the apk files stored in the zip file with newer version ?
2. How can we delete /update the backup apks with newer version?

rohitshakti said:
1. Is there any method to update the apk files stored in the zip file with newer version ?
2. How can we delete /update the backup apks with newer version?
Click to expand...
Click to collapse
There may be a better way to do this, but somewhere in Preference you can tell it how many backups to keep. I think the default is "All". Set it to 1 and that should do the trick.

Problem with Nandroid backup empty folder

HI, i got this problem since i update to 4.2 (or i notice just after update) :
i made one nandroid backup in 4.1.2 and 2 backup in 4.2, but when i enter in clockworkmod/backup i can see only the files from old 4.1.2 backup.
New backup really exist because i can restore it from recovery! but no way to see the files or directory under /sdcard/clockworkmod/backup ...what is the problem? to browse folders i use root explorer, and also in windows7, but i always see only the old backup directory i made on 4.1.2... now deleted it, but no changes, now the backup folder is empty...
any ideas/solution?
thanks!

CrashV5 said:
HI, i got this problem since i update to 4.2 (or i notice just after update) :
i made one nandroid backup in 4.1.2 and 2 backup in 4.2, but when i enter in clockworkmod/backup i can see only the files from old 4.1.2 backup.
New backup really exist because i can restore it from recovery! but no way to see the files or directory under /sdcard/clockworkmod/backup ...what is the problem? to browse folders i use root explorer, and also in windows7, but i always see only the old backup directory i made on 4.1.2... now deleted it, but no changes, now the backup folder is empty...
any ideas/solution?
thanks!
Click to expand...
Click to collapse
/sdcard is a symlink the files are actually stored at /data/media/0. The new CWM bacups should be at /data/media/clockworkmod/backup

[Q] Problem with nand bakcup

Hello
My problem is that I downloaded the nand stock rom from the thread and extracted it and tried to put it in the clockworkmod\backups folder and I think it was ok (not sure) but by mistake I deleted all of backups (the stock and the one i created) and I tried to copy it again and create another one but I noticed that there never 2 backups.
The one that I created I can see only from the restore option in recovery and not in the folder ( I used to see it in the folder ..) and the stock one I can see in the folders but not in the restore option.
Should it be like this ? Am I doing something wrong ?
How can I restore that stock backup if I cant see it ?
I'm on ordroid 9 with TWRP recovery.
And the stock one gets in ZIP but i extracted it and copied as folder.
Thanks in advance , I'm afraid to flash new version.

That's because you didn't put it into clockworkmod>backup folder in the sd card and btw you don't extract anything .....every nandroid backup must have 5 zip files in it (don't extract it) and should be named as the date and time it was created

The folder should be like this
Clockworkmod\backup\date & time folder\backup files

donhashem.dh said:
That's because you didn't put it into clockworkmod>backup folder in the sd card and btw you don't extract anything .....every nandroid backup must have 5 zip files in it (don't extract it) and should be named as the date and time it was created
Click to expand...
Click to collapse
I know :\
I extracted the stock backup folder from the zip . not the content in backup.
Forgot the part about renaming, that actually might be the case.
Thanks both of you, I'll try it.

[Q] Extracting backup file

I have a backup file on my sd card from my old evo. The phones broken so i can't restore the backup. I wanted to pull some files out but I don't know how to go about doing it. I started making an emulated version of the phone but I'm not sure I'll be able to restore the backup in the emulated version. Any help would be great.

Put the file in your new phone and use a program like Nandroid Manager to extract what you need.

Captain_Throwback said:
Put the file in your new phone and use a program like Nandroid Manager to extract what you need.
Click to expand...
Click to collapse
Great. Thank you.

TWRP can't recognize backup folder name

My phone is GT-N7105 (Samsung Note 2)
=============SHORT STORY=============
TWRP can't recognize my backup folder name which I am trying to restore
=====================================
=============LONG STORY=============
I had a nandroid backup before, then I copied the backup to PC, still have it. Then I flashed lineage 13. I deleted the nandroid backup on the phone storage. Now I want to restore the backup so I copied the backup files from the PC.
Now when I go to TWRP Restore mode, no backups are found.
I already searched through the internet and found the renaming method but there's a problem:
this is my original backup:
TWRP/backups/42f7491d7b409fc7/2017-03-01--05-28-34_JZO54K.N7105XXDMB
I tried to make a new backup of my current lineage (just to see if the folder name changed based on the new folder the backup process will create), here is what the resulting folder was:
TWRP/backups/42f7491d7b409fc7/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
As you can see, only the innermost folder name changed. So from what I found through searching, it said to rename the old backup folder to the new backup folder's name, meaning :
I changed
2017-03-01--05-28-34_JZO54K.N7105XXDMB
to
2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
TWRP still can't see the original backup.
So what should I rename the original backup folder for TWRP to recognize it and make it appear?
EDIT:
I already updated my TWRP but problem still exists.

Create a new backup with your current rom, then remove it and add the old one instead.

futchy4u said:
Create a new backup with your current rom, then remove it and add the old one instead.
Click to expand...
Click to collapse
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.

It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
/TWRP/BACKUPS/4d00475b004150de/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
Click to expand...
Click to collapse
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
sgn15 said:
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.
Click to expand...
Click to collapse

futchy4u said:
It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
Click to expand...
Click to collapse
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.

sgn15 said:
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.
Click to expand...
Click to collapse
You're welcome. I think it's ok to be left here so that it could help others.