Unexpected Files in root of Google Drive

Help Android App
6

Sorry for the late response!

I would recommend to restore the vault in format 7 that you’ve all your files back, also the pictures that were taken after the migration. So assuming you’re in format 7.
Then follow this steps:

  1. Create a copy of the masterkey.cryptomator file of the vault
  2. Open the masterkey.cryptomator file in a text editor and change the following
    1. "version": 7 to "version": 6
    2. Change the value of "versionMac" to the "versionMac" of this vault in version 6. Use it from your backup or look through the masterkey.cryptomator.XYZ.bkup files to find the value.
    3. save and close the file
  3. Use the Sanitizer in decryptFile mode. Provide the vault path and passphrase and press enter
  4. Provide the full path to the file to decrypt in your root of the cloud, enter
  5. Provide a full path to a file where you want to have the decrypted file, enter
❯ java -jar sanitizer-0.16.jar decryptFile -vault /home/julian/test --passphrase t
# Cryptomator vault sanitizer v0.16 #

Enter absolute path of an encrypted file: /home/julian/WXG0Nok5uMpOsAqNAiSuwMUBkFolajw=.c9r
Enter absolute path of decrypted output: /home/julian/foo.txt
File successfully decrypted.

Using this script you can restore the missing file extension. The name of the file is unfortunately not recoverable.

Last but not least change back the "version" and "versionMac" values in the masterkey.cryptomator. Now all files should be back and you can continue use this vault.

Side node: We released Android version 1.5.8-beta1 a week ago which fixes the problem that you figured out. Soon the version will also be available in the release channel.

2 Likes