Trezor firmware

This commit is a routine UI translation update for the Trezor hardware wallet's device menu. It replaces hard-coded English text strings with references to the device's translation system so the menu can be displayed in multiple languages. There are no security fixes or functional behavior changes.

This is a routine user-interface cleanup for the upcoming Trezor 'Eckhart' device layout. It makes menu divider lines always appear instead of requiring each screen to opt in. There is no security change, no bug fix, and no handling of secrets or sensitive data.

This is a routine user-interface cleanup for the upcoming Trezor Safe 5 (Eckhart layout). It makes header buttons slightly larger and easier to tap, and switches several screens to use a shared 'close button' helper. The only functional change visible in the code is a larger touch target and a small visual radius on header icon buttons; there is no evidence this affects security-sensitive behavior such as transaction confirmation, PIN entry, or seed handling. The huge list of changed test hashes is simply because every screen screenshot changed by a few pixels.

This commit is a routine user-interface polish change for the Trezor hardware wallet. It updates the on-screen button label and color when changing the device's name, and adds a short 'Device name changed' confirmation screen afterward. There is no security fix or vulnerability here.

This is a cosmetic user-interface tweak for the Trezor hardware wallet's new 'Eckhart' layout. It makes the up/down pagination buttons the same size and updates the expected screen snapshots used in automated tests. There is no indication it fixes or introduces any security vulnerability.

This commit is a routine user-interface styling change for the Trezor hardware wallet's QR-code display screen. It swaps the foreground and background colors (inverts them) and adjusts the layout code accordingly. There is no indication this change affects security, cryptography, private keys, or transaction signing. The large number of changed test hashes is simply because the on-screen appearance changed, which is expected for a visual update.

This commit replaces a pre-built bootloader binary file for the T3W1 hardware model and updates the matching cryptographic hashes in a header file. The change itself is a routine binary refresh with no source-code diff, no changelog entry, and no stated security relevance. There is no visible evidence of a vulnerability or malicious change, but the opaque binary blob cannot be independently verified from the commit alone.

This is a one-character logging fix in a Trezor firmware debug message. It adds a colon and space to a log string so the formatting reads correctly. There is no security relevance: no behavior changes, no crash, no data exposure, and no vulnerability is introduced or fixed.

This small patch fixes a bug in the Trezor hardware wallet's message-handling code where certain errors could cause the device to loop forever instead of stopping. Before the fix, if a specific kind of error happened while processing a message, the code would just log it and continue running, potentially retrying the same failing work endlessly. The patch makes the handler return after logging, breaking the loop. This could prevent device lock-ups or unresponsiveness, but the change alone does not clearly enable remote theft of funds or private keys.

This commit fixes a bug where opening the device menu on a Trezor hardware wallet would crash with a red screen of death (RSOD) if a Bluetooth device was connected. The fix simply increases the maximum number of subscreens the menu system can handle from 8 to 10, because the Bluetooth menu entries push the count over the previous limit. There is no evidence this is exploitable by an attacker.

This commit is a routine maintenance update to the project's Python dependency lock file (poetry.lock). It was generated because the team upgraded their Poetry tool version from 1.8.5 to 2.1.3, matching the version available in their Nix development environment. The file changes are purely metadata format differences produced by the newer Poetry version, plus one local package version bump (tvl from 0.10.1 to 2.2). There is no indication of a security fix, vulnerability patch, or code behavior change.

This is a tiny user-interface fix in the Trezor Python command-line library. When a user runs a command on a brand-new, uninitialised Trezor, the tool now prints 'Device is not initialized.' instead of falling through to a generic 'Failed to find a Trezor device.' message. It does not change device firmware, crypto handling, or any security boundary; it only makes the error text clearer.

This commit adds a new power-saving feature: pressing the physical power button on a Trezor device can now suspend the firmware. If the device has a PIN and is currently unlocked, the button press first locks the device (ending any active workflow) and then triggers a shutdown. Otherwise, the device is suspended and later woken up. The change is a feature addition, not a fix for a known security bug, and there is no evidence in the commit or supplied references that it addresses a vulnerability.

