Messages

Good morning a1ex, thanks for the reply!

I think you are right, it's likely a hardware issue.  I gave the camera a brief round of fixes this morning with no success. 

I'll give the autoexec a go, and then start planning for hardware repairs.

The error flag on the LCD screen I'm pretty sure just showed up randomly, and no batteries were taken out at the time.  I just powered it down immediately for fear there was some power overload.  But now I think it was just a last electronic gasp before the hardware went South.

My research indicates it's probably the DC Power PCB board (hopefully)  Not an expensive part, but if  not, then the it's the Main Logic Board. 

Well thank you again A1ex (and the team) for the reply and the great software!  Keep up the great work!  I'll update the thread once I know more.

Best ~ MJ

[How I got here:]

Ladies and Gentlemen of the Magic Lantern forums, today, my Canon 5DM3 appears to be bricked.

I have a feeling that this is hardware issue, but I didn't want to rule out anything with software before shipping this off to Canon for costly repairs, so I'll share the tale and perhaps someone out there has had a similar issue and can shed some light onto what went wrong and how to fix it.

How I got here:

Before the camera went completely dark, I was doing some tests to resolve an issue where the ML audio meters were showing some kind of weird audio distortion that was appearing when either the HDMI cable was connected from the Canon 5MD3 to the external EVF (IDX powered via regulated dummy battery), or when my the mini stereo cable was connected to the Canon 5DM3 via a Tascam 70DR, the on board digital recorder (IDX powered via regulated D-Tap Multi Tap with USB port).  The ML Audio meters were handy for seeing this problem. See below:




best image hosting free


I had previously done an audio test on this camera after uninstalling ML and the audio issue was still present, so I was confident ML was not the problem.

All the devices on my rig are powered via regulated D-Tap Batteries via the appropriate cables and never gave me any trouble.  Everything seems to be getting it's appropriate voltage (Zacuto Gratical EVF, Tascam 70DR, Canon 5DM3).

However when each device was switched to it's own independent power source like a Canon Battery or AC power via a plug and usb cable, the audio issue would stop. See below:





I ruled out ML being part of the problem after these tests and that it had something to do with the Tascam 70DR and it's power source.

Well, during my trouble shooting tests, I would forget myself and just quickly turn the Canon 5DM3 on and off at my leisure, changing cables, popping off shots to review later, though I didn't think this would cause any problem.

Right before it bricked:

