Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

2011 MacBook Pros can support Handoff/Continuity

As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Yes it works on the final edition

gtot said:
Hi all.

Thanks for all the fantastic work done here.

I was about to try this solution on my mid 2011 MBA. I have had all public betas, but i just updated to the final version.

Do i need to change anything in the step by step guide, before doing it or should it also work for the finale 10.10 version ?

Rgds

Torben
Click to expand...

Just tried it...and it works fine on the official Yosemite as well on my MBA mid 2011. Thanks for the fantastic guide 🙂🙂
 
Königsblauer said:
The guide posted a couple of pages ago worked well at every Golden Master without any hardware modifications.
Click to expand...

I am not having good luck with this.

I have followed the guide here exactly: https://forums.macrumors.com/posts/20015070/

I have a Mid 2011 MBA with chipset:

Mac-742912EFDBEE19B3

When I reboot after replacing the kexts and running the terminal commands, the "enable handoff" does not appear and the System Profilers still says "No" in the Handoff boxes.

This is with the final release of Yosemite. I have double checked and the updated kexts are in the Extensions folder.

Any suggestions for things I can do to fix / debug this?

Update: I got it to work! I added an extra step. Once I had deleted to old kexts from the Extensions folder, I ran the cache clearing commands and rebooted. My Mac then lost Bluetooth and Wifi. In this state I then added the new Kexts via Kextdrop, ran the terminal commands again (including the one which puts the Mac into kext dev mode) rebooted and it worked!
 
Last edited:
hounslowfish said:
I am not having good luck with this.

I have followed the guide here exactly: https://forums.macrumors.com/posts/20015070/

I have a Mid 2011 MBA with chipset:

Mac-742912EFDBEE19B3

When I reboot after replacing the kexts and running the terminal commands, the "enable handoff" does not appear and the System Profilers still says "No" in the Handoff boxes.

This is with the final release of Yosemite. I have double checked and the updated kexts are in the Extensions folder.

Any suggestions for things I can do to fix / debug this?

Update: I got it to work! I added an extra step. Once I had deleted to old kexts from the Extensions folder, I ran the cache clearing commands and rebooted. My Mac then lost Bluetooth and Wifi. In this state I then added the new Kexts via Kextdrop, ran the terminal commands again (including the one which puts the Mac into kext dev mode) rebooted and it worked!
Click to expand...

I also have an MBA 13" (2011) and it was working for me from beta 4 to 6. Any success with the final version (14A389) anybody?
 
I have to say I'm a bit underwhelmed with handoff! It seems quite hit and miss at the moment.

Reminds me of Airtunes in the early days. I'm sure they'll fix it...
 
anthony cox said:
ok will do, also what would happen if the machine had a factory restore of the operating system, would i need to do this process again? silly question but i am going to sell my mac next year
Click to expand...

I can report my experience: The new 4CAX card works perfectly with both Mavericks and Yosemite 10.10 (official release). I have a Late 2011 15" MBP. In order to have handoff on Yosemite the new owner will have to play the .kext trick.
 
Hi All,

I'm really struggling with implementing this hack.

I've got a Mac Mini mid-2011 (Bluetooth LMP reports as 6), Yosemite Final (App Store public from yesterday).

The terminal dump of my Mac string is Mac-8ED6AF5B48C039E1

I've run through the steps, no errors (the first kext cache command came back and said it was allowing signature mismatch of one of the files).

But when I reboot, I still don't see the Handoff option appear under General.

Any help greatly appreciated


Cheers, Simmo
 
hounslowfish said:
I am not having good luck with this.

I have followed the guide here exactly: https://forums.macrumors.com/posts/20015070/

I have a Mid 2011 MBA with chipset:

Mac-742912EFDBEE19B3

When I reboot after replacing the kexts and running the terminal commands, the "enable handoff" does not appear and the System Profilers still says "No" in the Handoff boxes.

This is with the final release of Yosemite. I have double checked and the updated kexts are in the Extensions folder.

Any suggestions for things I can do to fix / debug this?

Update: I got it to work! I added an extra step. Once I had deleted to old kexts from the Extensions folder, I ran the cache clearing commands and rebooted. My Mac then lost Bluetooth and Wifi. In this state I then added the new Kexts via Kextdrop, ran the terminal commands again (including the one which puts the Mac into kext dev mode) rebooted and it worked!
Click to expand...

