Confirmed. The firmware update can no longer be started from EOS Utility (tested with 2.14.1, but not expecting any surprises with newer versions). I can create a tool that would allow downgrading, but this would require effectively porting ML to 1.3.6 (i.e. time-consuming, but doable, and not necessarily by me).
However, I'm willing to bet OP's issue is *not* caused by the boot flag, which is currently enabled on firmware 1.3.6 on his camera. As long as you use a clean card (without ML), even if the boot flag is enabled on the camera, you will be running standard firmware. This should *not* cause battery drain. Refer to
this flowchart for the low-level details.
Possible exceptions:
- hardware issue (can be diagnosed with an external power source, but one has to cut the cable to connect an ammeter)
- incomplete shutdown from last ML session (if the camera starts and shuts down properly, a few times, with the usual LED activity, this can be ruled out)
- some incompatibilities with Eye-Fi cards (unlikely here)
I'm not aware of any other ways to lock up a camera without ML during normal use (yes, with boot flag enabled in the camera; card contents are not important, as long as the card was not prepared for ML).
I wouldn't rule out an incorrect report, so... I'd like to see some kind of video proof that battery drain actually happens.
