how to recover segwit bitcoin in taproot?

[q7naistar]

i exported these public keys from my exodus wallet: xpub6DA, zpub6ruWS, zpub6rhPfS.

from what i understand, xpub is for older addresses, and zpub is an extended public key for segwit (bc1q-starting) and taproot (bc1p-starting) addresses.

exodus gave no warnings, so i messed up and used a taproot address to receive bitcoin. now it's not showing up in my wallet.

i found a transaction on trezor at m/84'/0'/1'/0/1. i tried importing my seed phrase and setting the path to m/84'/0'/1' like online guides suggest, but still no transaction.

my wallet says it's wallet #1 for my zpub6ruWS address. so basically, my bitcoin is complicatedly stuck in a taproot address.

how can i get my money back?

[Satofan44]

exodus gave no warnings, so i messed up and used a taproot address to receive bitcoin. now it's not showing up in my wallet.

If you are sure it went to a taproot address then the issue is with the path.

BIP 44: m/44'/0'/0' (1addresses)
BIP 49: m/49'/0'/0' (3addresses)
BIP 84: m/84'/0'/0' (bc1qaddresses)
BIP 86: m/86'/0'/0' (bc1paddresses) - This is Taproot.

https://learnmeabitcoin.com/technical/keys/hd-wallets/derivation-paths/

i found a transaction on trezor at m/84'/0'/1'/0/1. i tried importing my seed phrase and setting the path to m/84'/0'/1' like online guides suggest, but still no transaction.

my wallet says it's wallet #1 for my zpub6ruWS address. so basically, my bitcoin is complicatedly stuck in a taproot address.

how can i get my money back?

How can you be sure it is Taproot if you say it is in this public key? According to https://slips.readthedocs.io/en/latest/slip-0132/:

BIP-0084 proposes a native-SegWit derivation scheme, encoding P2WPKH addresses in Bech32. However, the extended serialization format is presented with a zpub prefix but no version bytes. This is an issue since multiple values of the version bytes may encode to the same prefix.

In any case you can try out the other derivation paths, there is no harm in trying.