I upgraded to KeyOS 1.4.0 and created a local Settings & Data backup (settings-2026-08-16_17-50-03.tar). I then wiped the device specifically to test the recovery process, but I was unable to reconnect Prime to Envoy.
This is exactly why I remain uncomfortable with Prime’s dependence on Envoy. A local backup is only meaningful if I can independently restore it on the device without relying on a companion phone app.
I understand that Prime has a much broader vision than Core, but Prime has also become a significantly larger and more complex platform. With Core no longer being the focus, I think reliable, independent backup and recovery should be one of the highest priorities.
Envoy should be an optional convenience layer, not a requirement for basic recovery.
For a device built around self-custody and sovereignty, **Prime should be able to back itself up, wipe itself, and fully recover itself on its own.
**
Hi @Ke_James as mentioned in my response to similar comments in another thread, we cater first to the largest demographic (simple onboarding and recovery with Magic Backups), then we fan out from there for more advanced users.
Manual backup recovery is planned and I am working on fast tracking it to an upcoming release.
For the reconnection stuff on the beta firmware, please provide copies of your Envoy and Passport Prime logs.
Since I can’t get into Passport Prime, I’m only able to export the Envoy logs.The forum doesn’t seem to allow file uploads. What’s the best way for me to send you the Envoy log file?
Thanks for the logs. They show that Envoy was not accepting the Passport Prime pairing QR during these attempts. There also appears to be leftover Envoy state from before the wipe, so the cleanest next step is to remove that state and start a fresh device pairing.
In Envoy, go to Devices. If Passport Prime is listed, tap it and remove it.
Remove any existing Passport Prime entry from your phone:
iPhone: Go to Settings > Privacy & Security > Accessories and remove Passport Prime if listed.
Android: Go to Settings > Connected devices > Previously connected devices or Bluetooth, then forget Passport Prime if listed. The exact wording varies by phone.
Force-close and reopen Envoy.
Restart Passport Prime and ensure it shows a static QR code during the first part of onboarding
Go to Devices, tap +, and add Passport Prime as a new device. Start with the initial setup QR and allow Envoy to advance automatically when Passport Prime switches to the animated QR.
If it still fails, please tell me exactly what each screen shows and export fresh Envoy logs immediately after the attempt.
Manual recovery is scheduled for 1.5. Best estimate for this given we are still in the beta phase of 1.4 would be ~2 months. This does not include files, which are not currently a part of any backup.
I do not have any timeframes for that part right now, but @Jack and I have a call to discuss later today.
I have to say, this is frustrating. Independent backup was originally discussed for 1.3, then it still wasn’t there in 1.4, and now it’s pushed to 1.5 — while files still aren’t included at all.
At some point, this raises a more fundamental question: what does “sovereign device” really mean if the device still cannot independently back up and fully restore itself?
Prime has gained a lot of ambitious features, but I feel the product focus has drifted away from the basics. Reliable, self-contained backup and recovery should be foundational, not something deferred release after release.
I have put this thread in front of the team. Independent recovery has moved across releases, and that is a scheduling, not a loss of focus.
One correction on files. I am not aware of us ever saying files would be part of a manual backup.
On the roadmap stuff - We are a small team, and we point engineering at where we see the most demand. The consequence is that sometimes means that features power users seek are the ones that move, because far fewer people ask for them. Most of our customers are on Magic Backups and never touch a manual flow.
We appreciate the candid feedback as always, it does help us.
Have you considered an option where magic backups can be redirected to a self hosted option? Use the same backup and recovery flow but target it either at a private server or something like Proton Drive (or even Google Drive since it end to end encrpted backup files)?
