# Cant Backup a new OnlyKey duo **URL:** \ **Category:** Backup and Restore\ **Created:** [November 4, 2023, 3:38pm UTC](https://onlykey.discourse.group/t/cant-backup-a-new-onlykey-duo/1176 "2023-11-04T15:38:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Amon](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Amon](https://onlykey.discourse.group/u/Amon)\ **Post date:** [November 4, 2023, 3:38pm UTC](https://onlykey.discourse.group/t/cant-backup-a-new-onlykey-duo/1176/1 "2023-11-04T15:38:44Z")
Hey, I just brought a OnlyKey duo and it came with the 3.0.4-prodn Firmware. I tried to follow the instructions and do a backup, holding the button 1 for 5+ seconds, and it began to write in the backup section. ![image](https://global.discourse-cdn.com/free1/uploads/onlykey/original/1X/319f6760f91fecbffb8018924cba65d82af1fb72.png) After trying to verify the bakcup It always will show “ERROR this backup file is corrupt”, however I tried to save it. When I select to restore to onlykey it says: "Could not parse backup file. InvalidCharacterError: Failed to execute ‘atob’ on ‘Window’: The string to be decoded is not correctly encoded." I’m using App v5.3.6 on Windows, also I tried with Arch Linux but got the same error. I had tried to downgrade it, however I’m getting this message: ![image](https://global.discourse-cdn.com/free1/uploads/onlykey/original/1X/57a54bd38a5f6ba6276c33b434a7f53caa8e5729.png) So I restored to v3.0.4-prodn ---
**Author:** ![SecureUser](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@SecureUser](https://onlykey.discourse.group/u/SecureUser)\ **Post date:** [November 4, 2023, 9:42pm UTC](https://onlykey.discourse.group/t/cant-backup-a-new-onlykey-duo/1176/2 "2023-11-04T21:42:00Z")
Hi, I am currently using v3.0.4-prodp and backup is also not working for me. But when I do it, I don’t get any error, but the restore is way too fast with the wrong animation, so it does not restore anything. I am not sure, but about 2 versions back ([Release OnlyKey 3.0.2 Firmware · trustcrypto/OnlyKey-Firmware · GitHub](https://github.com/trustcrypto/OnlyKey-Firmware/releases/tag/v3.0.2-prod)), this thing (backup/restore) worked. I think the changes in recent releases broke this functionality. Also, the size of my working backup is not the same as the new one. ---
**Author:** ![Amon](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Amon](https://onlykey.discourse.group/u/Amon)\ **Post date:** [November 5, 2023, 1:31am UTC](https://onlykey.discourse.group/t/cant-backup-a-new-onlykey-duo/1176/3 "2023-11-05T01:31:03Z")
Hey! I got a second question/error report. I have a normal onlykey, and I tried to do a backup on it and it worked the backup verification was fine not corrupted. I tried to wipe the Onlykey Duo and restore to the Onlykey backup file, using the same backup phrase. They both have the same number and version in the Keepass, however Google and Keepass refuses to open with the Onlykey Duo. Is this a error in this firmware version or I can not use a Onlykey Duo as a replace for the Onlykey? ---
**Author:** ![SecureUser](https://avatars.discourse-cdn.com/v4/letter/s/858c86/32.png) [@SecureUser](https://onlykey.discourse.group/u/SecureUser)\ **Post date:** [November 5, 2023, 9:08am UTC](https://onlykey.discourse.group/t/cant-backup-a-new-onlykey-duo/1176/4 "2023-11-05T09:08:32Z")
Backup says that it is not corrupted on mine (OnlyKey Duo) too (v3.0.4). That (proper backup of the resident key) was fixed in 3.0.2 version (read notes in releases) and I can confirm that when I backup/restored using that version it did indeed properly restored on my second OnlyKey Duo (with resident key and all the rest). I have unfortunately not bothered to try to downgrade from the current 3.0.4 version.