Hello all -- I have this same model MBA mid-2011, and I haven't been able to get this working, though I've tried following the tutorial twice. (This is my first attempt at modifying kexts on my machine, so maybe I've gone astray.) If anyone has a modified file for chipset Mac-742912EFDBEE19B3 that they'd like to share, I'd very much appreciate it.
 
I try in MBA mid 2011 and impossible

Terminal log is this
Last login: Fri Oct 17 14:49:34 on ttys000
MacBookAir:~ juanito$ ioreg -l | grep "board-id" | awk -F\" '{print $4}'
Mac-742912EFDBEE19B3
MacBookAir:~ juanito$ sudo kextcache -system-prelinked-kernel
Password:
kext file:///System/Library/Extensions/ZTEUSBMassStorageFilter.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/Vodafone.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/Contents/PlugIns/ssudserial.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/Contents/PlugIns/ssudmtp.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/Contents/PlugIns/ssudmdmdata.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/Contents/PlugIns/ssudmdmcontrol.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/ssuddrv.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/sony_prs2.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/RIMBBUSB.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/PdaNetDrv.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/OptionMSD.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/NovatelWirelessFilter.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/NovatelWireless3G.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/NMSmartplugSCSIDevice_106.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/NMHuaweiPhonesVTPCDC_106.kext/Contents/PlugIns/NMUSBCDCACMData_106.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/JMicronATA.kext/ is in hash exception list, allowing to load
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
BroadcomBluetoothHostControllerUSBTransport.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
IOBluetoothFamily.kext is not valid; omitting.
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AirPortBrcm4360.kext
kext file:///System/Library/Extensions/IceraUSBMassStorageBypass.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/Contents/PlugIns/HuaweiLogLevel.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/Contents/PlugIns/HuaweiDataCardHidPort.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/Contents/PlugIns/HuaweiDataCardECMData.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/Contents/PlugIns/HuaweiDataCardECMControl.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/Contents/PlugIns/HuaweiDataCardActivateDriver.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/Contents/PlugIns/HuaweiDataCardACMData.kext/ is in hash exception list, allowing to load
kext file:///System/Library/Extensions/HuaweiDataCardDriver.kext/ is in hash exception list, allowing to load
kext-dev-mode allowing invalid signature -67023 0xFFFFFFFFFFFEFA31 for kext BoomDevice.kext
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
AppleBluetoothHIDMouse.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
AppleBluetoothHIDKeyboard.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
AppleBluetoothMultitouch.kext is missing dependencies (including anyway; dependencies may be available from elsewhere)
Invalid signature -67023 for kext <OSKext 0x7fee1150efb0 [0x7fff7d45ccf0]> { URL = "BoomDevice.kext/ -- file:///System/Library/Extensions/", ID = "com.globaldelight.driver.BoomDevice" }
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
/System/Library/Extensions/IOBluetoothFamily.kext - missing load info or dependencies array in applier function.
/System/Library/Extensions/IOBluetoothFamily.kext - missing load info or dependencies array in applier function.
Can't resolve dependencies amongst kexts for prelinked kernel.
Failed to generate prelinked kernel.

Any help please??
 
whsbuss said:
How hard is it to install? Anyone do a youtube on it yet?
Click to expand...

Its not that hard you just need to take your time. The routing of the antenna wires is really the hardest part. The part is a lot smaller than you think and its inside a plastic case. It took me maybe 20 minutes.
 
MrSimmo said:
Any help greatly appreciated


Cheers, Simmo
Click to expand...

I was in same place as you. Try deleting both kext files, clearing kext caches, rebooting (now bluetooth and wifi should both be disabled), then reinstalling the kexts and follow the rest of the instructions.
 
spitf1r3 said:
I also have an MBA 13" (2011) and it was working for me from beta 4 to 6. Any success with the final version (14A389) anybody?
Click to expand...

Works! I repeated every single step and noticed, that all modifications made in the kext-files were kept after the installation of the final Yosemite from GM 3 / latest Beta.

----------
hounslowfish said:
I have to say I'm a bit underwhelmed with handoff! It seems quite hit and miss at the moment.

Reminds me of Airtunes in the early days. I'm sure they'll fix it...
Click to expand...

For me, it's huge difference between Handoff or Call-Forwarding vs. Instant Hotspot. The latter one works rather seldom
 
Camillionaire93 said:
i have a early 2011 macbook pro 13'' which one should i get?

will this one work?

http://www.amazon.com/Eathtek-MacBo...1537&sr=8-1&keywords=macbook+pro+airport+card

the one in the picture shows BCM94331PCIEBT4AX but the details/description says BCM94331PCIEBT4CAX.

assuming that it is the BCM94331PCIEBT4CAX will this one work?

thanks
Click to expand...

I'm ordering one via Prime to have it delivered Sunday.

I'll follow up to if it's a *CAX model. If it's not, I'll just easily return it saying it doesn't match the item description for a refund. Perks of the item being "fulfilled by amazon".
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
kittonian said:
I realize we are talking mid-2011 here, but is there any solution to upgrade a mid-2010 MBP?
Click to expand...

rob3r7o made it happen. Steps here.

----------
johny979 said:
I try in MBA mid 2011 and impossible

Terminal log is this
(...)
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
IOBluetoothFamily.kext is invalid; can't resolve dependencies.
(...)
Any help please??
Click to expand...

Something went wrong when you patched your bluetooth kext, it seems corrupt. Get your IOBluetoothFamily.kext backup and try the 0xED editing steps again carefully, manually (not a find & replace). Let me know in case you lost your backup.
 
Last edited:
hounslowfish said:
I was in same place as you. Try deleting both kext files, clearing kext caches, rebooting (now bluetooth and wifi should both be disabled), then reinstalling the kexts and follow the rest of the instructions.
Click to expand...

Cheers,

One step forward; I've got an error on kext cache -system-prelinked-kernel now, says 'AirPortBrcm4360.kext not valid omitting' now. Still no joy on the handoff unfortunately.

Any ideas?
 
dokterdok said:
rob3r7o made it happen. Steps here.

----------



Something went wrong when you patched your bluetooth kext, it seems corrupt. Get your IOBluetoothFamily.kext backup and try the 0xED editing steps again carefully, manually (not a find & replace). Let me know in case you lost your backup.
Click to expand...
I think the biggest thing making the tut not work for people is when they use find/replace or copy/paste. I walked a few people thru your tutorial last night and got it working for them and modified some and emailed for others. I found it ALWAYS works if you do it manually and very carefully. One missing . or ' means corrupted kext. I think people were excited and did it too fast and messed things up to be honest. 99.99% User error hah
 
UncleSchnitty said:
I think the biggest thing making the tut not work for people is when they use find/replace or copy/paste. I walked a few people thru your tutorial last night and got it working for them and modified some and emailed for others. I found it ALWAYS works if you do it manually and very carefully. One missing . or ' means corrupted kext. I think people were excited and did it too fast and messed things up to be honest. 99.99% User error hah
Click to expand...

Thanks for your help in this mod. You and a bunch of others have been consistently helping people which is sweet.

This is kinda tangent, but I think some of the problems stem from this mod being slightly above the typical comfort level for a lot of users. I think a lot of people know enough to know that they want to do this mod and it is possible, but they don't know enough about the files and systems being modified to retrace steps when they go wrong.

I think people get carried away like you said and do this mod without knowing what they are actually doing. When I first started reading this thread, I certainly didn't.

For me personally, I can't leave well enough alone and when I saw people were providing kext files, I wanted to use them but also wanted to understand what was changed so when ***** hits the fan, I will have a better understanding of how to reverse it or fix it. It is my understanding that the only thing being modified in the kext files is replacing one or more of the "approved board ids" list in the new BT4.0 board file(which omits ids from various MBs circa 2011 etc), to include the ID of the board in your current machine. Pretty simple (but I wouldn't be able to figure that out without help from reading this thread).

I would just ask people reading this thread to understand all of the steps and what you are actually doing like I did. If you do not know what a specific thing does, like

Code: 
sudo nvram boot-args="kext-dev-mode=1"

or even just the "sudo" in it, check it out and research it a bit. You will find yourself being a lot more comfortable with how computers work if you do.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back