Usually, I programmed the Thingy 91 with the nRF connect Programmer (right now version v.3.3.3). As my Thingy did not work with the asset tracker software and only with the original firmware a friend sent me his app_signed.hex file from the asset tracker. After programming it with his file it did also not work.
I own a debug probe (JLink mini from Segger) and tried to flash the asset tracker SW with the official manual using SEGGER (version 4.42a) to build and download it to the Thingy. It all succeeded but my Thingy didn't do anything after it.
The LTE Monitor didn't show any activity and the AT commands always resulted in Timeouts.
Therefore I tried to reset the Thingy by flashing it with the original firmware. It always stopped at 5% with an "erasing image failed" "Please make sure that the device is in MCUboot mode and try again.
As I used the Thingy before I know how to enter the MCUboot mode.
In another step I tried a modem and firmware update as I read in the forum it can resolve these issues. The update was successful but the Thingy still won't work and I can't program anything else.
I as well tried to program it using mcumgr and again using SEGGER with the debug probe as well as with the debug probe using nRF Connect Programmer. All different ways fail.
To make sure it's not a nRF software issue I tried it as well using a different computer.
It kind of seems that the Thingy can't enter the MCUboot mode correctly anymore. But even with a debug probe where the MCUboot mode is not needed it does not work which makes the whole thing strange again.
Can anyone help me with this issue?
