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.
Related
Is it possible to move one Program from a ROM to another ROM? I've tried TB but it only see's that it's a backed up file but won't restore. Is this possible and if so, what is the process?
you can unzip both ROMS and drag the app from the Sys/app folder on one to the same folder on the other, rezip it and flash it and it will install with the flash
Titanium Backup is really the only way. What exactly happens when you try to restore? Does it give you an error.
HipKat...thanks! As soon as I posted this I found that I can get into the zipped APK folder, move it to my SD Card, and then use my file manager to install it. Worked great! This is the fix!
dfr867 said:
HipKat...thanks! As soon as I posted this I found that I can get into the zipped APK folder, move it to my SD Card, and then use my file manager to install it. Worked great! This is the fix!
Click to expand...
Click to collapse
Cool. I forgot about getting into the zipped folder with a file manager
On my old Magic, I was running CM6 and I thought CWM - but I don't remember now, I'm thinking possibly it was another recovery, because I had the ability then to name my backup files before starting the backup, so I could give them more meaningful names than just the date.
Can I rename my backup files on my SD card? Just use Astro for this, or what?
Or will this cause CWM to no longer see the files as valid backup files?
Additionally, I had been rooted prior on GB - now that I'm on ICS, I'm not sure I want those on my SD card in the (hopefully) unlikely event that I accidentally pick one of those nandroids to restore when I meant to restore back to a prior ICS version. Seems like there could be risk of bricking my phone, so can I copy and delete these off my phone?
Is it as simple as knowing where to look on the SD card and using Astro to rename them, or Kies (or Windows) to move them/delete them?
I dont think you can do that because then it will give you an MD5 mismatch. I think in the new version of TWRP recovery coming out, you can name and rename backups though.
slick_rick said:
I dont think you can do that because then it will give you an MD5 mismatch. I think in the new version of TWRP recovery coming out, you can name and rename backups though.
Click to expand...
Click to collapse
You can rename them as long as you don't put any spaces when you rename it. For example - blazer 4.1 gb- would not work you would have to us blazer.4.1.gb and it would work fine.
albertouresti said:
You can rename them as long as you don't put any spaces when you rename it. For example - blazer 4.1 gb- would not work you would have to us blazer.4.1.gb and it would work fine.
Click to expand...
Click to collapse
There's your answer then.
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.
I was doing some changes to my phone so i did a backup and then copied the backup directory from the phone to my PC to save it. The backup was under /clockworkmod/backup/Jan312013.
I copied that directory (Jan312013) to my PC not even realizing when it copied it, for some reason it changed it to a zip file??? Now i have Jan312013.zip and have no idea how to copy that back to phone to restore?? If i open the zip it has all the files that would normally be in the backup directory but of course recovery does not recognize a zip file for backup.
Thoughts? Help? Thanks.
What version of CWM, if that's what youre using? I just used 6.0.2.3, and i believe there's an option to backup as .zip. Maybe you accidentallychose that method?
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.