https://devzone.nordicsemi.com/f/nordic-q-a/3262/bootloader-fails-with-hex-from-android-but-ok-with-iosHi - I&#39;m using the 51422 dfu bootloader from the nrf 6.0.0 SDK and it works fine with the iOS apps, I can send both .bin and .hex files to the device and it works fine. However, with the same exact hex file when loaded from the NRF Toolkit on Androiden-USTelligent Community 13Wed, 10 Sep 2014 19:11:59 GMThttps://devzone.nordicsemi.com/thread/11928?ContentTypeID=1Wed, 10 Sep 2014 19:11:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a7365a38-6b56-4504-9252-0544fe9566e8zer0page<p>This solves the issue for me as well. It seems that the new iOS version(as of Sept 2014) has the same issue and I had to switch MBR to 0 on Android to work.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/11927?ContentTypeID=1Fri, 25 Jul 2014 17:53:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b4ffe52a-6b6d-4be2-ad88-6acd95d516cfJason De Lorme<p>After some more searching around, I found this post: <a href="https://devzone.nordicsemi.com/question/13486/dfu-udpate-corrupt-from-address-0x20000/">devzone.nordicsemi.com/.../</a></p> <p>I am compiling my hex with gcc and Nikita discovered that you need to set MBR size in Master Control Panel to 0.</p> <p>I am using the NRF Toolbox app, but I found the MBR setting which on Android defaults to 4096. When I set it to 0, the app loads from Android! It doesn&#39;t seem that the iOS app has this setting and defaults to 0, which works. This must be the difference.</p><div style="clear:both;"></div>