Use this Foundation Passport firmware troubleshooting page when an update appears stuck, Passport is in update mode, Envoy pairing changes after firmware work, or an update prompt looks suspicious.
Independent wallet security guidance. This site is not Foundation Passport.
Foundation Passport help topics
Wallet security
Quick issue summary
Ledger and Trezor support teams should never ask for a recovery phrase, seed phrase, private key, or remote access to a wallet.
Recently Reported Issues
A Foundation Passport firmware update problem should be handled through official Foundation instructions with recovery phrase safety confirmed offline and no seed words entered into websites, chats, or unverified prompts.
Common wallet topics include Foundation Passport firmware update issue, stuck update, firmware mode, Envoy pairing after update, QR signing after firmware, backup readiness concern, or fake Foundation Passport update warning.
Never share your recovery phrase, seed phrase, private keys, or PIN.
Wallet topics
Firmware state can cause connection and pairing issues.
OpenIf Envoy cannot recognize Passport after an update, use detection checks.
OpenRetest QR signing separately after firmware work.
OpenIf Bitcoin balance changed after update, check sync and account context.
OpenReview recovery boundaries before any reset or restore step.
OpenReturn to Foundation Passport support for setup and update help.
OpenReport non-private firmware symptoms to PhraseWallet.
OpenEnvoy app troubleshooting is safest when you separate display, sync, device, firmware, and recovery phrase concerns before changing wallet settings. Use official Foundation Passport support links for device-specific instructions.
Use these checks to separate ordinary setup friction from wallet safety risk before you reset, restore, reinstall, or open wallet support portals.
Use a data-capable cable, confirm computer permissions, avoid untrusted browser prompts, and check whether the official app recognizes the device before restoring anything.
Handle firmware updates only through verified official software. A firmware prompt should not require typing seed words into a website, chat, or support form.
Zero balance or missing transactions can come from the wrong account, network, passphrase, derivation path, sync delay, or exchange withdrawal still pending.
Keep the phrase offline and private. Do not photograph it, paste it into support, or use a recovery check page from an ad, email, DM, or search result.
Read the device screen carefully before approving. If the destination, network, fee, or contract request is unexpected, reject and investigate first.
Avoid remote access, paid recovery, messaging-app helpers, fake live chat pages, and anyone asking to be added to your wallet or computer.
Start with the most common causes before resetting the wallet, restoring from a recovery phrase, or trusting a support message.
Step 1
Use official Foundation sources for firmware instructions. Do not continue from a link sent in a chat, comment, email, or advertisement.
Step 2
Make sure the recovery phrase is stored offline before risky update work, but never type it into an update page or support form.
Step 3
Review the exact Passport screen, Envoy version, battery or power state, and whether the device is still in update mode before repeating steps.
Step 4
After firmware work, verify Envoy pairing, Bitcoin account view, QR signing, address display, and transaction review before relying on the wallet.
Confirm the firmware instructions, file source, and device state from official Foundation materials before continuing.
Check whether pairing records need refreshing and whether balances or addresses need time to resync after update work.
If signing fails after firmware work, retest scan direction, brightness, transaction details, and final broadcast before restoring.
Expected flow
Firmware update troubleshooting is safest when you move in order: verify the official update path, confirm backup readiness, complete the update, reconnect, then let accounts rescan before changing wallet settings.
Use official Foundation Passport instructions and confirm Envoy app or the official update path before starting.
Make sure the recovery phrase is stored offline, but do not type it into a website, chat, or support form.
After the firmware step, reconnect the device, approve any device prompt, reopen the official app if needed, and let account discovery run again.
Confirm selected accounts, networks, addresses, and token visibility before assuming a post-update balance delay is a loss of funds.
Experiences may vary depending on wallet brand, device state, app version, network congestion, firmware status, and how the wallet was originally backed up.
What users commonly report: Users often report balance delays or device detection problems after firmware updates until the wallet reconnects, rescans accounts, and refreshes the selected network view.
For official Foundation Passport help, downloads, updates, or contact options, use Foundation Passport's official portal and verified official channels. This page helps you prepare safe, non-private context before opening support portals.
No legitimate wallet guidance should need your recovery phrase.
A recovery phrase controls wallet restoration. Treat it as private self-custody information and review how phrases work before using any wallet.
Community reports
Foundation Passport troubleshooting reports often involve Envoy pairing, QR signing, firmware prompts, Bitcoin account display, recovery planning, and fake support warnings. These examples avoid private wallet data and focus on the support pattern.
These examples are informational and reflect common user-reported wallet issues. Never share your recovery phrase, seed phrase, private keys, PIN, or wallet backup with anyone. Official wallet support should never ask for your recovery phrase.
“Foundation Passport shows an empty or delayed balance after the app or firmware update.”
Users often report temporary balance delays after firmware or app updates until the device reconnects, account discovery runs, and the correct network or token view refreshes.
“Foundation Passport QR signing stopped working after an app update or reconnect.”
QR-signing problems commonly involve app pairing records, camera focus, unsigned transaction QR content, firmware validation, signed QR broadcast, or a network mismatch.
“A support message said it could fix Foundation Passport if I shared my seed phrase or screen.”
Fake support often appears during update, restore, missing-balance, and QR-signing stress. No legitimate wallet support flow should ask for recovery words, private keys, PINs, or remote access.
“The restore finished, but Foundation Passport is showing different addresses or no expected funds.”
Some restores initially show empty wallets until the right account type, passphrase context, derivation path, network, or imported account view is selected.
Report wallet issue
Submit a non-secret wallet problem for moderated review and safer routing. PhraseWallet is independent and this is not official wallet support or emergency recovery assistance.
Never enter your recovery phrase, private key, password, PIN, or payment details.
Common wallet issues
Use these maintained support paths to move from a symptom to the right setup, recovery, troubleshooting, or security help without sharing private wallet data.
Related problems
If this page is close but not exact, check these nearby support topics so the next step matches the failure pattern.
Use the Foundation Passport support hub for Envoy pairing, QR signing, firmware, recovery, balance, and fake support warning paths.
Open helpPSBT scan direction, camera focus, firmware state, and transaction review can block Foundation Passport signing.
Open helpAvoid cloned downloads, seed phrase validators, remote access helpers, and messages asking for private wallet data.
Open helpOfficial wallet support should never ask for your recovery phrase, seed phrase, private keys, PIN, wallet backup, screen sharing, or remote access. Verify downloads, QR tools, and update prompts on the official wallet site before acting.
FAQ
It may be waiting for a device prompt, official update sequence, current Envoy version, battery or power stability, or post-update pairing refresh.
No. Backup readiness matters, but a firmware update page, support chat, or validation form should not ask for recovery words.
Check Envoy pairing, selected Bitcoin account, balance display, QR signing, and device transaction review flow.
Device model, firmware screen state, Envoy version if known, phone model, exact error, and steps tried. Never include recovery words or private keys.
Use official Foundation Passport support links for device-specific support, and keep private wallet recovery data offline while you troubleshoot.