Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
EFI update issue
- Thread starter SangYuP
- Start date
- Sort by reaction score
my MBP was back from service (7 days).. upgrade EFI with SL without a problem but... this damn AS Retail haven't done all the tests, because right fan is faulty
now i need to go back another time to this damn retail and get another fix..
What do you mean by faulty?? Which MBP do you have (as the 13 only has 1 fan)?? If it is not reporting in iStat,I would just open the back and make sure it is plugged in and that they didn't forget to plug it back in or it didn't get seated properly, before i made the trip back to the store.
15 inch, two fan.. already checked the cable, fan doesn't spin.. also AHT give fan right error
stupid technichan.. he doesn't have make any type of test on the HW (as the report list) -_-"
I have a solution!!!
For guys who upgrade the EFI of MBP8 (early 2011) to v.2.2 and after that gets a crazy problem. I created a solution http://goo.gl/CXbf1 #mac #firmware
This is a mod of original pkg of firmware upgrade to force reinstallation to able you to downgrade (to v2.1).
Good look!
Work for me.
My Twitter: @upNic
For guys who upgrade the EFI of MBP8 (early 2011) to v.2.2 and after that gets a crazy problem. I created a solution http://goo.gl/CXbf1 #mac #firmware
This is a mod of original pkg of firmware upgrade to force reinstallation to able you to downgrade (to v2.1).
Good look!
Work for me.
My Twitter: @upNic
Well, I had the similar problems and it seemed to be solved by re-applying the firmware 2.2 update. However, the EFI 2.2 package refuses to re-update if it finds the machine is already updated to 2.2. Therefore, the update can only be done manually in the terminal.
Please also remember to "unplug" all peripherals such usb, external monitor, firewire, and ethernet.
Here are the procedures:
(1) please check whether the file exists:
/System/Library/CoreServices/Firmware\ Updates/MacBookProEFIUpdate-2.2/MBP81_0047_1EB_LOCKED.scap
It should be the image of EFI 2.2
(2) please open the terminal and type the following command:
sudo /usr/sbin/bless -mount / -firmware "/System/Library/CoreServices/Firmware Updates/MacBookProEFIUpdate-2.2/MBP81_0047_1EB_LOCKED.scap" --recovery --verbose
(3) Please enter your password and wait. There would be some messages pop in the window and the prompt will appear soon again.
(4) Type "sudo reboot" to reboot the macbook pro
(5) A long low-tone chime, which is different from the chime for booting, will be heard. After the chime, the typical progress bar for updating firmware will appear on the screen.
(6) After the bar is over, the macbook pro will reboot soon and the whole procedure is finished.
This command is collected from the "blessEFI" within EFI 2.2 package. The "bless" command seems not be fully documented and the option -firmware could not be found in the relevant man page.
Please also remember to "unplug" all peripherals such usb, external monitor, firewire, and ethernet.
Here are the procedures:
(1) please check whether the file exists:
/System/Library/CoreServices/Firmware\ Updates/MacBookProEFIUpdate-2.2/MBP81_0047_1EB_LOCKED.scap
It should be the image of EFI 2.2
(2) please open the terminal and type the following command:
sudo /usr/sbin/bless -mount / -firmware "/System/Library/CoreServices/Firmware Updates/MacBookProEFIUpdate-2.2/MBP81_0047_1EB_LOCKED.scap" --recovery --verbose
(3) Please enter your password and wait. There would be some messages pop in the window and the prompt will appear soon again.
(4) Type "sudo reboot" to reboot the macbook pro
(5) A long low-tone chime, which is different from the chime for booting, will be heard. After the chime, the typical progress bar for updating firmware will appear on the screen.
(6) After the bar is over, the macbook pro will reboot soon and the whole procedure is finished.
This command is collected from the "blessEFI" within EFI 2.2 package. The "bless" command seems not be fully documented and the option -firmware could not be found in the relevant man page.