https://devzone.nordicsemi.com/f/nordic-q-a/8439/bootloader-dfu-update-invalidates-appI am testing with SDK6.1 S110 7.1. I&#39;ve noticed that when I try and update the Bootloader image using the Android MCP app, everything updates fine. I have logic in place that has the Bootloader image start the App. HOWEVER if after updating the Bootloaderen-USTelligent Community 13Thu, 30 Jul 2015 18:34:48 GMThttps://devzone.nordicsemi.com/thread/30725?ContentTypeID=1Thu, 30 Jul 2015 18:34:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:625c9617-fde7-4981-a18d-1f9412e28864Locky<p>Thank you Hung. We are looking to migrate to the latest SDK next month.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/30724?ContentTypeID=1Thu, 30 Jul 2015 12:24:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8ee09a8a-d7aa-4ede-95b8-5f57d86b5d07Hung Bui<p>@Locky: What you experience is similar to this: <a href="https://devzone.nordicsemi.com/question/20356/bootloader-only-update-with-dfu/">devzone.nordicsemi.com/.../</a></p> <p>It&#39;s a bug on our DFU in SDK v6.1 and v7.0. The fix has been implemented in SDK v7.1 In the case above, you can find the explanation of the bug by Adrian at the bottom.</p> <p>If you want to implement the fix please follow what we did in bootloader_dfu_update_process in update_status.status_code == DFU_UPDATE_SD_SWAPPED case.</p> <p>I would suggest you to use the lastest SDK which is v9.0. The chip you going to use in production will be rev 3 chip.</p><div style="clear:both;"></div>