This commit doubles the stack memory size for the Trezor hardware wallet's production-test firmware from 12 KB to 24 KB. A stack that is too small can cause crashes (the commit notes 'Overflow causes UsageFault'). There is no direct evidence in the commit that this is exploitable as a security vulnerability, and the change appears to be a stability fix for a special manufacturing/QA mode rather than the normal user-facing wallet firmware.

This commit is a routine build/dependency housekeeping change. It updates Python version constraints and the internal 'trezor' package version requirement so that the project's Poetry lock file can be regenerated without conflicts. There is no indication this fixes a security vulnerability or changes runtime behavior of the Trezor firmware or wallet software.

This commit changes the vibration pattern that the Trezor hardware wallet produces when it powers on. It adds a new dedicated 'power on' haptic effect and uses it instead of reusing the existing button-press vibration. There is no security relevance in this change.

This commit finishes a previously stubbed-out feature in Trezor's core firmware: automatic retransmission of lost USB packets during a secure protocol called THP. Before this change, the code had a TODO comment where retransmissions should have been. After this change, the device will resend a packet up to 50 times with an increasing timeout if it does not receive an acknowledgment. This is a normal reliability improvement, but because it touches low-level packet handling and timeout logic, it could introduce subtle bugs such as the device hanging, retrying forever in edge cases, or misinterpreting a delayed packet as a fresh one.

This is a test-only change for the Trezor hardware wallet firmware. It adds a small cleanup step in the debug/test code path that waits for a debug-link helper task to finish before restarting the event loop used by the new THP (Trezor Host Protocol) code. It does not change normal user-facing behavior and is not a security fix for a live vulnerability.

This is a test-only change that replaces a fixed 0.1-second sleep with an explicit device-readiness check before starting screen recordings in UI tests. It does not touch firmware, wallet logic, cryptography, or any production code path, so it has no direct security relevance for end users.

This commit is a large internal refactor of the Trezor firmware's THP (Trezor Host Protocol) event loop and message handling. It removes an old global buffer-locking scheme and a separate retransmission task, replacing them with per-channel buffer objects and a simpler synchronous send-and-wait-for-ACK flow. The change also removes the old `loop.clear()` restart-on-error behavior in favor of explicitly joining workflows before restarting. The diff itself is a feature rewrite with no explicit security claims, but it touches sensitive code paths (encrypted channel setup, session scheduling, buffer management) and removes some safety checks, so it should be reviewed carefully for regressions.

This is a one-line fix in Trezor's factory production-test code for the Tropic secure chip. It changes a preprocessor condition from an apparently wrong/placeholder macro name 'ABAB' to the intended 'TROPIC_TESTING_KEYS'. The effect is to ensure that testing-only cryptographic keys are compiled in only when the proper configuration flag is set, rather than under an unrelated or accidental flag. This reduces the risk that production devices could be built with test keys instead of real factory keys.

This commit fixes a command in Trezor's production-test firmware that checks how many arguments a user passed. The old check rejected commands with more than zero arguments, but accidentally allowed commands with zero arguments through. The fix requires exactly one argument. The affected command is part of a low-level factory/testing tool, not the normal wallet firmware users run every day.

This commit fixes the formatting of a debug/production-test command output for a wireless charging chip. It changes how numbers are printed (decimal to hexadecimal) and moves the data values from a 'PROGRESS' line to the 'OK' line. There is no security issue here—it's a cosmetic/output-formatting fix in a factory testing tool.

This commit fixes a minor formatting bug in the Trezor production-test command-line tool. Previously, every response line in non-interactive mode had an extra blank line (CRLF) appended. The change moves that blank line so it only appears in interactive mode, where it serves as a prompt separator. There is no security relevance in the commit or diff.

This commit removes a single leftover debug logging line that printed the contents of a channel allocation packet. It is a cleanup change with no security relevance: the log line was informational, not an error, and removing it does not fix a vulnerability or change any behavior an attacker could exploit.