At one point, after restarting the Canon 5DM3, I could see on the display an error message from ML, something about it not being shut off cleanly and the it would skip loading certain files.  (I should have paid closer attention, I can't recall what it said exactly.)

Things seemed to be running fine during my tests, but then I saw an ERROR flag on the LCD display on the top of the 5DM3 camera body. 

I panicked and immediately cut the camera off.  The last time I saw something like this, I had connected an unregulated dummy tap to an unregulated D-Tap and was worried that I had fried the camera, but I didn't.  It was long ago and I'd never made that error again, so this was a reflex action on my part.  The camera in fact had the correct dummy block in it, connected to the regulated side of my IDX V mount plate.

After that, I gave it a moment, flicked the power switch on the 5DM3 back to the "ON" position, and now I have no activity on the 5DM3, zero.

No activity on the display.

No activity on the Red flashing work light.

No activity on the LCD display. 

No mechanical noises at all.

The fixes I've tried:

So far I've tried the standard recommended fixes from the forums, such as removing the lens, battery, card, and then replace.

I've tried using freshly formatted cards, SD & CF.

I've tried all three of the autoexec.bin testers, Display, LED*, and ROM Dump.
*(Desperate. Though not meant for 5DM3, tried it anyway.)

I've tried formatted cards with the latest nightly build.

I've tried formatted cards processed through MacBoot.

Unfortunately, no success. 

After inserting the blank cards and switching on and off many times, I've re-checked the cards on my MacBook and I can see that there are no file directories available, that Canon's cameras usually write to blank cards when inserted for the first time.

So as far as I can tell there is no electrical activity anywhere on this camera.

At this point, I think that this is just a hardware issue, but if anyone out there has had a similar experience, please share your thoughts or direction.

I'd hate to think it was something that I created buy abusing the on off switch while using ML, but I don't think so.  ML is a pretty tough bit of code in my opinion and I don't think it's the root of the problem.

But I could be wrong, which is why I'm here.

The ML Firmware I was using is from the 08/18/17 nightly build, 2:13am.

Canon 5DM3 firmware 1.2.3

Thanks folks! Please share your thoughts!

Best to you all. 

MJ Walls

Hey there, for anyone who is interested I solved this install problem on the 550D.

I need to open my eyes, slow down a bit...and read.

So I couldn't install ML on my 550D after a great run of using it.

Then one day after removing it, and updating to a nightly build, it wouldn't work. 

Couldn't figure it out but it the 550D update would keep saying that it needed firmware to update.

I figured out today that the nightly builds don't include the firmware. the firmware is only available in the old builds v2.3  I've avoided this for a while now and today decided to take a crack at it.

I slowed down, took a look at the nightly builds page and saw this:

Installation

You cannot use this package for first install. Download the old v2.3, install it, then replace the files with the ones from the nightly build.

Well, chocolate and peanut butter.  I downloaded v2.3, then updated the folders on this from the nightly builds and voila!  It works.

So if I've waisted anyones time on this one, or there has been a groan or rolling of eyes upon reading my earlier post, and was punished by a non reply because of it.  My bad.

Thanks to everyone out there for sharing their thoughts. 

Best,

MJ

[Regarding the T2i]

Hi Steve,

I was having a similar problem on both of my cameras, 5D and T2i.  The newest file structure for these builds don't show a fir. file that I can find, but for some reason, I couldn't seem to get ML to install on my T2i, and had a similar experience with the 5D where I couldn't get ML off.

I sorted out the 5D, I simply took out the ML SD card (512 MB PNY SD card)  and the camera restored itself to the normal firmware 1.2.3.  I formatted the small SD Card with Mac Disk Utility to MS-DOS (FAT) and then added the latest build of ML to the 512 SD card, and then updated the firmware, where as before it gave me the message "Memory Card content firmware is required to update".

Regarding the T2i, I followed the thread and located a Firmware file 1.0.9 for the 550D, placed it in with the newest build, and it allowed me to "attempt" to update, but said it was missing fonts.  So I turned off the camera, restarted and saw that ML was still not installed. 

So knowing that the Firmware file would allow the update to work, I went back and used an older build posted and installed the good old fashioned way and I was able to install ML on the 550D/Rebel T2i.

For some reason or another, I suspect the camera is not reading the autoexec.bin file.  Even stranger, I had this camera working with ML before with a previous "Nightly Build" that only contains the single .bin file and the ML folder and it was working perfectly.

So I don't know what gives.  The boot flags must be working if I can install using the much older builds, but so far, all things point to the camera being the culprit. 

If I learn anything new, I'll be sure to post.

Best,

MJ

I'm glad to hear that you fixed the problem. 

I apologize in advance for not posting this sooner.  Truth be told the ML install scare kept me from installing the software even after the camera was fixed.

So originally, I had copied the ML data onto an SD card and only after I upgraded the camera firmware did I move on with the install.

(Read earlier parts of the thread if you wish to re-live the ordeal.)

Anyway, after the card was inserted I went ahead and did the firmware update with the ML SD card and the camera died on me.  It had some reactions from time to time, auto focus, shutter action with no picture being taken, a locked red work light that wouldn't stop unless I removed the battery.

Since this all happened right after installing MD, I felt that ML had to play a role in it, but I was not certain.  I tried all the tricks and suggestions to fix the issue, but nothing worked.

After much help and discussions from the ML Leaders of the forum, they were very confident it was the camera and not the software, and they were right.

I ended up sending it back to Canon, out of warranty, and chose not to include the details of ML in the repair request.

The camera had lite use and had not been abused so it didn't seem right that this problem should be occurring regardless of ML.

As it turns out the logic board in the Camera was failing, and had nothing to do with ML.

Canon replaced it, no questions asked, no charge, and I got the camera back in perfect working order.  It makes me wonder if this is a common issue with the Rebel T2i.

Trepidatious, I stayed away from ML for some time.  But a buddy of mine with an older and exact same camera, has been sporting ML for sometime with no errors or issues  whatsoever.  So I worked up the nerve and gave it another shot.

I couldn't be happier with the result.  I followed the instructions and installed ML and it works wonderfully.  Actually now with the ML software installed I want to use my camera more for video work, particularly the focus tools.  It makes it a more enjoyable experience when shooting video with this little DSLR.

So there you have it.  If all else fails and all the trick and suggestions on this forum do not work for a possibly bricked camera, it may just be the camera. 

Good luck to anyone out there suffering from the same techno-mality.  I hope this post offers some comfort in knowing that what may be a brick right now may just need a tune up.

Big thanks to the entire Magic Lantern Team!

Best regards,

MJ

Michael J. Walls
DP/Cameraman
www.MikeJWalls.com

So:

1) You have upgraded to 1.0.9 and you have seen the confirmation that update completed successfully.

