Can't install EFI Firmware Update? Check partition scheme; disconnect peripherals
As we reported earlier, many people (especially MacBook Pro owners) are finding that although, according to the descriptions at Apple's Web site, their computer should be eligible for the recently released EFI firmware updates, nevertheless they get an error message informing them that the update can't be installed, or a flat-out denial from the installer that the machine requires the update.
Now comes word of an amazing possible fix, that has worked for some people (at least three of our readers wrote in independently to say that this was the case for them).
As you may be aware, there are two current "partition schemes" for Macintosh computer disks: the earlier Apple partition scheme, which is used for disks that will boot up a PowerPC machine, and the GUID partition scheme, which is used for disks that will boot up an Intel machine. You could encounter this distinction, for example, when a system installer running one type of machine refuses to let you install the system onto a disk that is partitioned for the other type of machine, as described in this Apple help document and this one.
However, there's an asymmetry here. Although a PPC machine cannot boot up from a GUID-partitioned disk, an Intel machine can boot up from an Apple partition scheme disk. Running an Intel machine, you can't install a system onto an Apple partition scheme disk, but if you start with a disk on which an Intel-appropriate system somehow has been installed, even if it is an Apple partition scheme disk, the Intel machine will start up from it.
This, it seems, is exactly what has happened to our three readers. Each one has written in to say, in effect: "I used Disk Utility to check my partition scheme (as described in this Apple article) and it wasn't GUID-partitioned!" In two cases, this had to do with the fact that the user had installed a new hard drive into the machine, but in one case, the hard drive simply came like that, purchased from the store.
In each case, repartitioning the drive as GUID allowed the firmware update to be installed. But there's a warning involved: repartitioning your drive as GUID will erase all your data! The only way to do this is to back up to some other disk and then restore. This task is not for the faint of heart, although it can be made a lot easier using a utility such as Carbon Copy Cloner or SuperDuper, which can clone your entire hard disk contents from one drive to another.
So the procedure would be: Use Disk Utility to Get Info on your internal drive (the whole thing, not just a partition of it) and thus check the partitioning scheme of your internal drive. If it isn't GUID, then you could clone to an external drive, boot from the external drive or from your installer DVD, repartition the internal drive as GUID, clone back from the external drive to the internal drive, boot up from the internal drive, and perform the firmware update.
Even if you don't perform this entire procedure (which is admittedly more than a little drastic) it would certainly be interesting (and easy) to check whether, if you're having trouble installing the Intel firmware update, your internal drive is using the Apple partition scheme. Please do check, and let us know what you find out.
Also, do note that according to this article from Apple, it might be sufficient to clone or install the system to an external GUID-partitioned disk, boot from that, and install the firmware update, without ever repartitioning the internal disk at all. Firmware lives in your computer's chips, not on the hard disk, so this should work fine.
Peripherals Another idea is simply to make sure no unnecessary peripherals are connected to your computer. Two readers reported independently that merely disconnecting an external firewire drive or USB device allowed them to proceed with the firmware installation. Rebooting in Safe Mode (hold down Shift during the startup procedure) might help too, we're told.
Resources

Oops! I checked the volume not the drive. The drive is GUID partitioned.
I think if you read the Apple Knowledge Base article referenced in MacFixit's article, there is no update for the MacBook Pro 2.4/2.2 ghz 17 inch model, and MBP31.0070.B02 is the latest firmware version for the 15 inch version. As I understand this, you don't need the update on either machine, so this isn't a problem for you.
Had lots of problems booting the cloned disk, eventually got Disk Utility to repair permissions (probably had incorrect settings on CCC).
But the bottom line was that when I finally got the cloned disk to boot, I started the Macbook EFI Firmware Updater and it worked! No need to wipe my system disk (shudder!).
The other good news is I now have an up-to-date bootable backup of my system disk. :-)
HTH
What version of Carbon Copy Cloner did you use? The latest version, 3.0.1b1, might have done the copy correctly.
It sure seems like the Apple Firmware Restoration CD should allow the update, but I can't get it to boot either:
http://www.apple.com/support/downloads/firmwarerestorationcd13.html
Install to a GUID disk, then clone to a MBR disk. This is used often by those multibooting linux on their Macs.
Thanks macfixit.
My System is on an GUID partition scheme.
I get a white screen after the "long Beep" and after a few minutes the cpu fan start to run.
I disconnected all my peripherals but this does not work either.
Any suggestions?
Regards,
jan
Same for me. Exact same behaviour. Apple has to fix this. GUID is correct, external hard drive or EFI CD don't work.
I can confirm above strategy worked for for my gen 1 MacBook Pro Core 2 (2.1). I triple boot Mac OSX/Vista/Linux, using an MBR instead and rEFIt bootloader instead of GUID. EFI 1.4 update would not flash until I shadow copied my Mac OSX partition to my HFS+ formatted USB drive (made bootable) using SuperDuper; booted up my lab top off the USB, and ran the update from there. Worked like a charm.
Thanks for the advice. I highly recommend this approach. If something does go wrong on the main drive, you have the shadow copy on the USB drive to restore from. Of course all other OS/partitions should be backed up first IMO.
Good luck,
John
Strange!
Baseball Bats For Sale
Cheap Baseball Bats
Cheap Baseball Bats
- by levancil January 20, 2010 4:38 PM PST
- My close friend in Kobe Japan had a problem with this update. His internal drives were HFS+ raid 1 and raid 5 ( 2 drives ) He ended up having to disconnect the internals and boot from an external GUID firewire 400 drive. Until he disconnected the internals the update always failed with drive not GUID errors.
- Like this Reply to this comment
-
(16 Comments)