Unlike the Canon P&S's, the 350D required that a program be run one time to change the setting of the boot flag so that it would later boot up the alternate software from the memory card. Magic Lantern works the same way on later DSLRs.
The original program to do this on the 350D, scanled.fir AKA bootflag.fir, was defective. It did not check for the proper firmware version, and did tests the results of which were ignored. The program worked for most people, but a few ended up bricking their cameras - even if they had the right firmware.
I worked on a new version to correct these shortcomings beginning with reply #329 in the 350D thread, and ended up publishing bootflg2.fir in reply #342:
http://chdk.setepontos.com/index.php?topic=4202.msg57328#msg57328But then a while later I sold my 350D, so I haven't kept up. But as far as I know my program worked ok for everyone. Well, to be specific, it did a bunch of tests, and if those didn't pass, it stopped before doing anything that might brick the camera. So far as I know.
The problem is that I don't know if my version replaced the bad one in the wiki or whereever the downloads are. So someone coming along now and starting at the beginning of the thread may not see the work I did, and end up using the original scanled or bootflag file, which I believe would be the wrong thing to do.
madly_sin, I don't know which version you used. I hope it wasn't mine. Anyway, the only cure I've ever seen for bricking was one guy who took all the batteries out and let the camera sit for a month that way. When he fired it up again, it worked. Probably just a coincidence, but might be worth a try.
However, if your camera worked ok on the initial install, then died later, it probably has nothing to do with the hack.
