T2i Magic Lantern Firmware won't stay installed?!?!?!?

Fritz bakon

Active member
I tried dowloading the magic lantern firmware today and I am having the worst of luck. I do all the steps correctly and when I upgrade the new firmware from 1.0.9 and turn my camera back on the new firmware I just installed is gone! Does anyone have a solution to this problem?

Thanks
 
Fritz, I don't fully understand the question you're asking, so I'm sorry if my answer is overly simple or obvious.

The actual Magic Lantern does not stay permanantly on your camera. The only thing that gets permanantly installed on your camera is some programming that tells the camera to look for the Magic Lantern of the SD card (Is it called a bootflag? I understand the theory just don't know all the technical terms!).

So when you first set your camera up to use Magic Lantern, you will update to the newest Canon firmware (if necessary) then update it with the ML installer version that has the bootflag (if that's the right name for it?). After doing this, turning your camera on will not give any indication that anything is different. Your camera will still operate exactly the same as with the Canon firmware and none of the ML features will be available - until you put in a bootable SD card containing the Magic Lantern file (autoexec.bin).

From your description it sounds like you already have the latest firmware, and when you try to update it with the ML installer, then turn your camera back on, nothing has changed. This is normal, and is only half of the process of running ML. To actually use ML, you now need to make your SD card bootable (using the EOScard.exe application) and then put the ML files on your card (autoexec.bin & the Cropmarks folder). After you do that, and turn your camera on, you will be able to use ML. However, if you format the card or erase the autoexec.bin file from the card, or use a different SD card, ML will stop working. If you delete the autoexec.bin file and leave the card as bootable, you will stop your camera from working at all - this is because the Bootflag tells the camera to look for ML as long as the card lets it - and if the card lets the camera look for something that isn't there it gets stuck in an endless loop and can damage your camera (again, this is my vague understanding of the theory and I don't know the technical terms).

Again I apologise if I've misunderstook your question.
 
Fritz, I don't fully understand the question you're asking, so I'm sorry if my answer is overly simple or obvious.

The actual Magic Lantern does not stay permanantly on your camera. The only thing that gets permanantly installed on your camera is some programming that tells the camera to look for the Magic Lantern of the SD card (Is it called a bootflag? I understand the theory just don't know all the technical terms!).

So when you first set your camera up to use Magic Lantern, you will update to the newest Canon firmware (if necessary) then update it with the ML installer version that has the bootflag (if that's the right name for it?). After doing this, turning your camera on will not give any indication that anything is different. Your camera will still operate exactly the same as with the Canon firmware and none of the ML features will be available - until you put in a bootable SD card containing the Magic Lantern file (autoexec.bin).

From your description it sounds like you already have the latest firmware, and when you try to update it with the ML installer, then turn your camera back on, nothing has changed. This is normal, and is only half of the process of running ML. To actually use ML, you now need to make your SD card bootable (using the EOScard.exe application) and then put the ML files on your card (autoexec.bin & the Cropmarks folder). After you do that, and turn your camera on, you will be able to use ML. However, if you format the card or erase the autoexec.bin file from the card, or use a different SD card, ML will stop working. If you delete the autoexec.bin file and leave the card as bootable, you will stop your camera from working at all - this is because the Bootflag tells the camera to look for ML as long as the card lets it - and if the card lets the camera look for something that isn't there it gets stuck in an endless loop and can damage your camera (again, this is my vague understanding of the theory and I don't know the technical terms).

Again I apologise if I've misunderstook your question.

Well I did all of that and it installed the ML but when I turned it off and turned it on back and all of the features were gone.
 
So you get Magic Lantern up and running, and can use all of its features, but when you swtich the camera off and then back on again it is no longer there?
 
This might be a stupid question but if the magic lantern is on the card what are you recording on? Is it recorded to the same card? If so do you just have to have magic lantern on all the cards you use? I looked at the FAQ and didn't spot anything answering that.
 
This might be a stupid question but if the magic lantern is on the card what are you recording on? Is it recorded to the same card? If so do you just have to have magic lantern on all the cards you use? I looked at the FAQ and didn't spot anything answering that.

Yes. Yes. and Yes.
 
Back
Top