-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot restore seedvault during initial set up - An error occured while loading the backups - OPENSSL_internal:BAD_DECRYPT #808
Comments
Do you have a screenshot of the restore page? I'd be curious to see how this error is reported to the user. Have you ever used more than one recovery code? Sounds a bit like the story in #804 where the reporter had another recovery code without remembering it.
This sounds like it was using a recovery code you had already set up. Could it be that you have forgotten it? Can you use the verify code feature to make sure you have the right code for the source device? |
Hi @grote, What I have tried in the meantime was to copy the backup from old device and to new device using adb on a fresh backup & avoid mixing personal and work profile backups. I am able to correctly validate the recovery code on the target device but it fails after. Looks like the same error to me: Here is how the error is reported: Will try now again from scratch by clearing all data on source & devices. Thanks for any pointers. |
Ok this means it can't decrypt the backups.
What do you mean that it fails after? Can you please try also validating the same code on the source device, so we can be sure both devices (and profiles!) are working on the same recovery code? |
I am getting this same issue, trying to restore a backup from DivestOS 20 (Android 13) to CalyxOS 6.2.1 (Android 15) on a Google Pixel 7 (panther). ADB output
Since this is the same device, it is very difficult for me to go back and check on the "source" device. I did verify the codes manually after I wrote them down, and after the backup was fully completed, and they are the same 12 words. |
I've also heard of another report on the Calyx main channel where the user had two phones: https://matrix.to/#/!UlsAcjNSfQqWJPccIO:matrix.org/$A3qMJCBzZkZktTkLTKmy3RYSDI4AflPc01i-oR4taCU?via=tchncs.de&via=matrix.org&via=calyx.dev |
Attempting to restore in DivestOS 20 (A13) on the same device gives a "No suitable backups found at given location". I'm afraid my backup may have gotten corrupted somehow. |
Have you ever had only one code? In #804 someone also thought they had the right code and eventually remembered a second code which turned out to be the real one. |
Hi,
Reported this to grapheeos and it was closed as upstream bug with recommendation to copy to device first: GrapheneOS/os-issue-tracker#4466
I am trying to move from GrapheneOS on a Pixel 6a to a Pixel 9 Pro.
I have a work account setup and so I have backed up both personal and work accounts.
During backup of the personal account I was getting backup errors so I deleted all seedvault data & cache and restarted from scratch, it successfully finished the backup. I did store both backups to the same USB as I read that it should be supported. It didn't get to the point to ask about passcode.
The error occurs during the initial setup while trying to restore, here is the info displayed:
And the corresponding section from the logs
Greatful for any pointers or suggestions.
The text was updated successfully, but these errors were encountered: