Frozen Camera need help by 9/19/13

Started by Cparelli, September 17, 2013, 06:30:44 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Cparelli

Hi I hope someone can out there can help me I am going trip Friday 9/20/13 and need this problem fixed by then.

Camera* 5D MK2

I had Magic Lantern Running and Installed on the camera Just Fine.

The CF Card I had it on is now gone and I was trying to reboot my camera and did not un-install it properly.

I purchased a new 8gb CF sans disk 30mbs card and transfered the ML Boot Files to it but it still did not boot up.

I was wondering if there is a way to get it to boot.

Should I have the card formatted by a different 5D MK2 and then but the ML Files on it?

If you have advice to get my camera up and running again I would be very grateful.

I live in Minot ND and am traveling to Alaska soon so if you are in those arias and would like to meet up to help me that would be nice too.




Walter Schulz

In short:
You need 4 things to run ML for fun and profit
1. Bootflag enabled on cam (current status: ok)
2. Bootable card (current status: not ok)
3. ML files and directory structure copied to card (current status: ...)
4. RTM


RenatoPhoto

Special note on to use EOScard Utility:

This is the way to set the flag on the card:

When you use EOScard make sure that:
1. You have the necesary files in the SD card: *.fir file (only if you need to set the bootflag on that camera; this process to be done only once), autoexec.bin file, plus the ML directory.
2. The Utility recognizes the card by identifiying it in the box next to Refresh.
3. You select the EOS_DEVELOP  check box
4. You select the BOOTDISK check box
5. Under Content, make sure EOScard recognizes: DCIM folder, autoexec.bin file, ML folder, and if required (to enable the boot flag on camera) the fir file.  When EOScard recognizes all of those files it should give you a check mark or something like that.
6. Press the Save button.
7. Look on the bottom of EOScard and should give you a confirmation that the card was written, ie. write successful.

I recently read about another situations with the newer EOScard utility in which the automatic function brought the files to the SD via internet connection.  I am not familiar with this function but Pelican seems to more about it since he created EOScard utility.  Anyway the issue was that EOScard utility had downloaded some files plus there were already some files in the card, the user noticed that in the fir file area it showed like 2 files so the user had to select the correct fir file for the EOScard utility to properly prepare the card! One of the files was for Mac and the other was for windows.

Also on most cameras, except 5D3, if you enable the camera bootflag via firmware update, and then do it again you will be disabling the bootflag.  It is and ON-OFF process, so if you have a camera working and set the camera flag using the *.fir file you will be disabling the flag in the camera and ML wont start.

So remember to make a card bootable use EOScard utility, and to set the camera flag use *.fir file and do the firmware update.
http://www.pululahuahostal.com  |  EF 300 f/4, EF 100-400 L, EF 180 L, EF-S 10-22, Samyang 14mm, Sigma 28mm EX DG, Sigma 8mm 1:3.5 EX DG, EF 50mm 1:1.8 II, EF 1.4X II, Kenko C-AF 2X