Are you using the secure OTA process that is defined in Software Over-The-Air Secure Firmware Update and is supported but the BCM20737 only as it requires the RSA library this part enables (not available on 20732/20736) ?
This version has been tested internally and works well with the Windows peer application that is provided within the SDK.
Are you using the non-secure OTA and Android peer apps posted as a part of these two threads:
http://community.broadcom.com/message/9499 (2 of 2, Android application is attached to this one)
If the former, check that his board has enough memory and that you are downloading the correct image (both common problems). For example if you download a .txt file, the download will work fine but it will not boot.
If the latter, we will have to check internally to see if this is supported.
I'm using the non-secure OTA.
The Android application if out of these threads, but I had to change sending the patch-size with the correct command.
But I tried it also with the windows application provided with the sample (in peerapps).
Both apps show the same result: uploading ok, but not booting.
I use the same application I flashed to the module, but only add one trace at the APPLICATION_INIT.
Then I upload the new ....ota.bin.
I found the problem:
I add a trace to the APPLICATION_INIT. If I set the trace in the create(), it works with the windows version of the tool, so everything is OK.
Excellent. Thanks for updating the thread with the resolution.