Hello Teltonika Community,
We would like to report a critical issue we are experiencing with the new Teltonika.Configurator_1.8.10_B.4.00_R.7 application.
While updating firmware using this Configurator version, one of our GPS devices entered boot mode after the firmware update failed. To rule out a device-specific problem, we tested multiple GPS devices using the same Configurator 1.8.10, and the same issue occurred on all of them.
In addition, during or immediately after the firmware update process, the PC running the Configurator crashes with a Blue Screen of Death (BSOD) showing the error code “WDF_VIOLATION.” This issue occurred on two different PCs, both using Configurator 1.8.10, which strongly suggests the problem is related to this software version.
For comparison, we reverted to the older Teltonika.Configurator_1.7.72_B.3.29_R.11 and performed the same firmware update (FMB.Ver.04.00.00.Rev.13.e.xim). With the older Configurator:
-
Firmware updates completed successfully
-
Devices did not enter boot mode
-
No BSOD errors occurred
Based on these results, we strongly believe there is a bug in Teltonika.Configurator_1.8.10_B.4.00_R.7 causing these issues.
Currently, we have an FMC125 device stuck in a boot loop after failing during a firmware update using Configurator 1.8.10. The device is installed in a vehicle, which is now operating without a GPS unit, creating an urgent operational problem for us.
We have already contacted Teltonika Support via the “Contact Us” page on the Teltonika website and are awaiting a response. In parallel, we wanted to share this issue here in case other users are experiencing the same problem or have insights.
We would appreciate any feedback regarding:
-
Known issues with Configurator 1.8.10
-
Recommended recovery or reflashing procedures for devices stuck in boot mode
-
Any official workarounds or fixes
Thank you in advance for your support and insights.