0

I used a link on

https://www.magiclantern.fm/forum/index.php?topic=23296.msg214271#msg214271

which gave me the file

BOOT_M50.FIR

I put that on a clean memory card as the only file and tried to update my Canon EOS M50 with that firmware.

I got a "rescue screen", but I am not sure what it means. Am I without luck because I have previously upgraded the Canon supported firmware to 1.0.3? If so, is there a way to go back? Maybe factory reset the camera?

Why does this screen read DONE? When I start the camera again, everything looks like before.

magic lantern rescue screen

1
  • Did you check the steps in the Magic Lantern usage FAQ? If so, which steps did you try and what was the result? – Saaru Lindestøkke Jul 21 '20 at 18:49
8

What you downloaded and put on your camera was simply a piece of firmware that allows you to change the boot flag of the camera. IT IS NOT A MAGIC LANTERN BUILD; it is a developers' tool that allows a coder to change the boot flag so their camera can load their code for testing. This is very clear when a1ex wrote just above the file link:

Please find the FIR file for enabling the boot flag on the EOS/PowerShot M50.

Magic Lantern uses a boot flag to tell the camera whether or not to load the autoexec.bin from the Magic Lantern build after loading the regular firmware. If the autoexec.bin doesn't exist, nothing happens.

There is no official ML build for the M50, yet.

Just grabbing whatever files you can find on the MagicLantern site's discussion board threads and loading them is A Very Bad Idea if you're not a firmware coder with the appropriate knowledge and tools to unbrick your camera. If you cannot actually follow the developer discussion from where you grabbed the file, do not load it, it is not for you. It is for the developers.

Stick to whatever's posted in the main builds, and if there isn't anything for your specific camera body, then wait—or contribute—until there is. Keep in mind, this will be a far more difficult port than with the dSLRs, because the M50's code is based in part on the Powershot code vs. the dSLR code the ML developers are familiar with; whole sections of code they're used to being able to rely on aren't there. Again, a1ex observes, further down thread:

It has some bits from PowerShot firmware, which makes it a bit different from all other EOS models. I mean, porting ML is no longer going to be "just" pattern matching; there will be parts of the code requiring wrappers or other "creative" solutions, not required on other models. That's where the difficulty comes from.

Trivial example: I could not find one of the stubs (GUI_Control), so I wrote a function that did the same thing, from scratch. I believe it's present on all regular EOS models (80D, 5D4, 200D, 77D, 7D2 and so on). ...

See also: Is there a way to get Magic Lantern on my newer model Canon?

3
  • Did I get you right in that magic lantern is a boot file you will always keep on your SD-card? – Anders Lindén Jul 22 '20 at 12:16
  • @AndersLindén, errr.. no. MagicLantern is several different files, including an autoexec.bat. There's an entire distribution of files/folders, etc. that make up Magic Lantern. Highly recommend that you read their installation guide before doing anything. DO NOT try to load a build meant for a different model: that's an easy way to brick your camera. – inkista Jul 23 '20 at 1:01
  • It's not just A Very Bad Idea to grab whatever files you can find on a Magic Lantern discussion board about a particular camera and try to load them, it's more of !!!A.VERY.BAD.IDEA!!! – Michael C Jul 24 '20 at 0:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.