4 Replies Latest reply: Jan 26, 2012 12:49 AM by UserNameX
Topher Kessler Level 6 Level 6 (9,790 points)

2009 MacBook Pro 5,2 (2.66GHz Core2 Duo), recently upgraded to 8GB RAM, 320GB HDD with an OWC SSD drive replacement for the optical drive.


The system ran great, and was really fast given the recent 8GB upgrade and SSD as the main boot drive. I decided to set a firmware password for added security...worked no problem. The system rebooted fine, and requested the firmware password as expected when attempting to boot to alternate drives.


I then enabled FileVault 2 in Lion (10.7.2), and it worked as expected and seemingly encrypted the drive just fine; however, in Disk Utility the main boot drive was greyed out. Figuring it might just be a temporary issue I decided to reboot. Upon restarting, I get the boot chimes and nothing else...dead!


Now when the power button is pressed, the system's fans and HDD start up as expected and the boot chimes sound, but then it sits there. The screen does not turn on, and the system does not boot. The caps lock light activates, but it does not get past this point. Pressing the power button again results in an immediate shutdown, suggesing the SMC is not activating properly since it usually requires a ~5 second press for a hard shutdown.


I am able to reset the SMC, but doing this does not show any difference in behavior. I am not able to reset the PRAM at all--the system just sits in this dead state and then shuts off immediately when the power is pressed. I suspect the firmware password setting is preventing the PRAM from resetting, so I swap out RAM to clear the password (from 8GB to the old 4GB set), but this has no effect and the system behaves the same...dead.


I've tried booting without RAM and the system issues warning beep sounds as expected, and I've tried disconnecting the battery for a while and unplugging the hard drives, but no change.


My only conclusion is a completely corrupt/fried firmware that if only I could force to reset would work properly, so it seems beyond somehow doing this the only options are to replace the logic board (unless anyone has any other ideas).


Anyone else experience this kind of complete firmware/hardware failure?