2) You removed the card, copied ML files, then placed it back in the camera and started it. Camera did not start.

Is this correct?

Yes to question 1. 

Yes to question 2 (I think).  My memory is kind of foggy at this point so I can't be 100% sure if reached the second firmware update window when attempting to install the ML software.

But after everything I've tried, I'll agree with you at this point that this issue is probably more attributed to the original firmware update to 1.0.9. 

I'm going to try another pass at the diagnostics, the suggestion by iheartbmx, and then look toward sending this in for service.

I do have faith in the ML software though and look forward to using it at some point.

Thanks to everyone for your all of your help.  I'll keep checking in if there are any other ideas or fixes offered, or if anything changes on my end.

All the best,

MJ

Did you see the screen saying "Firmware Update Program - Loading"? (you didn't answer this).

When you have tried the blink test, did you make the card bootable first? (e.g. with eoscard)

Hi A1ex,

Thanks for your patience with me on this.

No, I did not see the screen saying "Firmware Update Program - Loading" when using the ML SD install card.  I watched the vimeo video link you sent me and I see what you referring too.  I don't remember getting that far.  I'm pretty sure the camera locked up after inserting the SD card with ML incorrect folder structure in it and then turning the camera on.  Then it went dark.

Yes, I did make the SD card "bootable" using EOSCard on a windows machine for the blink test.  I then placed the autoexec.bin file for the blink test in the bootable sd card, then in my Rebel T2i.  I replaced the battery, powered up and the same results, one blink, nothing more.

I just watched a video on how to use EOSCard.  I will make another attempt at a bootable SD card via EOS card with the blink test file to be sure I've done it correctly.

Thanks for the link on Bug Reports.  I'll check it out.

@EMJAYWLZ What firmware update did you use (the one that "killed" the camera)? Can you give us the link?
Was it called e8kr7109.fir or 550D-109.fir ?

Greetings nanomad,

"e8kr7109.fir"  is the firmware update that I downloaded, and installed on my Canon Rebelt T2i.  I went through the menu system and visually confirmed the update to 1.0.9.

Below is link for the firmware update that I downloaded from the Canon website.

http://web.canon.jp/imaging/eosd/firm-e/eosdigital7/firmware.html

I was having some of the same issues you originally had (Blank screen, one light blink) I'm using a SanDisk Extreme Pro 64Gb SDXC in my 550D. I BELIEVE What ended up working in my case was low-level formatting the card, boot version 2.2, then replace the ML files on the card with with version 2.3's. I think the install info for 2.3 explained that this is not recommended? Just my experience.. running fine so far.

iheartbmx,

Much thanks. I'll look into this and report back if there are any changes.

Best,

MJ

Can you answer my questions with yes and no? I'm even more confused.

Hey a1ex,

Sorry about that.  I didn't see this reply.  I'm not a big forum user, so I don't know the ettiquete.  I guess less is more would be the best way to go.

For me, there are a few things unclear.

1) Did you run ML firmware update? Did you see the screen saying "Firmware Update Program - Loading"? Did you see ML green screen? (as in this video: http://vimeo.com/30803116 )

2) Is the bootflag enabled on the camera? (does it matter if you use a bootable card with autoexec.bin on it, or a freshly formatted card?)

3) Can you try the LED blinking test from here? http://www.magiclantern.fm/forum/index.php?topic=2296.0

Answer 1) Yes, I did, or thought I did.  After I updated the camera firmware, I  inserted the ML SD Card I created, turned the camera on and then the camera stopped working. No, I did not see the ML green screen.

Answer 2) I do not know.  I think it is.  I have never altered or knowingly altered this function on the camera.  I have tried an SD card with an an autoexec.bin on it, and a freshly formatted card.  At most, the camera writes a DCIN and MISC folders as when you use the camera normally.

Answer 3) Yes, I did try the blinking light test.  The behavior is the same.  When any card, with an autoexec.bin file or blank is inserted, followed by the battery, and then switched on, the red light blinks one time, and then that's it. A moment of autofocus, maybe a single shutter action, No visuals on the back display, maybe an error 80 code in the viewfinder, and that's it.

Again, sorry about the confusion.  You are the experts here.  I just wanted to make sure you had the whole story.

Thanks again.

MJ

Hey there A1ex,

Yes, I did run the Canon camera latest firmware update, then I followed the install pdf instructions and did the ML update. 
(My earlier posts list the specifics of what I did)

