Related
Yes i know the fastboot trick, but can anyone guide me towards making the nandroid backup files into a update.zip that would work?
I'd like to know too ^^.
Me too.
I've successfully scripted the automated creation of a file structure into which the contents of BOOT.IMG, SYSTEM.IMG, DATA.IMG, CACHE.IMG and SD-EXT.IMG are extracted. The script also creates a valid update-script file under ./META-DATA/....
The only issue I have is that I'm using windows so the .IMG files extracted as a yaffs file system, looses the original file permissions. I need someway to recreate the permissions in the update.zip.
Thats all.
Having a way of converting a nandroid backup to an update.zip means you can very easily cook custom roms from a nandroid backup, and port ROMs across phones using a portable .ZIP format.
Maybe dsixda can help
http://forum.xda-developers.com/showthread.php?t=633246
"OR [cook a rom] from a Nandroid backup (under /sdcard/nandroid) [NOT RECOMMENDED]:
Copy the system.img and boot.img files from the backup folder to your kitchen's original_update folder
NOTE: The Nandroid-backup method of cooking is not the best way to cook, because the kitchen may not account for various advanced options that were cooked outside of this kitchen (these options are in the update-script file which was in the original ROM but is not in the backup. The kitchen needs to re-create this file and 'guess' those options). However, it will support Nandroid backups that already have basic features like root, busybox and /data/app functionality. "
You get nandroid backup images by backing up a ROM which was flashed from an update.zip package. What is then the point of recreating that update.zip package?
giant is right with the klitchen by dsixda you can make an update.zip form nandroid very easy
Guys, we're missing the point.
To clarify:
The "point of recreating the ZIP ROM file" are numerous. For example, to create a ROM where the original ROM isnt available, i.e. to create a portable ROM based on an existing set of images in a phone where the phone and/or its sdcard cannot be removed or where we do not wish to remove the card. Simple. But more importantly, the process is a learning and development activity that I want to undertake, its a personal decision, for which support would be welcome.
Secondly, dsixda issues many caveats around cooking ROMs from nadroid backups. It simply doesnt work - I've tried it - thus his caveat is correct and should be observed. Furthermore, his kitchen creates windows based ZIP files. The process is inherently flawed for creating ROMs for linux because the ZIP files contain a windows file structure which does not contain the appropriate linux based file permissions (linux being the O/S base system on android. The restore operation does not work - in stock form - because one looses the critical file permissions, UID and GID that are required in order for the ROM to function correctly, and in some instances from my experience, to even boot up! His update-script attempts to reinstate the appropriate permissions, UID and GIDs, however, and as dsixda admits, the process is not foolproof and does not cover all eventualities, combinations and scenarios. Thus, the issue of permissions, GID and UID remains outstanding.
For these reasons, in my humble view, the issue of permissions is critical in ensuring a successful ROM flash from [linux based] .IMG files. Once this is resolved, the rest of the process is trivial. Indeed, if this one issue could be resolved, then dsixda's kitchen would mature from a useful toolset, to a truly wonderous one-stop solution.
well i don't know what people have tried and got to work or not, but it can eb done and have been done before, one of my sliderom build was done froma nandroid
soo i guess it's up to how much effort you put into it and use the kitchen as a tool, but not only use it, cause then you fail, if you don't do some manual work, nothing 100% automated will ever be a big succes
I have a solution.
I am coding this up as we speak.
My solution will extract the file permission, UID and GID from the .IMG , for each contained file. My script then runs as part of the update-script (i.e. RUN_PROGRAM restore-protection) subsequent to a ROM flash. Thus, the resultant file structure after a ROM update is exactly the same as that contained within the .IMG files.
EDIT:
coding complete.
will test tomorrow on existing phone + sdcard.
The purpose of this exercise is to 'clone' an existing phone software load, as ROM file, that can then be flashed. My script takes all partition images (system, data, cache, sd-ext and so on), creates a ROM that includes functionality that will - when flashing - restore the exact permissions, GID and UID as written in the backup files (.IMG), thus cloning the phone.
I plan to update the script in future so that APK files can be added or removed, and additional low level features such as kernel pre-empting, scheduling and other features can be added --- I think they call this "a kitchen" in Android speak.??
From your description of what you're doing it sounds like you could end up with the simplest and closest to a one click kitchen that allows users with less knowledge to fully backup / restore / clone their phone (rom, personal settings, data and all). A lot of noobs might like this tool big time
Any progess made on this? I have been trying to create a rom for a nandroid backup. When I go to flash it, I get symlink errors and the flash fails.
dazxda said:
I have a solution.
I am coding this up as we speak.
My solution will extract the file permission, UID and GID from the .IMG , for each contained file. My script then runs as part of the update-script (i.e. RUN_PROGRAM restore-protection) subsequent to a ROM flash. Thus, the resultant file structure after a ROM update is exactly the same as that contained within the .IMG files.
EDIT:
coding complete.
will test tomorrow on existing phone + sdcard.
The purpose of this exercise is to 'clone' an existing phone software load, as ROM file, that can then be flashed. My script takes all partition images (system, data, cache, sd-ext and so on), creates a ROM that includes functionality that will - when flashing - restore the exact permissions, GID and UID as written in the backup files (.IMG), thus cloning the phone.
I plan to update the script in future so that APK files can be added or removed, and additional low level features such as kernel pre-empting, scheduling and other features can be added --- I think they call this "a kitchen" in Android speak.??
Click to expand...
Click to collapse
Do you have a link?
dazxda said:
I have a solution.
I am coding this up as we speak.
My solution will extract the file permission, UID and GID from the .IMG , for each contained file. My script then runs as part of the update-script (i.e. RUN_PROGRAM restore-protection) subsequent to a ROM flash. Thus, the resultant file structure after a ROM update is exactly the same as that contained within the .IMG files.
EDIT:
coding complete.
will test tomorrow on existing phone + sdcard.
The purpose of this exercise is to 'clone' an existing phone software load, as ROM file, that can then be flashed. My script takes all partition images (system, data, cache, sd-ext and so on), creates a ROM that includes functionality that will - when flashing - restore the exact permissions, GID and UID as written in the backup files (.IMG), thus cloning the phone.
I plan to update the script in future so that APK files can be added or removed, and additional low level features such as kernel pre-empting, scheduling and other features can be added --- I think they call this "a kitchen" in Android speak.??
Click to expand...
Click to collapse
Hi, could yo share your script? I'm also working on something similar, and could use a bit of help
OMG this is exactly what I need.. I read all the way to the end and then ARRGGGGGG.. no more responses in months. Have you made this script yet? If no .. does anyone else have instructions on taking a nandroid backup and creating an IMG or ?
My personal reasons.. I have a Craig CMP741E tablet that is stuck in the android logo screen after attempting the factory update.. the one that crashes EVERY1's tablet. And there is no working way that I have found to fix it. No custom roms or factory roms that can be flashed without FIRST having the tablet ON and turn on USB Debugging or already have CWM installed. So I cannot use ADB or any other method I can find to do this.
I have a buddy with the same tablet that is rooted and has GAPPS and everything on it. He gave me a copy of his nandroid backup but now I cannot find anything I can actually do with it. If I can turn it into an Update.zip or IMG I can simply put on SD Card.. restart and cross my fingers.
lilc420 said:
OMG this is exactly what I need.. I read all the way to the end and then ARRGGGGGG.. no more responses in months. Have you made this script yet? If no .. does anyone else have instructions on taking a nandroid backup and creating an IMG or ?
My personal reasons.. I have a Craig CMP741E tablet that is stuck in the android logo screen after attempting the factory update.. the one that crashes EVERY1's tablet. And there is no working way that I have found to fix it. No custom roms or factory roms that can be flashed without FIRST having the tablet ON and turn on USB Debugging or already have CWM installed. So I cannot use ADB or any other method I can find to do this.
I have a buddy with the same tablet that is rooted and has GAPPS and everything on it. He gave me a copy of his nandroid backup but now I cannot find anything I can actually do with it. If I can turn it into an Update.zip or IMG I can simply put on SD Card.. restart and cross my fingers.
Click to expand...
Click to collapse
Can you access the tablet's fastboot mode? Turn the tablet fully off, then hold the Menu button and the Power button. I don't have your tablet, but it's a standard boot mode.
Make sure you have the tablet connected to the PC. You should see it pop up in the Device Manager, or by doing "fastboot devices" from a command prompt.
If you can get there, you may be able to flash a recovery image.
Hi, does anybody knows if there is a response for this post??, i am looking for a method to convert the images files that are included in a rom stock (for using with sp flash tool) to an update.zip file. I have no way to use sp flash tool because my tablet has a hardware problem with microusb port and the only way is flashing a new rom via microSD card with an update.zip..
Maybe the solution is in another thread, please be kind and give me a link or at least give me some suggestions where to look for.
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
This question is not specific to the G2 however since it's the device I currently own I figured I might as well ask it here since it seems as good as place as any to ask. That being said I would like to know how I can explore the contents of a TWRP created nandroid backup from my PC running Windows 7 professional. I have already transferred the files to my computer without issue, but when I try to extract the "data.ext4.win000" or "data.ext4.win001" files using 7Zip it just says the files are not supported so I am not sure what piece of software I need to get to open these files and explore their contents from within Windows and any help would be greatly appreciated.
TIA,
MTCellph
You need a specific program to view the files inside, as soon as I check the one I use on my laptop I'll let you know
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
---------- Post added at 11:34 AM ---------- Previous post was at 10:49 AM ----------
Ok so here's what you want to do rename the file to data.est4.tar.gz and you will be able to explore the archive using 7zip
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
I did that and there was a Tar file inside of the tar.gz file which I tried extracted to my desktop and tried to open in 7zip, but it would not open so I am at the same spot I was in to begin with
mtcellph said:
I did that and there was a Tar file inside of the tar.gz file which I tried extracted to my desktop and tried to open in 7zip, but it would not open so I am at the same spot I was in to begin with
Click to expand...
Click to collapse
for some reason that keeps happening with the data folder but you can easily view the system
XxZombiePikachu said:
for some reason that keeps happening with the data folder but you can easily view the system
Click to expand...
Click to collapse
Thanks again for the reply. I was trying to view the DATA folder as you may have guessed which as you found out does not work (or atleast I could not get it to work for me) on Windows so I had to boot up into my Ubuntu partition on my machine and concatenate the 2 .WIN files into one file using the following command from the Ubuntu terminal.
cat data.ext4.win000 data.ext4.win001 > data.tar (or tar.gz if compression was enabled when you created the backups in TWRP)
I then used the built in archive manager in Ubuntu and was able to browse the DATA partition and extract the information that I needed. This should not be necessary, but as we both discovered, windows (for whatever reason) does not seem to be able to handle the DATA partition while Ubuntu can so if anyone stumbles upon this post wanting to know the same information then you should try downloading a live cd / live usb version of Ubuntu (if you don't already have it installed on your machine that is) and running it and follow the steps above to access the files in your DATA partition.
Note: In the above example I had to combine the 2 data.ext4.win* files into one file before I could access the archive. If you do not have multiple data.ext4.win* files then you can skip that step and go straight to the next step which is opening the data partition in the built in archive manager that comes with Ubuntu.
HTH,
MTCellph
mtcellph said:
Thanks again for the reply. I was trying to view the DATA folder as you may have guessed which as you found out does not work (or atleast I could not get it to work for me) on Windows so I had to boot up into my Ubuntu partition on my machine and concatenate the 2 .WIN files into one file using the following command from the Ubuntu terminal.
cat data.ext4.win000 data.ext4.win001 > data.tar (or tar.gz if compression was enabled when you created the backups in TWRP)
I then used the built in archive manager in Ubuntu and was able to browse the DATA partition and extract the information that I needed. This should not be necessary, but as we both discovered, windows (for whatever reason) does not seem to be able to handle the DATA partition while Ubuntu can so if anyone stumbles upon this post wanting to know the same information then you should try downloading a live cd / live usb version of Ubuntu (if you don't already have it installed on your machine that is) and running it and follow the steps above to access the files in your DATA partition.
HTH,
MTCellph
Click to expand...
Click to collapse
great I already run Ubuntu on a virtual machine so this is very useful information
explore/extract system.ext4 with IZArc
Sorry - please ignore this post - I don't know what I'm talking about sometimes...
I know the thread is over 6mon old, sorry...
I have a recent backup from TWRP 2.7.x and really need to figure out how to get into /data/media or whatever the equivalent is in the archive. I did a 'cat' of my 4 data.ext4.win00* files and opened that in Ubuntu. All it contained was a big stack of APKs and a subfolder with a bunch of 0 byte objects. What bugs me the most is that the file browser reports the data.ext4.tar.gz I created at 3.3GB, but the ubuntu handler only reports the /data folder inside at 1.6GB.
I lost a buttload of data and files to an Odin restore necessitated to wipe 2 stubborn cache files. Nothing I tried could change their properties (thanks G00gle). Anyway, I ended up doing a full wipe of the phone thinking I had a good TWeRP backup on the extSDcard. Wrong.
I just checked system.etx4.win* and found the same/similar files under it's /app folder.
Have I lost all those files or is there something else I can try? TIA.
Talos4 said:
explore/extract system.ext4 with IZArc
Click to expand...
Click to collapse
Thanks a lot for this hint! I hadn't heard about IZArc before. It's really great and saved my day. :highfive:
Windows users
For windows (if you have multiple files) :
Code:
copy /B data.ext4.win001 + data.ext4.win001 + data.ext4.win001 + data.ext4.win001 output.tar
Mehdiway said:
For windows (if you have multiple files) :
Code:
copy /B data.ext4.win001 + data.ext4.win001 + data.ext4.win001 + data.ext4.win001 output.tar
Click to expand...
Click to collapse
Thanks to this, I was having a bad time viewing each of the data.ext4.win000 etc. etc. can't handle by windows I think. Looking for solution from google and I end up here. Thank you my friend. :good:
zidane02 said:
Thanks to this, I was having a bad time viewing each of the data.ext4.win000 etc. etc. can't handle by windows I think. Looking for solution from google and I end up here. Thank you my friend. :good:
Click to expand...
Click to collapse
if you want to explore twrp backup files on windows:
- rename i.e. data.ext4.win000 to data.ext4.tar and open that .tar file with winzip or winrar (whichever reads .tar compressed files) - same goes for .win001 etc...
btw just a sidenote - twrp doesn't backup your personal media files (photos, videos, etc)
I know I'm bumping a super old thread in a sorta old forum area, but Google brought me here. I am trying to browse a TWRP backup but I have a feeling I need to do a bit more fussing around. The backup is split into data.ext4.win000 through data.ext4.win007 and each of the parts has an accompanying .md5 with the same naming structure (ie. data.ext4.win000 and data.ext4.win000.md5.) There's also a data.info file as well.
The system backup is the exact same as described above for the data, except it's only 2 parts (system.ext4.win000 and system.ext4.win001, with the accompanying md5 files and the info file.)
Can someone provide a bit of guidance? I'm using a Windows 7 Home Premium machine.
I'm in the same situation cognitivedissonance is. Any help to put us on the right direction?
The answer for one question would be beneficial and highly appreciated: in which format the data.ext4.win00x files are ?
cognitivedissonance said:
I know I'm bumping a super old thread in a sorta old forum area, but Google brought me here. I am trying to browse a TWRP backup but I have a feeling I need to do a bit more fussing around. The backup is split into data.ext4.win000 through data.ext4.win007 and each of the parts has an accompanying .md5 with the same naming structure (ie. data.ext4.win000 and data.ext4.win000.md5.) There's also a data.info file as well.
The system backup is the exact same as described above for the data, except it's only 2 parts (system.ext4.win000 and system.ext4.win001, with the accompanying md5 files and the info file.)
Can someone provide a bit of guidance? I'm using a Windows 7 Home Premium machine.
Click to expand...
Click to collapse
To browse the "system.ext4.winxxx" files, simply add at the end of the file ".tar" and decompress them in the same folder created by the first file.
The MD5 is a type of Checksum file wich is created just to check the integrity of the backup file is linked to.
the gladiator said:
I'm in the same situation cognitivedissonance is. Any help to put us on the right direction?
The answer for one question would be beneficial and highly appreciated: in which format the data.ext4.win00x files are ?
Click to expand...
Click to collapse
They are compressed in TAR format.
Mehdiway said:
For windows (if you have multiple files) :
Code:
copy /B data.ext4.win001 + data.ext4.win001 + data.ext4.win001 + data.ext4.win001 output.tar
Click to expand...
Click to collapse
Actually the file numbers should increment, using the above example:
Code:
copy /B data.ext4.win001 + data.ext4.win002 + data.ext4.win003 + data.ext4.win004 output.tar
In the example you're appending a file to itself over and over.
forkup said:
Actually the file numbers should increment, using the above example:
Code:
copy /B data.ext4.win001 + data.ext4.win002 + data.ext4.win003 + data.ext4.win004 output.tar
Click to expand...
Click to collapse
In most cases that should be;
Code:
copy /B data.ext4.win000 + data.ext4.win001 + data.ext4.win002 + data.ext4.win003 + data.ext4.win004 output.tar
And the other (uncompressed) .win image-files (like system_image.emmc.win) can be read with a tool like Ext2Read.
Mehdiway said:
For windows (if you have multiple files) :
Code:
copy /B data.ext4.win000 + data.ext4.win001 + data.ext4.win002 + data.ext4.win003 output.tar
Click to expand...
Click to collapse
Unfortunately, thats wrong. It might work with tar --ignore-zeros (-i) option but only for uncompressed archives.
Do not combine the data.ext4.win* files into one file before accessing. These are single standalone tarball archives (gzip compressed sometimes) you should rename and unpack for each own
I am also seeking a correct and up-to-date answer for this. I have TWRP 2.8.7.0 and multiple .win files, .md5 files and data.ext4 files in my SD Card. Is renaming archives enough to browse in 7zip? Is there any special tool for this, or do we also combine/merge multiple files into one?
Thanks a lot!
Can anyone here shed any light on my TWRP backup browsing issue described here? Thanks
I've been scouring the interweb looking for a way to take a stock tar file and convert it to a zip file that will flash with twrp. I know it can be done, but thus far I'm not happy with the processes I've found... how do you guys do it?
The stock TAR files contain partitions in IMG format - an all in one file system, and in this case using EXT4 formatting.
In order to create a ZIP, you need to access the files on the partition, which means finding a way to mount those IMG partitions to copy their contents, or find a piece of software to extract from them w/o mounting. Since they are EXT4, you can probably assume a Windows solution isn't available (EXT4 is Linux). Some utilities may exist to handle EXT4 on Windows, but finding one that knows EXT4 and can extract/mount an IMG file is pretty specific.
EDIT : found a utility for you - http://forum.xda-developers.com/showthread.php?t=2285831
If you can somehow get the files out of the archive, you'll need to find a tutorial on the structure of a flashable ZIP. Generally, its just folders and files but there is also a META-INF folder, scripts to install and set permissions, etc. There are likely threads here on XDA that can detail these steps.
Spitzaf, thanks so much! I was hoping for just such a tool