https://devzone.nordicsemi.com/f/nordic-q-a/58644/dfu-recover-from-dfutarg-bootloader-to-applicationI run into this situation on Android nRF Connect [latest version], where the device can lose a connection when attempting a DFU. In this situation, the advertising name is DfuTarg and the user has no idea the name and even the bluetooth address changesen-USTelligent Community 13Wed, 04 Mar 2020 14:34:09 GMThttps://devzone.nordicsemi.com/thread/238074?ContentTypeID=1Wed, 04 Mar 2020 14:34:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3f509086-a3e9-454f-a01d-aaa0e9e745b1Einar Thorsrud<p>Hi,</p> [quote user=""]How do you advise to recover from/handle this situation?[/quote] <p>The bootloader has an inactivity timeout that will reset if the device after&nbsp;a specified number of inactive miliseconds, configured by setting NRF_BL_DFU_INACTIVITY_TIMEOUT_MS in the bootloaders sdk_config.h. If the application is still present (either because the timeout happened early, or because dual bank DFU is used), the application will be started in this case. If not, the device will enter DFU mode again.</p> <p>You could also set the advertising name of the bootloader to be something that reflects your product (&quot;Productname_DFU&quot; or similar) so that it would make more sense to the user if this happens.</p><div style="clear:both;"></div>