There is no error message because it doesn't recognise a different password as an error. It just goes ahead and generates a different set of keys with the 'new' password as part of the seed.

If it did know your password (so that it could generate an error message) it would have to store it somewhere and that would be a less secure (and different) methodology.

I've done multiple firmware updates without problem, but you are alays warned to make sure you have a backup of the mnemonic prior to upgrading. Are seeing the same wallet addresses on the new firmware ? If you have no passphrase you should see the same addresses, and if you have entered the same passphrase again you should see the same HD tree. Do you have any old transactions in from phone wallet to Trezor accounts you can check ?

Edit : Must have been I page back or something....

TREZOR The Bitcoin Safe Now Available on Amazon.com

https://www.reddit.com/r/Bitcoin/comments/2sjk1j/trezor_the_bitcoin_safe_now_available_on_amazoncom/

Any idea how the trezor could be used to sign longer messages? Like if you wanted to sign a contract that was a few pages long.

I know for maximum security you need to be able to see what you are signing on the trezor but maybe there is some reasonable middle ground for when people dont need that much security? I mean even if someone is spoofing client side the worst they could do is trick you into signing something other than what you intended. As long as it wasn't a transaction than its an acceptable risk. By tricking you in this way they wouldnt actually be getting your private key. And unless they are in such control over your computer that they are man in the middle brute force projecting pixels onto your screen, or part of some vast conspiracy, when you went to verify your signature with a third party you would immediately know you had been compromised in said relatively contained fashion.

It could be bad though if they tricked you into signing a transaction. Does anyone suppose there is a way for the trezor to be sure that, when it is signing a message that is too long to be reviewed on the trezor screen that at the very least it is signing something other than a transaction? One idea is that the trezor forces a concatination onto the end of any long message it signed. For example: signed using trezor. Any message that was being signed that ended with "signed using trezor" shouldnt be validated by the bitcoin network as a transaction. I know that transaction scripting is fairly robust in some ways but not that robust, is it?

Ok anyway that was less of a simple question and more of a stream of consciousness but thoughts?

Everything digital could be reduced to a single hash. Then sign the hash that corresponds to the document.

I am one hundred percent positive nobody can steal any coins from my Trezor. For me "watch only" on a Trezor is a fools errand, in other words, not necessary. I can even give out my 24 word seed in proper order and know I have at least an hour to transfer my funds to a new wallet because of passphrase.

It still wouldn't have been appropriate for me to say. Here is a hash of the doccument: blablabla. Hash the document yourself to make sure you get the same hash. Now here is a signature of that hash: blablabla. Not as a businessman. You cant put barriers like that between people and your service. Even though in theory it is as simple as you said if they are using linux.

And actually it wouldnt have worked with bitrated.com (which is where i wanted to use an address stored on my trezor but couldn't). It's an automated process. I cant "explain" to it that its a signature of the hash of the document rather than the signature of the document that it asked for.

Are you sure you entered the right passphrase?

Does anyone know why outgoing transactions take longer to confirm in mytrezor than incoming ones?

When sending coins to the trezor from my desktop client, they show up as confirmed on mytrezor after one confirmation, but when sending coins from the trezor to my desktop client they take longer. Mytrezor shows it as unconfirmed even though my desktop client reports 3of6 confirmations.

Edit: 6 confirmations in my desktop client (bitcoin core), but still shows as unconfirmed in mytrezor...