MBA mid 2011 2.9 Firmware update just killed by Air

If this is the only device that you have access to and have no alternative device available, in case this does not work, Zantac_150 and EdisonW have two opposite results. YMMV.

Since you have a partial update, during the course of normal work, you MBA may be rebooted and may provide some instability. I would suggest doing the procedure, but your issues may get worse.

Loner T: Once again, very useful info.

Since I have other devices and my MBA is currently working fine I will check which Firmware version is actually installed before deciding if I should complete the installation of buggy 2.9 (by following above procedure) or wait for Apple to provide newer Firmware update.

Thanks!!

Albert

I don't believe you can "complete" the installation, as Apple has pulled the update.

If it were me, I would wait until Apple re-releases this EFI in a fixed form and then go ahead with the update IMHO.

According to this:

MacBook Air EFI Firmware Update 2.9.1

The system requirement for the update is: MBA41.0077.B11, which I believe was last weeks EFI 2.9 that would not install on most MBAs, and that Apple later removed.

The new 2.9.1 shows up in App Store software updates, even though I never succeed installing the EFI 2.9,

I really don't know if I dare try to install 2.9.1.

Jens

Can't imagine 2.9 being a pre-requisite since they pulled the update. It seems to be a totally new install for the EFI update. In any event, my installation went without a hitch. My Mid-2011 13" MBA now shows Boot ROM Version: MBA41.0077.B11 in System Report.

It could be that the App Store is smart enough to know if you tried to install 2.9 before ... and if so offers 2.9.1? And for those who never tried the App Store may show 2.9? In any event, I was one of the first to participate in the thread and I tried to install 2.9 a few times. As I said above, 2.9.1 installed for me without any issues whatsoever.

From the old log that EdisonW had posted on 22 July 2014 ...

Jul 22 14:58:03 Drs-MacBook-Air.local installd[269]: postinstall: 2 : <CFString 0x10ef08eb0 [0x7fff7937ff00]>{contents = "efi-apple-recovery"} = <CFString 0x7fdda9600310 [0x7fff7937ff00]>{contents = "<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia </string><key>IOPropertyMatch</key><dict><key>UUID</key><string>3D4CFE9E-2731-4 7 43-940F-4B8AD73DDC1A</string></dict></dict><key>BLLastBSDName</key><string>disk 0 s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</st r ing><key>Path</key><string>\EFI\APPLE\FIRMWARE\MBA41_0077_B11_LOCKED.scap</strin g></dict></array>"}

The internal version has not changed but the content seems to have changed. 😎

Hello Loner,

I've just successfully installed the new 2.9.1 EFI update onto the same machine from which Apple harvested the diagnostic logs from my case number, and can confirm it installed with no issues, and the Boot ROM Version is now "MBA41.0077.B11".

I can also confirm the wireless, cooling, and all other systems are running as they should! The only thing I've noticed, is when the machine shutdown to perform the installation, the screen still went dark for about 4 seconds before the traditional grey screen with a progress bar.

Other than that, everything looks like it's back to normal. I think it's safe to say this issue has been resolved with 2.9.1.

What I'd love to hear, is if people here who've experienced non-bootable MBA's after the original update, can get their system running again using some of the troubleshooting steps that have been documented here, and then install the new update and report results...

Cheers

I am glad new 2.0.1 update came out for those hwo are out there. But my mid-2011 MBA became non-bootable after 2.9 update. And none of the steps provided through this forum solved problem. I am currently out of luck but to decided whether to pay to fix it or not which was really unnecessary.

After the failed installation of 2.9 last week (x2) and although Software Update history indicated I installed it twice, I suspect the 2.9 was never actually installed in my MBA since the System Report indicated still having BOOT ROM Version: MBA41.0077.BOF (EFI 2.4) which was the latest listed at EFI and SMC firmware updates for Intel-based Macs

I just installed EFI Firmware update 2.91 and had no problems whatsoever (new BOOT ROM Version: MBA41.0077.B11). Therefore, having 2.9 installed is not a pre-requisite for the installation of 2.91.

Issue resolved!

Many thanks to Loaner T and all others in this thread.

No, I didn't pay anything and I still do have my bricked-non-working-MBA.

Apple Genius Bar person couldn't do anything but to suggest to pay it and fix it.

But I didn't want to. Because it was simply not my fault at all.

i downloaded 2.9, had no problem with it but the thing it isn't doing what it suggest... still having problems when waking up take too much time. today in installed 2.9.1 I'm gonna find out if this version solves the problem...

Is there anyone else still experiencing keyboard issues? Even after 2.9.1 update?

I have 4 dead keys since the 2.9 update. I did not have the worst of the other problems and just experienced the dead keys since waiting for the fix which I installed today (2.9.1) without fixing my dead keys on my build-in keyboard.

I tried, I think, all of the reset options found searching the net. Like SMC, NVRAM and whatever. With no effect. Booting from an backup also shows these keyboard issues. Following the instructions here One or more keys on the keyboard do not respond (9.4) shows on my (german) keyboard 2 keys are colored orange and are 2 of the 4 dead keys.

The dead keys are (1) on the left the key below esc which is "^" (US keyboard: "§") (2) "F12" (3) the key below F12 and right of backspace which is "´" (US keyboard: "=") (4) next right to P which is "ü" (US keyboard: "[")

Anyone else with this strange thing?

Thanks

I never installed the original 2.9.0 EFI update but installed the 2.9.1 update the other day. Since then, I'm having problems with my keyboard and cursor not responding when trying to enter my username and password to login.

This means I have to hold the power key down to turn the laptop off and then turn it on again - this time I can enter my password and move the cursor. It only seems to happen if the laptop sleeps and on wake-up doesn't recognise the keyboard/trackpad.

Anyone else got this problem?

Roj Snook wrote:

I never installed the original 2.9.0 EFI update but installed the 2.9.1 update the other day. Since then, I'm having problems with my keyboard and cursor not responding when trying to enter my username and password to login.

This means I have to hold the power key down to turn the laptop off and then turn it on again - this time I can enter my password and move the cursor. It only seems to happen if the laptop sleeps and on wake-up doesn't recognise the keyboard/trackpad.

Anyone else got this problem?

Two suggestions.

1. In Applications -> Utilities -> Console check /var/log/install.log for successful Firmware Update.

2. Reset SMC.

You can also check messages in the log (All Messages) for events after the wake for any error messages related to HID.