Hello everyone, I wanted to open a new thread, maybe others like me found themselves in the same siditura, that is, to be able to extract a saved file, backed up with TWRP the file in question, was initially saved in.snb format, file an app. pre-installed on the S3Neo, and it's called SMemo, the file contains sensitive data and password, you will say but because it does not restore the backup, if you want, but the saved one there are data that are not in another file, I made two backups , with the data inside, are in various formats, some I add immediately after, now what I ask, you can find that file and extract it using a PC with windows7 system, thank you in advance.
- recovery.emmc.win.md5
-system.ext4.win000.md5
-recovery.log
-data.ext4.win001
-data.ext4.win000
-boot.emmc.win
-recovery.img
and others similar with different formats. :fingers-crossed:
Related
I have been running roto backups for a while now, but have never had the need to restore from one. While looking through the different files that were backed up after I ran the command code, I noticed a file called data.tar.gz. Where is the correct place for selecting this file in Heimdall when doing a restore? For example, do I put it in the recovery slot under other, or does it not matter where I put this file performing a restore?
Also, I found a file called efs.rfs that was backed up and I have the same question for that file.
Thanks in advance for any advice,
caveman999
caveman999 said:
I have been running roto backups for a while now, but have never had the need to restore from one. While looking through the different files that were backed up after I ran the command code, I noticed a file called data.tar.gz. Where is the correct place for selecting this file in Heimdall when doing a restore? For example, do I put it in the recovery slot under other, or does it not matter where I put this file performing a restore?
Also, I found a file called efs.rfs that was backed up and I have the same question for that file.
Thanks in advance for any advice,
caveman999
Click to expand...
Click to collapse
By just taking a look at how data.tar.gz is created it looks as though you could just copy it to your phones sd card and extract it to /data.
Heimdall does support efs.rfs, however it's intentionally not included in the user interface. The efs partition includes a lot of phone specific data, which depending on where you live it might be illegal to tamper with. As a general rule you shouldn't need to flash this file as the phone should retain this information. However, if in the event your efs does become corrupt you can flash the efs partition via the Heimdall command line tool.
Benjamin Dobell said:
By just taking a look at how data.tar.gz is created it looks as though you could just copy it to your phones sd card and extract it to /data.
Heimdall does support efs.rfs, however it's intentionally not included in the user interface. The efs partition includes a lot of phone specific data, which depending on where you live it might be illegal to tamper with. As a general rule you shouldn't need to flash this file as the phone should retain this information. However, if in the event your efs does become corrupt you can flash the efs partition via the Heimdall command line tool.
Click to expand...
Click to collapse
Thanks for the detailed response.
What program would you recommend to extract the data file? Would root explorer be suitable?
Thanks
Sent from my AT&T Galaxy Tab using XDA App
Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse
Dear geeks and peeps of the xda- dev forums, I'd like to introduce myself, I am Janesalami. I am new to my LG Optimus L5 E610, and I'd like to know how to really make my phone ultrahaxorzpwn. I rooted it and now I don't know what to do.
How To Extract Zip File From Corrupt Zip Archive Folder?
Hi Friends,
I am James Simon and visit on this forum first time for asking query as regarding of zip corruption issues. I have lost my all data in Zipped archive folder because my zip archive folder has been damaged due to virus attack. I have tried a lot of time to extract zip file from zip archive folder but i can't get success to restore once again it. Please if anyone has sufficient solution to defeat such complication so share with me.
Thanks
How To Extract Zip File From Corrupt Zip Archive Folder?
Hi,
Also I have suffered from such Zip corruption error issues but I used a SysTools Zip repair tool which repairs all formatted zip data instantly without harming any file content value. I got it this software from search Engine Google and I recovered my entire corrupt Zip file instantly.
Thanks
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Icculus760 said:
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Click to expand...
Click to collapse
Follow these instructions. Enjoy.
Misterxtc said:
Follow these instructions. Enjoy.
Click to expand...
Click to collapse
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Icculus760 said:
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Click to expand...
Click to collapse
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Misterxtc said:
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Click to expand...
Click to collapse
What the heck, man. Stop helping me so quickly! :laugh:
Thanks again!!
Hey all, like the title said, I need to recover some files from a TWRP backup. But I do not want to flash the backup. I changed the extension to .tar and was able to browse just fine, but am unable to find the home folder which is where the files I need were stored. Specifically Storage\Emulated\0\ProgramData but of course this path doesn't exist since it's essentially little more than a link to the real path, so where would I find the correct path in a twrp backup? Thank you for any advice or help!