My T2i just died

L

Lenilenapi

Carbonite Member
My T2i just died. Unless all of 3 batteries surprised me by suddenly being dead - its the camera.
I can't get any image on the screen and its not responding. When I initially put a battery in I see a little bit of the blinking red light and if I hit the Live view button I hear a click, but then its dead as a doornail.

2 Things preceded this -
One I have the feb 14th version of Magic Lantern in the camera. I first suspected that , however then I noticed my hoodman Raw SDHC card plastic housing was cracked. This is the second time that's happened to me with that card! Could tyhe card problem kill the camera.
The last few times I powered it up I noticed that it would go dead on me but I turned it on and off at it was OK. I assumed it was ML acting weird , but that's before I noticed the card.

This sucks. I hope I'm still in warranty , though will they know I had ML on there if I don't have that card in the camera?

Lenny
 
Sorry to hear lenny.. Did you try a fresh SD card possibly? When I cut on my camera w/ ML on it, I wait almost 15+ sec before pressing anything *just in case. Do you have battery Grip too? Maybe remove that too and see..

GL anyhow...
 
(from ML thread)

Tried both no card and a non ML card that I know is good.

When I turn it on the screen stays black. and there are some blinking red lights at the bottom which soon stop. No buttons do anything except the Live view which makes a clicking sound, then I hear another clicking sound and that's it. If I turn the camera on and off there will now be no response at all.

Lenny
Click to expand...

The clicking sound is the normal clicking sound which you used to hear when camera went in LiveView mode, and then back?

If you start it in photo modes, do you see anything in the viewfinder? Does it autofocus?

Does EOS Utility see the camera via USB?
 
OK more tests. The camera seems to function out of live view in still modes.
I can see the readout in the viewfinder for stills and adjust ASA shutter etc. and it will snap stills.
If I hit the live view button though it I hear it click then it freezes and I see an Err 70 code in the viewfinder.
At that point I have to turn off pull the battery and put it in again and then the viewfinder functions again.

If I just go into movie mode I also hear the click and the freeze and the Error message in the viewfinder.

EOS utility connects OK & you can look at the card. but when you put it in live view through the software the same thing happens you get an err 70 code and the software freezes as well until I disconnect the USB cable
 
Well I was about to send in the camera when I decide to scour the web for a long time looking for other people's experience. Seems Error 70 is pretty common on all the Canon line.
Then low and behold I come across a guy who fixed his on a 7D and Praise be to Allah, Jesus, Moses and Saint John Coltrane the damn thing worked!
The previous poster had this happen with a Black Magic HDMI adapter but for me it was an HDMI Lilliput monitor.
So here is the fix:


--power down camera and remove battery
--power down HDMI device or powered adapter
--unplug the HDMI from the body, then plug it back in
--power up HDMI device or powered adapter
--insert battery and power up camera

In my case the lilliput image came up, I unplugged the HDMI and my live view was back on the camera.

So what caused it? Don't know. I had been using my Lilliput the day before this happened and perhaps the problem started randomly at that point.
It may have had something to do with my cracked SDHC card as I found a few posts where people said the problem followed them on multiple cameras when they kept using the same card. But that was just a few posts and it may have been accidental. One guy had 4 7D's brick with Error 70 after connecting to the same PC. ( Think you'd stop after 2 or 3?)

I thought at first it was magic lantern but so many people posted with 7D's 5D's 1D's etc that I got more dubious about that.

Anyone else see this on an ML camera?

That's all for now. Maybe the solution should be a sticky here. I'll at least post it as a separate thread so it will show up in searches more easily.

Hope the camera stays fixed or I'll be back.

Lenny
 
This sounds like HDMI setting was left stuck on the camera (which means it may be saved in the non-volatile memory). If my theory is true, it would happen either if you take the battery out while HDMI is plugged, or if you turn off the camera with HDMI connected and restart it without it. Can you check if these are true?

(I don't have a monitor to check it myself)

Which also means I won't be able to enable a "dummy" HDMI mode for taking higher-res silent pics in ML.
 
I will check it out and report back Alex. Could it have anything to do with turning the HDMI output off and on when toggling the audio monitoring function also?

Lenny.
 
Neither scenario reproduced the error. I do not have ML installed at this time if that makes any difference to you. Its on the cracked card and I want to get a new card before I try it again.
You can keep sending me new things to try Alex. Anything I can do to help troubleshoot it. This was a nasty scare indeed.

Odd thing is many people have reported it on different cameras and it often is just a random problem not a permanent dead end like mine was. However I think I was having the problem randomly for a few days and just never looked in the viewfinder to see the Err 70 message. At first turning the camera on and off fixed it. Then it became all the time.

Another oddity is that a number of people reported having it happen again after getting the camera back from Canon repair tho the 2nd time it was always fixed. Canon said it was the failure of a component.

There may be different problems resulting in the Error 70 message though.

Lenny
 
It shouldn't make a difference whether ML is loaded or not, as it does not (try to) interfere with HDMI connection. Only when Audio Monitoring is enabled, it kills all the external connections.

If people say the problem persists after repair, I believe it's an intermittent bug which can only be fixed by a firmware upgrade (and which appears to be fixed by changing a component). This kind of bugs is very difficult to find and troubleshoot, because they can happen once in 1000 restarts or so.
 
I just talked with someone else who had the problem after connecting to an HDMI TV.

Oh well I'll just have to see what happens. Carry an HDMI device with me at all times in case it recurs.
 
You must log in or register to reply here.
Back
Top