Trezor hidden wallet: confirmed BTC on-chain, passphrase not reproducing

[jwsutherland]

Bitcoin Client Software and Version Number:
Trezor Model T using Trezor Suite (desktop, current version).
Also verified independently using Sparrow Wallet in watch-only mode.

Operating System:
N/A (not a client software bug).

System Hardware Specs:
N/A.

Description of Problem:
I transferred BTC from Newton (Canadian exchange) to a self-custodied address generated by my Trezor Model T.

The BTC exists, is fully confirmed on-chain, and has never moved since the original transaction. However, I cannot currently access the wallet that derived this address.

This strongly indicates that the address was created under a BIP-39 passphrase-protected (hidden) wallet and that I am currently entering an incorrect passphrase.

Important clarifications:

There has only ever been one Trezor device.

The 12-word recovery seed is correct and verified.

Entering an incorrect passphrase opens a valid but unrelated empty wallet (expected behavior).

This is not a transaction failure, theft, or exchange issue.

Any Related Addresses:
bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv

Any Related Transaction IDs:
(Available if needed — omitted here for brevity, but the address above shows the confirmed balance on mempool.space.)

Screenshot of the Problem:
Not applicable — no client error message; behavior is expected for an incorrect passphrase.

Log Files from the Bitcoin Client:
Not applicable.

What I am asking:
I understand that a forgotten passphrase cannot be “recovered” in the general case. I am looking for expert confirmation on the following points:

Whether there are any remaining derivation-path edge cases (e.g., legacy vs native SegWit) worth ruling out given this setup.

Whether offline passphrase reconstruction (bounded candidate testing using the known seed and funded address) is the only remaining technically sound approach.

Confirmation that no other wallet-level explanation exists beyond an unreproduced passphrase.

I am not asking for hacks, shortcuts, or guarantees — only technical validation and guidance on whether anything remains to be checked.

Thank you for your time and expertise.

[FinneysTrueVision]

Any Related Addresses:
bc1qgn5raset2n9m0npn50xnyadmlvdgctgdtum3mv

Any Related Transaction IDs:
(Available if needed — omitted here for brevity, but the address above shows the confirmed balance on mempool.space.)

That is not a valid Bitcoin address.



Trezor Suite does not let you load any more accounts if there is already one empty Bitcoin account in the application. If you have already checked different account indexes on Sparrow, then it is most likely that you have the incorrect passphrase for the wallet and will have to use recovery software to brute force it to regain access.