Repository navigation
RECOVERY
VD $ VD171 @ Priv8 edited this page Nov 4, 2026
·
1 revision
Languages: English | العربية | Čeština | Deutsch | Español | فارسی | Français | हिन्दी | Bahasa Indonesia | Italiano | 日本語 | 한국어 | Nederlands | Polski | Português | Русский | Svenska | ไทย | Türkçe | Tiếng Việt | 中文
Your VDBackup backups use standard formats, so you can open them anywhere,
without this module. A backup folder contains a manifest.json, the APKs
(*.apk.zst) and the data archives (<item>.tar.zst, .tar.gz or .tar.lz4),
optionally encrypted with a trailing .age.
-
zstd: https://github.com/facebook/zstd/releases (macOS:
brew install zstd; Linux:apt install zstd) -
age (only for
.agefiles): https://github.com/FiloSottile/age/releases -
taris built into macOS, Linux and modern Windows 10/11. -
gzipis built in everywhere; for.tar.gzyou need nothing extra.
Keyfile (recommended):
age -d -i age.key -o data.tar.zst data.tar.zst.age
Passphrase:
age -d -o data.tar.zst data.tar.zst.age # age will prompt for the passphrase
Do the same for each *.age file (APKs and data archives).
.tar.zst:
zstd -d data.tar.zst # -> data.tar
tar -xf data.tar # extracts the files
.tar.gz:
tar -xzf data.tar.gz
.tar.lz4 (zstd reads lz4):
zstd -d --format=lz4 data.tar.lz4 -o data.tar
tar -xf data.tar
APKs are just zstd-compressed APK (ZIP) files:
zstd -d base.apk.zst # -> base.apk (a normal installable APK)
- Extracted files keep their relative paths; the SELinux context, uid/gid and modes are inside the tar (and are reapplied properly only when you restore on Android).
-
manifest.jsondescribes exactly what each file is, the app version and the original owner/context. It is the source of truth. - Nothing here is tied to a specific device: the same passphrase/keyfile works on any machine.