SMC Update killed my computer!!

I just downloaded and installed the smc update from automatic updates. However, when the computer restarted it remained with a blank screen for 20 minutes. I tried to restart it but now the bottom power light under the track pad lights for a second and nothing happens. The computer seems dead now. I have everything disconnected and tried resetting the SMC, but to no avail.

Please help!

Powermac G4 Laptop, Mac OS X (10.4.7)

Posted on May 28, 2009 11:01 PM

Reply
204 replies

Jun 1, 2009 2:16 AM in response to Dean HK

A friend of mine tells me that this is indeed a firmware problem and that any power failure during the firmware installation will kill the computer. IN PCs, he says, one can reset the BIOS (he says it's the equivalent of the Firmware in Mac's) by pressing an hidden button, but this is not possible in Mac's.
Anyone knows how to do an SMC reset in a MBP?

Suggestion is to go to an Apple service and they might be able to restore the firmware, which might not be an easy task.
But this is not videocard or HardDisk problem! It is a firmware failure and that's why only a bunch of unfortunate people is having trouble, as somehow there was a power failure during the update process.

Jun 1, 2009 4:31 AM in response to dmph

Just to be clear, when you booted your iMac off of your MBP's hard drive (with the MBP being connected via Firewire and booted into "Firewire Target Mode"), which keyboard would not work?

If you can boot this way, you should be able to use the keyboard and mouse on the iMac. It will act as if you are using your MBP from a software perspective as you have booted your iMac using the MBP's hard drive.

I tried Apple Firmware Restoration CD-- it did not revert the firmware as the firmware update is technically "complete".

It's odd-- if i use the MBP with an external monitor, and pull the monitor cable, the LCD comes back fully awake for a few seconds before it dims/sleeps.

Jun 1, 2009 5:13 AM in response to dmph

Yeah, like I said... "pwnd"

The repair guy suggested I could get a brand new macbook for that much. It's sad, but true. They couldn't get it to do anything, so the default was that it was my fault or, as the repair guy put it, "bad luck." I totally meant to get applecare, but we just moved overseas and it was forgotten. Huge mistake on my part, I guess. 300$ versus 700 pounds.

I'm hoping that Apple comes back at some point and says, "Oops, here's your money back." I'm not holding my breath though.

Jun 1, 2009 5:42 AM in response to bhive01

Anybody with a happy ending on this? I keep coming back to this thread waiting to read some: "the MBP is working fine now" or "Apple is a planning a recall on this". I followed the instructions just right. No power failure during the update. I still believe it's apple fault and they should show their costumers some respect.
Here in Brazil it's 50 dollars upfront just for them to look at the computer.

Jun 1, 2009 7:23 AM in response to DRmbp

Got the same problem too.
Got prompted to update the SMC firmware to 1.3, and been asked to restart the computer once it's done.

Next reboot the screen didn't come back on. I actually thought it switched itself off and didn't bother checking until the next morning (had to hit the sack).

Tried resetting PRAM and NVRAM, tried resetting SMC. Tried starting with C, D, T...

No go.

I'd like to see Apple doing something about this, and called them in regarding to this. Apparently they haven't received any issues about this so far, or at least it hasn't appeared as an emerging issue to them.

Jun 1, 2009 10:30 AM in response to Dean HK

Same problems....MBP 17" first MBP intel processor, after software update stop work...when turn it on after 1 second that became the apple on the screen, kernel panic e compare messages in many lenguages to "turn off the computer" bla bla bla...

I'm disperate, tons of important work on it.

I'am a macuser from LCI and this one is the first machine that give me problems.

A 2700 €uros put in the hole....

keyboard impeftections, hot same a fire..., battery axplosion and sostitution, case that not close fine, and not after update stop work.

I think that at this price I can be very disappointed and now what I can do?!?!?!?

Jun 1, 2009 11:53 AM in response to Scott Nourse

Strangely, I've the opposite problem. I didn't have a problem with my fans initially but figured I'd do the update anyway. No problems there - update went smoothly and there were no noticed issues. I use my MBP at work and hook it up to a secondary monitor, and the second monitor won't work. The MBP recognizes the monitor, and the monitor can tell when it's plugged in vs. when the cable is unplugged, but the monitor immediately goes into sleep mode and won't come out of it regardless of what settings I use for it.

