Personally I wouldn't bother with that if Apple will swap out the motherboard - that way you get a later chipset, maybe even later stepping CPU, GPU, etc.) (He noted Monday that his 10.6.8 system would only boot into safe mode after installing the update manually via Pacifist. I still might try to hack the software patch into submission, but will probably end up just getting the board replaced. Turns out, unless you're running 10.7.2, the 'fix' is hardware based, i.e. Went to the Apple Store here in Boston (just visiting) and took my MBP in to try to get the 'fix'. "More on the 2010 15in MBP video update (10.6.x user) (I mentioned in Monday's post on the update that it is not 10.6 compatible, verified by his Pacifist install attempt in 10.6.8.) ( Original post from October 26th follows:)Īs promised, here's notes from the reader with an affected 2010 MacBook Pro 15in running 10.6.8 and therefore can't use the MacBook Pro Video Update 1.0 software update for 10.7.2 released Monday. ( Update: On Nov 14th, 2011 Apple posted an updater for 10.6.8 users - see MacBook Pro Video Update 1.0 (Snow Leopard)) Service Notes from 2010 MacBook Pro 15in owner w/Video issues - Motherboard Swap is fix for OS X 10.6.x users Mac Upgrades/Mods | Storage | Video | Audio/Home Theater | Tips/OS Updates/WiFi News Archive for Wednesday, October 26th, 2011: Go to Current News Page Apple posted this in the now archived website About EFI and SMC firmware updates for Intel-based Mac computers.Accelerate Your Mac! News page - News Archive for Wednesday, October 26, 2011 At some point, Apple decided to include firmware updates in the macOS installs. You used to manually update the firmware. The APFS is new and older Macs would need a firmware update before being able to recognize this filesystem and read the boot files. Having to update the firmware to run High Sierra makes sense. Basically, the same procedure occurs for firmware updates on my HP PC running Windows. The firmware is then instructed to update itself. When a SDD or HDD is formatted to use a GUID partition scheme by the Disk Utility or diskutil command, the EFI partition is automatically created.īasically, the firmware update is copied to the FAT32 formatted EFI partition. Apple posted that firmware updates require a GUID partition scheme at the archived website Firmware updates for Intel-based Macs require a GUID partition scheme, although the site does not explicitly say this must be the primary drive. I assume this EFI partition must be on the primary internal disk. The EFI partition is used when the firmware is updated. Error while writing firmware updater for EFI. disconnect all internal hard drive, connected the USB external drive and SXCARD reader.It selected the ESP on internal hard drive as the staging EFI. kept internal hard drive connected, connected the USB external drive or SXCARD reader.replaced the Samsung SSD with original Apple HDD and tried again.Unfortunately the first one of my MacBook is out of order.Ĭonfirmed the following methods do not work. It seems that the root cause is running OS X from a second internal disk. I've just seem a related post Is there any way to manually bless firmware when main disk is external? In another word, the Boot ROM Version hasn't been changed. Then, 3 times power off automatically in a short period, end up with a normal OS X startup. It got a flashing LED light indicating the firmware was about to be updated. sudo bless -mount / -firmware /MBP91_00D7_B00.scap -verbose -recovery Thus, I've no idea why High Sierra installer failed to update the EFI firmware at the very first time.Īccording to the chapter 2.0 How Does a Mac Update Its EFI Firmware & How Do You Find Your EFI Version of The Apple of Your EFI, with the following command bless, the file MBP91_00D3_B0C_LOCKED.scap extracted from mac2015002efiupdate.dmg, which downloaded from, and the file MBP91_00D7_B00.scap extracted from Install macOS High Sierra.app, it executed successfully. usr/libexec/efiupdater finished with status: 0 Writing firmware update installed cookie (/Volumes/MacSSD/macOS Install Data/.FirmwareUpdateInstalled) Volumes/bless.YdD7/EFI/APPLE/FIRMWARE/MBP91_00D7_B00.scap created successfully If look into previous log of EFI updating, it seems they are quite normal. Operation: Verify firmware failed, Failure Reason: Error Domain= Code=512 Key info in ia.log is as following.Ĭlearing automation and attempting to rebless.įailed to get disk for UUID specified for rebless. Here comes the detail.Īttempt 1 - update it by updating macOS from 10.12.6 to 10.13.2įailed with error message "An error occurred while verifying firmware". In short, the firmware cannot be updated either by upgrading macOS to High Sierra or by bless manually.
0 Comments
Leave a Reply. |