Trezor firmware

This commit fixes a bug in the factory testing tool (prodtest) for Trezor hardware wallets that use a Tropic secure chip. The previous code accidentally marked the Tropic chip as initialized even when initialization actually failed, and it also shut down the chip during cleanup even on success. The fix makes the success/failure status accurate and stops the premature shutdown, so production tests can run correctly.

This change fixes how the Trezor hardware wallet waits for a small security chip called 'Tropic' to finish booting before starting a secure session. Previously, the code used a fixed 100-millisecond delay, which could be too short and cause the chip to respond with 'busy' errors. Now it actively polls the chip for up to one second until it reports it is ready. This is a reliability and robustness improvement rather than a fix for a clear-cut exploitable vulnerability.

This commit fixes a timing issue in the Trezor hardware wallet's communication with the Tropic secure chip. Previously, the code simply waited a fixed 100 milliseconds and hoped the chip was ready. Now it actively polls the chip for up to 1 second, waiting until it responds as ready before starting a secure session. This reduces the chance that the chip is still busy when sensitive operations begin, which could otherwise cause failures or potentially unpredictable behavior.

This commit fixes a bug in the factory testing (prodtest) code for the Tropic secure chip on Trezor hardware wallets. A previous change accidentally made the Tropic chip appear uninitialized during secure session setup, which broke production tests. The fix restores correct tracking of whether the chip has been initialized, so the production line can reliably set up secure sessions.

This commit is a routine cleanup of translation strings in the Trezor firmware. It changes how some text labels are stored so that different device screen layouts (Bolt, Caesar, Delizia, Eckhart) can have their own versions of the same string, often leaving unused layouts with an empty string. There is no indication this fixes or introduces a security vulnerability.

This commit replaces two precompiled binary files used for the T3W1 hardware model's secure monitor in development builds. The actual code changes cannot be seen because the files are binary blobs. There is no description of any security fix or vulnerability, and no independent references were provided.

This commit adds a compile-time switch that lets developers turn off the battery-charging temperature limiter in Trezor's STM32U5 power manager. By default the thermal control stays enabled, so normal builds are unchanged. The change itself is a feature flag, not a fix for an active bug or vulnerability, and there is no claim that it addresses a security issue.

This commit swaps in a newer QA (quality assurance) bootloader binary for the T3W1 hardware model and updates the matching hash table used by the firmware to recognize it. The change is labeled as a routine chore with no changelog entry. There is no information in the commit or supplied references indicating this fixes or introduces a security problem.

This commit simply adds one new firmware version number (2.9.3) for one device model (T3W1) to a release metadata file. It does not change any code, fix any bug, or alter device behavior. There is no security relevance visible in the change itself.

This commit simply updates a timestamp and a matching version number used for Ethereum token/chain definitions. It is a routine metadata refresh with no code logic changes and no security relevance visible in the diff or commit message.

This commit only updates translated user-interface text strings for Bluetooth-related screens in several language files. It adds labels like 'Apps connected', 'Host info', 'MAC Address', and 'Waiting for host' in Czech, German, Spanish, French, Italian, and Portuguese, and refreshes the translation signature metadata. There is no executable code change, no security fix, and no vulnerability introduced.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. No actual firmware code, logic, or behavior was changed. It is a routine maintenance update to keep automated UI tests aligned with the current firmware output.

This is a routine user-interface styling update for the Trezor hardware wallet's newer 'Eckhart' screen layout. It changes how long text (such as cryptocurrency addresses) is broken into chunks and how pagination hints are shown. There is no indication of any security bug or vulnerability being fixed.

This commit adds an automatic page counter hint to a text screen UI component in the Trezor firmware. It is a user-interface feature change, not a security fix or vulnerability. There is no indication it addresses any security issue.

This commit is a purely cosmetic UI adjustment for the Trezor hardware wallet's 'Eckhart' layout. It increases the spacing between descriptive labels and their content on the receive-crypto screen, replacing hard-coded padding numbers with shared theme constants. There is no security relevance.

This commit removes two unused Rust import statements (`Insets` and `fonts`) and one unused import group (`text::TextStyle`) from UI source files. It is a routine cleanup triggered by the Clippy linter to eliminate compiler warnings. There is no functional code change and no security relevance.

This commit is a routine user-interface layout tweak for the Trezor hardware wallet's Eckhart design. It changes how text is positioned on progress screens (for example, 'Signing transaction...' and 'Please wait') and moves some shared layout constants into a common theme file. There is no security-relevant change here.

This commit removes the on-screen percentage number from loading/progress indicators in the Trezor hardware wallet's user interface. It is a cosmetic UI change only and does not alter security logic, cryptography, or how data is handled.

This commit only updates expected test result hashes (called 'fixtures') in a single test data file. No actual product code was changed, so it cannot introduce or fix a security vulnerability on its own. The hash changes likely reflect an earlier code or test update that altered screen output for the T3W1 device.

This commit only changes user-facing text strings. It adds an ellipsis (three dots) to progress messages like "Please wait" and "Processing" for the new "Eckhart" device layout, while keeping the old wording for older layouts. It also updates the translation files and their cryptographic signature metadata. There is no code behavior change and no security relevance.

This commit only rewords user-facing text in the Trezor firmware. It replaces the technical word 'host' with friendlier terms like 'app', 'connected device', or 'connection' across on-screen messages, translations, and test snapshots. There is no change to security logic, permissions, or behavior.

This commit removes Japan from a device menu screen that displays regulatory certification information. It is a routine product compliance change, not a security fix. There are no code changes that affect cryptography, authentication, or how the device protects funds or data.

This is a trivial code cleanup: a single unused import was removed from a Rust source file. It has no functional or security effect on the Trezor firmware.

This commit adds and updates automated user-interface tests for the PIN and wipe-code menus on the Trezor Safe 7 (Eckhart) hardware wallet. It also renames some Spanish translation strings for consistency. There is no change to the firmware's security logic, cryptography, or device behavior—only test code and translations are modified.

This commit fixes a bug where wiping a Trezor wallet did not reset all device settings. Previously, settings like haptic feedback, RGB LED, Bluetooth, and experimental features could remain enabled or disabled based on the old wallet's preferences instead of being reloaded from storage after a wipe. The fix makes sure these settings are reloaded when the wallet is reset, so the device behaves consistently with a fresh state.