It's bizarre. Until I can use a different secondary monitor to test with (just to make sure that this one didn't randomly break over the weekend) I guess I can't point to the SMC update as the cause of this, but it's rather suspicious. I guess I should count myself lucky that my main screen functions properly and that it's only my video out functionality that's been broken (assuming that's what it really is).

Jun 1, 2009 3:28 PM in response to dmph

no people, this is NOT a firmware problem.

Here's my setup: Macbook Pro 15", 2.4GHz Penryn from early 2008, all standard equipment except I swapped out the harddrive with a 200GB 7200RPM one right after I got the computer

Here's what happened: When installing SMC 1.3, a window came up to prompt for restart, blah, blah... after ignoring it for an hour, i rebooted via that window's "restart" button. After an hour, I was still at the initial screen, after the apple-logo, now it displays a circle with diagonal slash, and a spinning thingy underneath.

Here's what I did: I called apple support, pressed 0 for customer service, yelled at the guy 'til she xfer'd me to a technician, at one point, the customer service rep was like "sir, you don't need to yell," and I effectively told her to shove it. I was furious with the technician too, who gave me some bs about warranty, and I told him that since it's an Apple update they forcibly pushed out, they have legal liability. Eventually, he said it may still be covered under your hardware warranty, and made an appt for me with an Apple genius at the local Apple store for next day when the store opened.

Here's what I tried after I got off the phone with Apple:
1. tried the usual stuff like PRAM, SMC zap, nothing
2. tried apple firmware restore 1.4, nothing
3. tried bootcamp and voila - by holding down "Option" at boot, you are given the choice to boot into Mac OS or Windows. I have Vista SP2, and figured might as well try that. It worked, which proves that it's not really a "firmware" problem. (was going to see if it can boot from CD, but didn't really bother)
4. took it to the apple store, the genius held "apple + s" at boot, to get into single-user mode, and saw the OS hanging at one point
5. he then booted from a firewire HD, since we established the bootloader is still intact when I booted into Vista
6. He ran disk-utilities, nothing came up (obviously)
7. He ran a system point-restore, restoring the OS to 10.5.6 (he quoted 20 minutes, I went to get lunch and when I came back, it was done)
now the computer is happy
8. I've updated everything once again via Apple Update, this time, SMC1.3 did not show up at all.

A bit of background about me - I do hardware, firmware, and driver development by profession, so I think I'm qualified to provide a guess as to what and where it went wrong:
for any computer, there's the initial "bootloader," which is what we commonly refer to as "firmware," and on the PC side it's the BIOS. This establishes the very basics of your motherboard, like "there is a CPU at address 0x0000 0000 0000 0000, there is 2GB of memory at address 0x0001 0000 0000 0000 0000, there is PCIe, there is graphics, etc..." When this gets screwed up, only way to restore the computer is via some "backdoor," often meaning a JTAG port. Some PC Motherboard has dual BIOS to make sure the updated BIOS will work before you can flash it to the "permanent" memory.

Next stage is the BSP (board support package) stage. This establishes basic driver things like "you can use 'writeToHD' function call to write to harddrive" etc. This will setup all the IO interfaces (harddrive, PCIe, whatever). This is where the "SMC 1.3 firmware" is inserted and went wrong... Since this BSP is also responsible to provide higher-level interface calls to the Kernel/OS, Windows and Mac OS uses different BSPs and we can boot into one but not the other. (If you've installed Windows XP via CD, when you first load the CD, there's tons of basic drivers it goes through before you can install, that's this stuff)

Next stage is the kernel, the all famous unix-based one Apple uses, or the Vista kernel. This provides stuff like TCP/IP stack, Bluetooth stack, etc.

At the end of the day, the "real" firmware wasn't really involved. Usually, when a BSP is updated, the entire BSP has to be recompiled and the Kernel should be recompiled with the new libraries provided by the new BSP. During the BSP compilation process, someone probably forgot to test some configuration (be it different HD, extra RAM, or whatever) and released it, causing the problem. This kind of bug is unacceptable and should result in someone getting fired if you ask me. I worked in Satellites and airplanes, these kind of errors could cause either billions of dollars or even lives! Judging by the fact that I had a restored BSP/Kernel and SMC1.3 did not show up, my guess is that this happened to enough computers and Apple had to pull the update.

Jun 1, 2009 4:01 PM in response to Dean HK

An update: My wife (bless her) took my MBP 2.2 into the local Apple store. Since my wife is not particular technical I gave her a printout with a description of the problem and what steps I'd taken to try and resolve it (SMC reset, zap PRAM, etc).

The tech took a look and confirmed the problem and took the machine in to replace the logic board (and possibly the display). No charge for the replacement.

While somewhat miffed that a simple software update could cause such issues and let me lose my prime machine for a few days, I have to say that I'm happy that they quickly accepted the issue and offered to rectify it.

Jun 1, 2009 4:07 PM in response to evangellydonut

Thanks for that. But I've tried holding Option or apple+s at startup and neither of those worked.

I don't feel like taking it to technical assistance until Apple has a word out about it, cause they'll probably want to replace my board and charge me for that. I don't think Apple Brazil has Genius trained personnel to help me out either.

Jun 1, 2009 4:09 PM in response to evangellydonut

evangellydonut, if all that the tech did was to reload your OS to 10.5.6, then your SMC version would have been untouched and that's why you didn't see it available in the updates. If he flashed anything on your board then it's likely that you ran Software Update and updated to 10.5.7, and then didn't run it again (the SMC update requires 10.5.7 or 10.4.11).

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

SMC Update killed my computer!!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.