Sending a transaction from a Trezor One with outdated firmware and lost seed

[super_merry]

I have a Trezor One with firmware 1.4.2 and I have lost the recovery seed. I'd like to send a transaction from the device to another address that I control. However, because of its outdated firmware, only older versions of wallet software can interface with the device. I've found that Electrum 3.0.6 is the latest version of that wallet that can work with this firmware.

The firmware update process on certain versions will wipe the device, and if the device gets disconnected during the process it will be wiped. So I'd like to avoid the firmware updates until I'm sure that the coins are in a wallet I can control.

Would it be possible to create an unsigned transaction on a newer wallet without the private key, then somehow signing it manually with the device before sending it to the network using the newer wallet?

[ranochigo]

Can you get the master public key of the Trezor?

You can download a Electrum 3.3.8 to import the master public key and create a transaction from there, transfer it to an offline instance of Electrum 3.0.6 and then sign it from there before transferring it back to Electrum 3.3.8 to broadcast. Electrum 4.0.1 and above has incompatible raw transaction formats with older versions.

[dkbit98]

Funny thing that I found exact same question word to word posted before on other places, and not to say that this is not you asking same question on multiple places but I am a bit suspicious after seeing what people are capable doing.

Other than connecting Trezor with older Electrum wallet version, you can also try connecting it with Exodus wallet and installing Trezor bridge only for that purpose.
I would not recommend using this option all the time, but only for this purpose if it works for you.

I have a Trezor One with firmware 1.4.2 and I have lost the recovery seed. I'd like to send a transaction from the device to another address that I control. However, because of its outdated firmware, only older versions of wallet software can interface with the device. I've found that Electrum 3.0.6 is the latest version of that wallet that can work with this firmware.

The firmware update process on certain versions will wipe the device, and if the device gets disconnected during the process it will be wiped. So I'd like to avoid the firmware updates until I'm sure that the coins are in a wallet I can control.

Would it be possible to create an unsigned transaction on a newer wallet without the private key, then somehow signing it manually with the device before sending it to the network using the newer wallet?

https://bitcoin.stackexchange.com/questions/102759/sending-a-transaction-from-a-trezor-one-with-outdated-firmware-and-lost-recovery
https://blickblock.re/sending-a-transaction-from-a-trezor-one-with-outdated-firmware-and-lost-recovery-seed/

[super_merry]

Can you get the master public key of the Trezor?

You can download a Electrum 3.3.8 to import the master public key and create a transaction from there, transfer it to an offline instance of Electrum 3.0.6 and then sign it from there before transferring it back to Electrum 3.3.8 to broadcast. Electrum 4.0.1 and above has incompatible raw transaction formats with older versions.

I tried doing this and got this error from Electrum 3.0.6 when attempting to sign the transaction I created in 3.3.8:

Electrum was unable to deserialize the transaction: unpack_from requires a buffer of at least 4 bytes

Funny thing that I found exact same question word to word posted before on other places, and not to say that this is not you asking same question on multiple places but I am a bit suspicious after seeing what people are capable doing.

Yes, that was me asking on the Bitcoin StackExchange, not sure what blickblock.re is though.

[ranochigo]

I tried doing this and got this error from Electrum 3.0.6 when attempting to sign the transaction I created in 3.3.8:

Electrum was unable to deserialize the transaction: unpack_from requires a buffer of at least 4 bytes

I read through the release notes between that and I found that the format was actually changed slightly in 3.2.0 which results in the raw TXes being incompatible.

If you don't mind, you can manually script the raw transaction using Coinb.in. Just key in the addresses which contains the funds and structure it exactly like the raw transaction that you were trying to sign (ie. the same output amount and the same transaction fees). Afterwards, just press Submit for the raw transaction and use your Electrum 3.0.6 to sign. That should work fine.

[super_merry]

I read through the release notes between that and I found that the format was actually changed slightly in 3.2.0 which results in the raw TXes being incompatible.

If you don't mind, you can manually script the raw transaction using Coinb.in. Just key in the addresses which contains the funds and structure it exactly like the raw transaction that you were trying to sign (ie. the same output amount and the same transaction fees). Afterwards, just press Submit for the raw transaction and use your Electrum 3.0.6 to sign. That should work fine.

I followed this and uploaded a screenshot of what happens when I load the transaction here: https://i.imgur.com/9Vx45PG.png

It says that the transaction is signed and the 'Sign' button is grayed out.

[ranochigo]

I followed this and uploaded a screenshot of what happens when I load the transaction here: https://i.imgur.com/9Vx45PG.png

It says that the transaction is signed and the 'Sign' button is grayed out.

Hmm. Seems like Electrum was using a different serialization format since many releases ago.

I'm unfortunately out of ideas now. Don't think Electrum 3.0.6 is able to connect to any peers now. The only risk is the phishing message since the unprotected RPC was fixed the version prior. Perhaps some other members can chime in to help.

[igor72]

I would try connecting Electrum 3.0.6 to Bitcoin Core using EPS.

[super_merry]

I would try connecting Electrum 3.0.6 to Bitcoin Core using EPS.

Here's a screenshot of what the history tab looks like in Electron 3.0.6 when connected to EPS: https://i.ibb.co/86B2BgZ/electrum-screenshot-1.png

When I go to the send tab, as soon as I type anything into the amount field, Electrum crashes. Same goes for clicking the 'Max' button.

[igor72]

When I go to the send tab, as soon as I type anything into the amount field, Electrum crashes. Same goes for clicking the 'Max' button.

Try making a watch-only wallet (from xpub) in version 3.1.3 (this is the latest version compatible with 3.0.6) and create a transaction there, and then load it for signing in version 3.0.6.

You can also try connecting your Trezor to Mycelium wallet.

[HCP]

It might also be worth trying to connect your Trezor to "Sparrow" Wallet (https://sparrowwallet.com/) and see if it is able to work directly with the older firmware. You might get lucky and be able to just create and sign the transaction without needing to mess about with unsigned transactions etc.

[super_merry]

Try making a watch-only wallet (from xpub) in version 3.1.3 (this is the latest version compatible with 3.0.6) and create a transaction there, and then load it for signing in version 3.0.6.

This worked! Thank you!