Why convert BACKUP1 to TAR?
A .tar is a portable, browsable archive, whereas the backup is a raw block image. People repackage to .tar to move just the files off the device image without keeping a multi-gigabyte raw dump.
How to convert BACKUP1 to TAR
cat + mount + GNU tar FREE
Rebuild the image with cat *.backup* > userdata.img, mount it (sudo mount -o loop,ro userdata.img /mnt), then archive the contents: tar -cf userdata.tar -C /mnt .
gunzip (gzip) OPEN-SOURCE
If a rejoined part turns out to be gzip-compressed, decompress it first with gunzip userdata.img.gz before mounting and running tar.
About these formats
A .backup1 file is the second part of a split backup created by an Android phone or tablet in System Recovery Mode. When the userdata backup is larger than about 2GB, the recovery splits it…
Open .BACKUP1 details →A TAR file (also called a tarball) bundles files and folders into one archive but does not compress them. That is why you almost always see it as .tar.gz or .tgz, with gzip added on top. On…
Open .TAR details →Quality & what to watch
- This is a two-stage process; the parts are a raw image, so you must rebuild and mount it before any archive can be made.
- Mounting ext4 read-write from another OS risks corruption - always mount read-only when just extracting files.
- File ownership, permissions and symlinks are only preserved if you run
tarwith root privileges on the mounted image.
Frequently asked questions
Can I turn `.backup1` straight into a `.tar`?
.img, mount it, then create the .tar from the files inside.Which OS makes this easiest?
Will the `.tar` be smaller than the image?
.tar holds only actual files. Add -z for a gzip-compressed .tar.gz.