Trezor firmware

This update fixes a bug in the Trezor Python library where reconnecting to a Trezor device could fail if an old, unread response was still waiting in the communication channel. The fix makes the library clear out up to 10 stale responses before it checks whether the device speaks the older protocol v1. A new test simulates a host disconnect mid-operation and verifies that a new client can reconnect successfully.

This commit adds the data structures and translations needed to support two new Tron blockchain operations—delegating and undelegating staked resources—but does not include the actual code that would handle or sign those operations. It also moves a few shared user-interface labels from the EOS section to a common 'words' section. There is no security issue visible in this patch.

This is a small cleanup change in the Rust Trezor client library. It removes an unused `script_type` parameter from the `get_public_key()` function and its callers. The parameter was being set in the request to the Trezor device, but the device does not actually need or use it for this operation. There is no security vulnerability here—just code simplification.

This commit is a build-system cleanup. It removes separate 'emulator board' configuration files and instead makes the emulator reuse the real hardware board's settings, only swapping in a special emulator header and the Unix display/touch drivers. There is no user-facing change or security fix visible in the diff.

This commit adds new configuration files describing Trezor hardware models and build targets. It is a build-system feature with no user-facing behavior change and no apparent security relevance.

This commit is a code-quality fix in the Cardano app of the Trezor firmware. It removes direct access to the global translation object (TR) at the time the Python module is first loaded, and instead reads the translated strings only when they are actually needed. This avoids a potential startup-time crash or import-order problem if the translation system is not fully initialized when the module is imported. There is no direct evidence in the commit that this is an exploitable security vulnerability.

This commit only adds comments explaining existing behavior in a Trezor firmware source file. No code logic was changed, no bugs were fixed, and no security vulnerability is present in the diff.

This update fixes a bug in how the Trezor device handles on-screen button prompts when communication with the host computer hits errors or timeouts. Previously, an input/output problem during a backup could cause the device to send extra button requests or errors after the workflow should have ended, and the final 'Success' message could fail to send. The fix makes the device ignore further host messages until the backup workflow finishes, and lets users cancel other workflows through a new waiting screen. It is a reliability and defensive fix rather than a clear-cut remote exploit.

This commit only changes user-facing text strings and their generated lookup tables in the Trezor firmware. It rewords a message about communication problems and adds a second, milder version of the message. There are no code behavior changes, no fixes to logic bugs, and no security-relevant functionality altered.

This is a routine automated dependency update by Dependabot that bumps the urllib3 library from version 2.6.3 to 2.7.0 inside a small internal testing tool (automatic_battery_tester). The change is a single line in a requirements file. There is no indication in the commit that this fixes a security issue, and the tool is not part of the Trezor firmware that runs on user devices.

This commit only changes a test file so that a Decred signing test is skipped when the firmware is built in Bitcoin-only mode. It does not modify any production firmware code, wallet behavior, or cryptographic logic. There is no security issue here.

This commit only adds a new test case for Solana message signing with 64 cosigners and updates the expected screen snapshots used by automated testing. It does not change any firmware code that runs on the Trezor device, so it cannot introduce a security vulnerability or fix one.

This is a minor GitHub workflow change that stops an automatic pull-request assignment job from running when the pull request is opened by a bot account (whose username ends with '[bot]'). It has no security relevance to the Trezor firmware itself or to user funds.

This commit fixes a crash in the Trezor device's on-screen 'About device' menu when the device lacks a serial number. It wraps the serial-number lookup in a try/except block and displays 'N/A' instead of crashing. There is no indication this can be exploited by an attacker; it is a robustness fix for a user-interface screen.

This commit only renames a single JSON key from '_reserved' to 'reserved' across 14 vendor header configuration files. No security settings, permissions, or values are changed. It appears to be a routine cleanup to match a naming convention elsewhere in the build tooling.

This commit simply moves a small helper function that checks whether a string contains only normal printable characters from one file to another shared location. No behavior changes, no bug fixes, and no security implications are visible in the code change itself.

This commit only adds new automated tests for a Solana feature that signs and verifies off-chain messages. It does not change the actual wallet firmware code that users rely on, so it cannot by itself introduce a security vulnerability or fix one. The tests exercise parsing, signing, and verification logic and include checks for invalid inputs.

This commit changes one German translation string to add the word 'ist' (is) for consistency, and updates the corresponding translation signature metadata. There is no code or security change.

This commit only updates translated text strings in Czech, German, Spanish, French, and Portuguese for the Trezor hardware wallet firmware. It changes wording for things like Ethereum transaction prompts, Bluetooth device labels, backup/recovery instructions, and passphrase prompts. There are no code logic changes, no new features, and no security fixes.

This commit is a routine user-interface update for the Trezor hardware wallet's 'About' screen. It adds a 'Made in Ostrava, Czechia' label and, on devices that use serial numbers, displays the serial number. There is no security-relevant change.

This commit only adds new test cases for Ethereum transaction signing. It does not change any production code, so it cannot introduce a security vulnerability by itself. The test data includes sample transactions and their expected signatures, used to verify the device signs complex DeFi transactions correctly.

This is a small internal tuning change for Trezor's Ethereum app. It increases the amount of transaction data the device preloads from 4 KB to 6 KB before asking the user to confirm. The only visible effect is fewer back-and-forth data requests for Ethereum transactions with large data payloads. There is no direct security fix or vulnerability being patched.

This commit simply restores a missing Python test dependency called pytest-retry. It only affects the project's testing environment and does not change any code that runs on the Trezor device or any production software. There is no security issue here.

This commit is a routine synchronization of translated user-interface text for the Trezor hardware wallet. It updates wording, adds missing translations, and removes obsolete translation keys across several language files. There are no code changes that affect security, cryptography, transaction signing, or device behavior.

This update fixes how Trezor displays Solana transactions that use Address Lookup Tables (ALTs). Previously, the device could misidentify or fail to show the real recipient when an ALT was involved, which might let an attacker trick a user into approving a transfer to an unexpected address. The patch also blocks ALT references in payment requests and some staking flows where the device cannot safely verify the destination.