The two big errors that I made were installing just the ML folder on the root of my SD card, not the 10 items within.  I was following the enclosed PDF witch from what I read, did not specify.  This being such a sensitive install I was trying to follow to the "T".

The other error I made was, putting my camera in A-DEP mode by accident, just one notch above M as listed in the install instructions.  (It's what I get for not measuring twice and cutting once I guess.)

After running the SD card with this ML folder configuration, the camera went dark.  Since then I've not been able to get the LCD screen to activate, and I never saw the Loading ML screen with green text.  I sure wish I had watched that vimeo link before doing this.

I would imagine the bootflag is enabled on my camera, but at this point, I don't know how to enable or change it since I don't have a menu system to look at, if it can even be altered by a menu system.

I have tried inserting an bland SD card with no auto exec.bin file, one with.  I've tried a ML SD disc created with EOScard on a windows machine instead of a mac which is my usual goto, with the appropriate fild directory structure in the root directory.  No changes.

I've cycled every setting while removing the lens, the sd door, the battery, with and without an SD card inserted.

The only activity I've managed to get so far is the red work light to blink once, as if reading the card, and then nothing.  On a completely blank and formatted card, it will read, light up for a moment longer and then cut off, and it writes the DCIM MISC folder directory in the root of the SD Card.

I've managed to get the shutter to work, some autofocus function but after more than a few seconds it just putters out, like it ran out of gas or something.

When it has managed to "appear" to take a photo, meaning a few shutter actions repeat in succession, it putters out, or the shutter will stop halfway, and that's when I usually see the Error 80 code in the viewfinder.  However the red work light will hang like it's writing to the card, but it writes for an abnormal amount of time, longer than I know it should, so I just remove the battery for fear of overheating.

Still, no working LCD Screen, no viewable menu system, and no signal is coming out of the mini HDMI port on the side.

I have tried the diagnostic tests last night as well but no changes in the red work light indicator.  It just blinks once after I put the battery in and turn it on.  I get the sense that it's just not reading the software at this point, but it still capable of writing.

My one last hope it seems before sending it in is to remove the CMOS internal battery.  I had read on a forum of a non ML user where a camera just stopped working.  Someone  has suggested removing the CMOS internal battery to wipe the Cameras internal memory and that this may allow you to start fresh.  You can see the internal battery, just inside the main battery slot, looks like a watch battery, but it's not easily accessible, and I have not found an appropriate teardown for this camera.  I made an attempt but decided I would just back off before making a complete paperweight out of my canon.  I'll need more confirmation first.

That's all I can think of. 

nanomad: I'm pretty sure I've tried this all without a lense, but I'll give it another whirl.

Thanks for all of the posts.  Keep them coming.

MJ

Hey everyone,

So, I'm still locked out of my Canon Rebel T2i since attempting to install the ML software.

I've noticed that some settings allow me some function over the shutter, I've even been able to complete one shutter action, but then after that it loses steam and I get an Error 80 code.

The red work light does come on but it stays on as if it's trying to write to the SD Card but I pull the battery to keep it from over heating.

I've tried the suggestion by Pelican, but no luck  (Thanks though.)

Still no LCD activity.  I tried connecting the camera to an external monitor via Mini HDMI cable, no luck.

At this point it's looking like I may have to send it in for repair but would like to avoid that.

If anyone else has experienced the same issue or found a solution, please post.

Thanks again. 

MJ

Thank you for the suggestion.  I'll give that a try today.

Much appreciated!

MJ

[To Recap what happened:]

Hey there ML Community,

So I've tried almost every fix that's been thrown at me and tried one of my own but no success yet.  My computer is a Mac Mini running OSX Mountain Lion.  I also have a Bootcamp partition running Windows 7 on a Macbook Pro.

To Recap what happened:

I downloaded and updated the latest firmware for the Canon EOS Rebel T2i.

I originally unzipped the entire contents of the ML archive download to my 32GB SD Card, as per the installation instructions.

My mistake was not emptying the contents of the folder named "magiclantern-v2.3.550D.60D.600D.50D.500D.5D2" into the root directory, but placing the whole folder in the root directory.

I then followed the install instruction and activated my camera.  The work light flashed once and that was that.  No further functionality.  The LCD display will not work.  No shutter activity.

I noticed that my dial was set to "A-Dep", not "M" when I turned on the camera with the ML card inserted.

Current Functionality of my Canon Rebel T2i:

The LCD Display will not turn on. 
The Canon will not take photos.
The Canon is not recognized via usb.
The Red work light will blink once when a charged battery is taken out and replaced.
The Red work light will blink once and a bit longer when inserting a completely formatted and blank SD Card.  It seems to be able to write
the root directory folders DCIM and MISC.

After trying to figure it out myself I turned to the forums.

What I've tried to do so far with no success:

Reinstall the latest firmware via a freshly formatted SD card with the firmware in it and with the EOS Utility Software.
Create a MS SD Install card with the appropriate file structure in the root directory.
Created a new ML SD Card on a windows 7 computer with EOSCard.  I've tried it with the current available builds of the MS Software.
Powered off the camera, removed the lens, removed the card, removed the battery and replaced all in the same order.
Followed the step by step fixes available on the forums in case you think your camera is bricked.

That's all I can think of for now.

Since trying all of the recommended and above suggestions, I cycled through the dial, swapping the battery with each pre set and turned on the camera.

It still has not returned to normal, but I noticed that pressing the shutter button gives limited function to the auto focus and the shutter from time to time.  Sometimes the shutter manages to complete a full action, sometimes it stops halfway.  I managed to snap off one shot it seemed, but the work light just hung, so I removed the battery. 

That's all I can think of folks.  If anyone out there has any ideas or faced this problem, please share your experience.  You help is greatly appreciated.

My fingers are crossed.

Thanks again!

Best,

MJ

Hey there. 

Maybe I'm missing something. 

I don't have LCD functionality.  It's black.  Is there a way to reinstall the firmware if I can't read the screen?  I have no menu system available.  The only thing that seems to be working is the red work light in the lower right corner of the camera body that lights up when I put the battery in and turn it on. 

I inserted a card with the latest firmware but with no success.  I'll see if I can get a menu system through the mini HDMI out to a monitor.

I also downloaded and used EOSCard to reinstall ML,  My previous Mac version of the ML installation had the autoexec file installed but I went ahead and used EOSCard on a windows machine and installed the ML software with the same results.

I replace the battery and turn it on, the red light blinks once, then nothing.

I decided to roll the dice and press the shutter button and there was a little shutter activity. On other attempts to get it working, I removed the battery, replaced it, light comes on, and that's it. 

After the shutter tries to activate I do see an Error 80 in the viewfinder. 

So it has a pulse, I'm just thinking it's flaked out in the software department somehow.

I'd like to at least get it back to factory setting so I can give ML another chance.

Please keep the suggestions coming.

Thanks!

MJ

Yep.  The first thing I did and the last thing that seemed to go right.  =^)

