Trezor Model T suddenly load in bootloader mode

Hi there!

I’ve using 2 Trezor Model T, one of them for few days in a week, another one is a backup device. Yesterday when i’ve connected my backup device, it has showed on screen message “Get started with Trezor Suite”
trezorctl showed me this figure means the device being in bootloader_mode. All of my tries to flash firmware (no matter what version) fails for reason “Internal error: messages.c:735”.
What should i do next? I already tried to change usb-cables, ports and even computers.

Features (36 bytes) {
bootloader_mode: True,
firmware_present: False,
internal_model: ‘T2T1’,
language_version_matches: True,
major_version: 2,
minor_version: 1,
model: ‘T’,
patch_version: 4,
vendor: ‘``trezor.io``’,
}

Best available version: 2.12.4
Downloading from ``trezor-t2t1-2.12.4.bin
T2T1 firmware image.
Vendor header from SatoshiLabs, version 0.0
Firmware version 2.12.4 build 0
Firmware fingerprint: 0c59a2d10c2eb4245b124d41b67f1506f888494598bee58bd886de46c5293418
Firmware is appropriate for your device.
Uploading [------------------------------------] 0%
Update failed: USB read failed: LIBUSB_ERROR_PIPE [-9]

messages.c:735 is here: it’s trying to erase the flash storage, and failing.

Unfortunately, a failure of this kind is pretty much game-over. You will have to get a new device.

It’s devastating. Brand new device and it’s just gone after 2, maybe 3 times of usage.

Could it be possible to reflash via external STM32 flasher?..

it’s unfortunate, and if you were in the warranty window, you’d be eligible for a replacement – but guessing by bootloader 2.1.4, that’s no longer the case

Using an external programmer won’t help, the mcu has its own internal flash erase / write circuitry that can’t be routed around. This error indicates that either a particular sector is damaged (which unfortunately kills the device as a whole, the firmware is sized to the chip exactly), or the entire programming circuitry is down (e.g. a burned out charge pump).