Unfortunately, I am forced to turn to the community with my problem, because the service provider could not a to help me (TicketID:166860).
Without excluding and avoiding my own responsibility, my goal is that all
I can examine a possible solution.
Summary:
Trezor forced a firmware update for proper display of Ethereum , in February 2023.
During the update process, the Trezor device froze and had to be reset using Seed.
After updating the firmware, Trezor Suite does not show the previous wallet (addresses:
different than before which the coins are currently on).
After the firmware update, the addresses in the wallet do not match the previous addresses, a
the balances, unlike the previous ones, show 0 balances.
Previous addresses still have cryptos, they are still visible.
Coins are allowed.
The seed works ( we are in a wallet, the balance is zero)
The hidden wallet was not created.
For previous logins and checks (before firmware update), everything was fine.
The problem started after the 02/02/2023 firmware update and has persisted ever since.
The wallet was created in 2017 with an original Trezor Model One device.
We have never had another wallet, never had another seed, never used another Trezor
device.
This is the only place where we store crypto.
The seed was recorded in writing.
The seed was not checked until the problem occurred.
Everything worked flawlessly until the February 2023 firmware update.
The firmware update failed the first time.
Wallet failed to recover after successful firmware update.
Currently, the seed points to a live wallet, but not ours, with zero balance,
the addresses are different. Scary!!!
You can find our cryptos at the previous addresses.
The crypto was credited to the wallet in 2017.
Tresor was new, the core was fixed exactly during installation, the cryptos were
they are visible during all checks and were available in the standard account created when a
a transaction has been initiated.
After installation (flashing) the seed was not checked again until the problem occurred, but
this was not necessary considering everything worked flawlessly. By the way
the need for this was never brought to our attention, e.g. before firmware update!)
What did we do to solve the problem?
The seed was recorded in writing.
The seed has been checked. It works, it’s fine. Balances show 0.
No password was entered either before or during the firmware update. We have a normal wallet.
Coins have been authorized.
We checked the possibility of segwit and legacy accounts.
We also checked the possibility of spelling words.
As far as we know - via internet -, there was a case in the past when the new wallet was generalized with an incorrect seed upon creation. This error was later corrected by Trezor and the problem was solved. It is possible that did this happen to us too? Please help: you may know someone with a similar problem
faced, who can give advice on the solution, to whom we can turn with confidence
with our questions?!