I'll get that windows install set up and let you know how it goes.

Thanks for all the help.

I'll check in soon.

Best,

MJ

Hey there,

Thanks, I do and I will.

I'll let you know how it works out.

Thanks for the suggestions!

Best,

MJ

Greetings jgore!

Thanks for you help with this.

I followed you instructions and formatted the card totally.

I inserted the blank card into the camera, replaced the lens and battery and turned it on.  This time the red work like stayed on for a moment longer and seemed to have added the DCIM and MISC folder to the card where there was none before.

However the LCD is still dark and there is no shutter activity when I press the button.  The camera is in "M" mode when I turned it back on.

Did your camera have the same behaviors?

Any other ideas would be welcomed.

Thanks!

MJ

Hey there,

Thanks for the quick reply.  I suspected that to be one of the issues.

I removed all the other files from the folder, matched your image including the .fir files from the original download on the MLSD install card.

I've gone through the process of rebooting, removing the batt, card and lens, putting them back on and turning the camera on.

The screen is still dark.  The LED does flash one time, and then thats it. 

The dial is set to M this time as opposed to the A-DEP mode from my initial install.

Any other ideas?

Much thanks! 

~ MJ

Greetings all,

So I was excited to finally install the ML software for my canon rebel t2i.  I followed all of the instructions, updated the firmware.

When I extracted the ML software into my 32GB SD card, I included everything,

"/Volumes/EOS_DIGITAL/magiclantern-v2.3.550D.60D.600D.50D.500D.5D2"

When I turned the camera on, the screen stayed dark, and the led in the lower right corner blinked once.

After that the camera was unresponsive.  I looked it over and of course, I made a mistake and the dial was set to A-DEP or AV, one notch above or below M as listed in the install instructions.

I have tried all of the methods listed for a possibly bricked camera, and have seen a new post for a diagnostic test but have not moved forward on it.

Any suggestions as how to best proceed.  I would hate to have started my morning off with a cup of coffee and brick.  =^)

Thanks in advance!

MJ