Originally Posted by Marcus_Ti

It is the nature of how firmware updates have-to-work. The problem is the wireless unit itself and its updates IME.

What happens? I'm guessing...

1) You connect wirelessly to Di2
2) You D/L an update.
3) The Di2 system applies the update...but to finish the update, like in Windows it must reboot the updated component
4) The wireless app (and the D-Fly) looses connection during the reboot, because well--the connection hard-hangs up.

Which means that E-Tube and D-Fly cannot handshake-check that the update worked...so they thought vomit at one another. E-tube errors out, and Di2 soft-bricks to protect itself thinking something went wrong.