Open PeterHolbrook opened 6 years ago
I think not because 10.13.3 is the last version that worked
Why do you say 10.13.3 is the last version that worked? I'm on 10.13.5 on a Mac Pro 5,1 and Continuity works just fine.
@PeterHolbrook : Yep! Me too, MacBook Pro Early 2011 w/updated CAX BTLE card...works great! Have not tried Mojave yet, and don’t plan to until at least official release. (Plus I’m annoyed anyway that Apple is dumping support for most all of my Macs except for my Mac Mini 2012. Using the open source patch tool, I’m running High Sierra on a MacBook Pro 2009 Unibody and it works perfectly without issue. So dropping support for older machines is complete BS in MANY cases. Same will go for Mojave...there is no technical reason it cannot run on an iMac 2010 w/Quad-core i7 and 32MB of RAM. Apple continues to piss off their original enthusiasts and evangelists... It is a shame what has happened to them.
Aye, me too with the exact same hardware and macOS configuration as DOCSISMAN (early 2011 17” unibody MBP + updated 4CAX card running High Sierra 11.13.5), and Continuity / Handoff / etc works like a boss!
Sent from my iPad
On 26 Jun 2018, at 00:19, DOCSISMAN notifications@github.com wrote:
@PeterHolbrook : Yep! Me too, MacBook Pro Early 2011 w/updated CAX BTLE card...works great! Have not tried Mojave yet, and don’t plan to until at least official release. (Plus I’m annoyed anyway that Apple is dumping support for most all of my Macs except for my Mac Mini 2012. Using the open source patch tool, I’m running High Sierra on a MacBook Pro 2009 Unibody and it works perfectly without issue. So dropping support for older machines is complete BS in MANY cases. Same will go for Mojave...there is no technical reason it cannot run on an iMac 2010 w/Quad-core i7 and 32MB of RAM. Apple continues to piss off their original enthusiasts and evangelists... It is a shame what has happened to them.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
I got with 10.13.5 a bootloop when I try to install it
You should investigate why it doesn't work for you. It's normally flawless.
I have a MacBook Pro 2011 which is NOT supported by mojave. I have an upgraded internal wifi card. Using dosdude1 tool I was able to install Mojave and install the continuity tool. Whats broken:
Everything else seems to work. Can continue from safari, messages work, shared clipboards also works. It would be great to get a proper update for Mojave as its literally the only significant upgrade to macOS in years.
@gt2416 - Awesome! 👏🏽👏🏽
Sent from my iPhone
On Jun 27, 2018, at 14:00, gt2416 notifications@github.com wrote:
I have a MacBook Pro 2011 which is NOT supported by mojave. I have an upgraded internal wifi card. Using dosdude1 tool I was able to install Mojave and install the continuity tool. Whats broken:
Can no longer initiate hotspot from phone. It fails to activate every time. Insert from iPad/iPhone or continuity camera does not work. Error says "Take Photos" service cannot be used. Although it looks to try and can see my device. Facetime app fails to initiate calls from iPhone unless its a facetime call. Error says make sure iphone is using same iCloud account. Everything else seems to work. Can continue from safari, messages work. It would be great to get a proper update for Mojave as its literally the only significant upgrade to macOS in years.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Just some updates
Any body else want to try it with Mojave ? The public beta is actually pretty stable. I've switched to it completely on my mac.
@gt2416 what is this “Camera Continuity” feature that’s completely missed me by?
Sent from my iPhone 5S
On 27 Jun 2018, at 18:01, gt2416 notifications@github.com wrote:
Just some updates
Continuity camera suddenly started working. (Did not reboot or anything) Tested with an iPad. Not being able to call phone numbers MAYBE because my iPhone is not running ios 12 and I will not update it till the official release. Any body else want to try it with Mojave ? The public beta is actually pretty stable. I've switched to it completely on my mac.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
If I'm not mistaken, a Mac using "Camera Continuity" is capable of "seeing" and capturing what its paired iPhone "sees".
@gt2416: It's a long time since I last checked this out, but I think that, back when I updated to Sierra 10.12, my hotspot wouldn't work even after running CAT. I had to manually edit one or two SIP-protected files for it to work. I think, somewhere in this forum, I mentioned the steps I undertook. I am almost certain that if you follow my old instructions, you'll succeed.
Could you point be to that info if you have it please ? I've searched for a while but can't find it.
No, sorry. I would have to look for it myself. I guess it will be among CAT issues relative to Sierra or High Sierra.
EDIT: I found it! Have a look at what I said in https://github.com/dokterdok/Continuity-Activation-Tool/issues/397 and the links provided therein. Good luck.
Thank you SO much for the link ! I actually did that already, it was part of my install notes. Guess I had problems on High Sierra or something so I had to do it. Thanks for the suggestion tho ! Airdrop and stuff works, its really only those specific things I mentioned that dont work. Continuity definitely works and functions well except for those things. The personal hotpot cant start but it can see my phone.
I have a MacBook Pro 5,5 running mojave through dosdude1 patch tool. I wonder if cat will work, I got a asus bluetooth 4.0 dongle. Thanks!
I have macbook air 4.2. Only Airdrop works for me on Mojave (On the last build of High Sierra all works well). Is there anybody who have old Handoff working?
I have a MacMini5,1 from 2011 which is NOT supported by mojave and using dosdude1 tool everything works perfect (except gray transparency glitch). I solved it with: "System Preferences" -> “Accessibility” -> “Display" -> select “Reduce transparency”.
As @gt2416 told before, there are a few continuity features don't work but all other things works perfect such as Airdrop or app switch.
App switch doesn't work for me (if you meant that in the picture below)... O'k. Will try to fix. Thanks.
I can see iMessages and Mail from my iphone in my macmini.
Hi :) So, if I understand the posts here correctly, it works to patch Continuity on a patched (dosdude1 tool) Mojave Mac? I thought there might be issues with the bluetooth kexts as the dosdude1 Mojave patcher might altered the kexts and CAT will alter them again, breaking Mojave ^^ If that’s not the case and sb can again confirm, I would love to patch my patched Mojave :D
Hi :) So, if I understand the posts here correctly, it works to patch Continuity on a patched (dosdude1 tool) Mojave Mac? I thought there might be issues with the bluetooth kexts as the dosdude1 Mojave patcher might altered the kexts and CAT will alter them again, breaking Mojave ^^ If that’s not the case and sb can again confirm, I would love to patch my patched Mojave :D
Yes, if you patch bluetooth again using dosdude1 patch app, your dosdude1-CAT patched bluetooth file will be broken and you should reinstall mojave. I did that on Saturday and I have to reinstall all again T_T Maybe dosdude should add CAT into his patched files to avoid this. Regards.
Thanks! Uhh that‘s bad luck:/ In the Macrumors thread, I already suggested to add a CAT patch to the list of available patches, but I received no answer...
BTW, do you know if one can disable the Dosdude1 patcher updates?
Wow! that's sounds bad. I don't know if I can disable patcher updates or a specific patch. The problem will be when apple release 10.14.1 version of mojave and we have to apply all patch again. I hope dosdude1 read your post at macrumors and add it to the list. Regards.
Same error for me.
Verifying Wi-Fi hardware... WARNING. An unknown/untested AirPort card using the 'BrcmNIC' kext is active. This tool can't fix this.
iMac 11.3, Mojave, Apple Broadcom BCM94360CD, GTX 765M AirPort Extreme (0x14E4, 0x111) Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2)
Working well on Mojave 10.14 (MacBook Pro A1278 Late 2011)
Got a MacBook Pro Early 2011 (MacBookPro8,1) running patched Mojave 10.14.1. I think I am going to order a BCM94331PCIEBT4CAX card to make everything work with my iPad Pro. Can someone please post instructions as to how to make everything work with the patched Mojave installation? It seems @glaurossi and @gt2416 got it working with similar MacBook Pro?
@GilDev
Step 1: Log out of iCloud
Step 2: Use the latest beta continuity Patcher, restart.
Step 3: Edit the file /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist
Look for the board number "94245B3640C91C81" and change the continuity flag to "true".
I did this through nano on terminal to make dealing with permissions easier.
Step 4: Run this command in terminal
sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-94245B3640C91C81/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360
Step 4: Restart
Step 5: Log into iCloud, restart. Test
Thanks a lot @gt2416! I have one reason to buy a new MacBook Pro, it would be nice if it had a better CPU. =) But I’ve just built an Hackintosh so this part is fine for now. I’ve found this card for 20 € so I think I’ll order it.
@GilDev
- I would 100% recommend getting the BCM94331PCIEBT4CAX card. Honestly I have no reason to buy a new Mac anymore. Really only wifi AC is missing.
- For the MacBookPro8,1 I believe the correct board number is "94245B3640C91C81" There are different models for 8,1 on Apple's website so not sure if yours is the same as mine. Either way it wont hurt even if its wrong.
Step 3: Edit the file
/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist
Look for the board number "94245B3640C91C81" and change the continuity flag to "true". I did this through nano on terminal to make dealing with permissions easier. Step 4: Run this command in terminalsudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-94245B3640C91C81/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360
Step 4: Restart Step 5: Log into iCloud, restart. Test
This method work like a charm on iMac mid 2010 Mojave and replaced AirPort card to Apple Broadcom BCM94360CD. No need to log out from iCloud. Also unlock with Apple Watch working.
In terminal get Your board number:
ioreg -l | grep "board-id" | awk -F\" '{print $4}'
My board number: Mac-F2238BAE - set flag to "true" in:
sudo /usr/libexec/PlistBuddy -c "Set:Mac-F2238BAE:ContinuitySupport true" "/System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist"
then do this 2 command in Terminal:
sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F2238BAE/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360
sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-F2238BAE/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcmNIC.kext/Contents/MacOS/AirPortBrcmNIC
Restart and all working OK.
Thanks for the tip.
Mojave on early 2011 MacBook Pro? Did I hear y'all correctly?
How?
Sent from my iPhone
On Nov 3, 2018, at 07:21, Grzegorz notifications@github.com wrote:
@GilDev
I would 100% recommend getting the BCM94331PCIEBT4CAX card. Honestly I have no reason to buy a new Mac anymore. Really only wifi AC is missing. For the MacBookPro8,1 I believe the correct board number is "94245B3640C91C81" There are different models for 8,1 on Apple's website so not sure if yours is the same as mine. Either way it wont hurt even if its wrong. Step 1: Log out of iCloud Step 2: Use the latest beta continuity Patcher, restart. Step 3: Edit the file /System/Library/Frameworks/IOBluetooth.framework/Versions/A/Resources/SystemParameters.plist Look for the board number "94245B3640C91C81" and change the continuity flag to "true". I did this through nano on terminal to make dealing with permissions easier. Step 4: Run this command in terminal sudo -E perl -pi -e "s/\Mac-00BE6ED71E35EB86/\Mac-94245B3640C91C81/" /System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/MacOS/AirPortBrcm4360 Step 4: Restart Step 5: Log into iCloud, restart. Test
This method work like a harm on iMac 2010 Mojave with replaced AirPort card to Apple Broadcom BCM94360CD. No need to log out from iCloud.
Thanks for the tip.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
@airmanchairman Just use dosdude1's patcher. It's easy and works great, just use dark theme (which I love) and maybe disable “Transparency effects” in Accessibility settings to avoid graphical glitches. Other than that, no differences from my Hackintosh!
Wow! I must’ve been living under a rock all this time! 😎
Thanks 🙏🏾
Sent from my iPhone 5S
On 3 Nov 2018, at 10:32, GilDev notifications@github.com wrote:
@airmanchairman Juste use dosdude1's patcher. It's easy and works great, just use dark theme (which I love) and maybe disable “Transparency effects” in Accessibility settings to avoid graphical glitches. Other than that, no differences from my Hackintosh!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
This method work like a charm on iMac mid 2010 Mojave and replaced AirPort card to Apple Broadcom BCM94360CD.
@grzegorz914 This method worked for me on MacBookAir 4,1 (mid 2011) in Mojave 10.14, even if the copy-paste function was too slow or absent, but it doesn't work anymore in Mojave 10.14.1. I've repeated the whole process (from CAT beta to everything suggested by GilDev and grzegorz914), with no result. Any suggestion?
Im updated Mojave from 10.14.1 to 10.14.2b1 and all working OK. I do not use CAT, I use only method what I previously described.
Im updated Mojave from 10.14.1 to 10.14.2b1 and all working OK. I do not use CAT, I use only method what I previously described.
Your reply to @GilDev began with "This method work like a charm", and since @GilDev's method at step 2 reads "Step 2: Use the latest beta continuity Patcher", I thought that you too used CAT. Anyway, now I don't know what to do…
Just for curiosity: why do the terminal commands use "Mac-00BE6ED71E35EB86" in the command line? That's the board-id for iMac 13,1.
OK, this was misunderstood, I start from step 3 because BCM94360CD is nativ supported under Mojave, no need to patch original .kext. I need only add my Board Number as supported to the original .kext.
The terminal command overwrite first supported Board Number with Yours Board Number. That’s all.
I start from step 3 because BCM94360CD is nativ supported under Mojave
I've re-installed Mojave 10.14.1 and done as you said, but it doesn't work. In System Information it says that Handoff is not supported and in System Preferences/General there is no checkbox for Handoff.
If I use CAT, System Information says that Handoff is supported and in System Preferences/General appears the checkbox for Handoff. In 10.14, after I used CAT and applied the changes suggested by @GilDev, Handoff and Continuity worked. In 10.14.1 I did the same exact thing, but it doesn't work. Well, I'll wait for the next update!
@erujp Are U set the flag to “true” for Your Board Number.?
@erujp Are U set the flag to “true” for Your Board Number.?
Yes, that's the only thing that made it work in 10.14. But this time it doesn't work. Anyway, that's not the first time that Continuity and Handoff work this way. In Sierra it worked fine, in High Sierra it didn't work. In Mojave 14.0 worked, and now it doesn't. I think there's a combination of different little things, that's why everyone has different results.
MacBook Pro 6,2 (Mid 2010, 15“) with external BT 4.0 USB dongle: Mojave 10.14.1
During patch process:
After patching and reboot:
AirDrop is working 👍 (No kernel panics or else…)
@gt2416 YOU ROCK! I followed your instructions closely and it does indeed work. This is a huge relief and I commend you for helping the community. Maybe a clean set of instructions should be posted for all those challenged.
With CAT only Airdrop works for me on Mojave (MacBook Air 4.2). With instructions of grzegorz914 handoff works well!!! ALL WORKS WELL (even "Get photo from iPhone/iPad"). THANK YOU!!!!!
@gt2416 @grzegorz914 Okay guys, I’ve just changed my WLAN card on my MacBookPro8,1 for the BCM94331PCIEBT4CAX I just received. I booted and WiFi and Bluetooth were working out of the box. System Informations (maybe it has another name in English?) says “Low-Energy Bluetooh: Yes” so everything seems to be in order. Sadly, I’ve followed @grzegorz914’s steps but using my own board number which was indeed the one given by @gt2416. Still no continuity, handoff or AirDrop. System Informations says Handoff is not supported. I tried logging out of iCloud then in again but nothing. To be clear, I haven’t used CAT but as WiFi & Bluetooth are working OOTB, maybe it’s not useful?
@grzegorz914
Glad I found this! I've been doing my best to modify my 13" MacBook Pro 8,1 (Early 2011) to continue lasting as long as I can. I've used CAT before and never fully worked for me. Updated my Mac to run Mojave using DosDude1's patcher and that turned out flawlessly (Running 10.14.1). Followed all your steps. This is what I did for Step 3 (After so much searching for an easy to use .plist editor): Downloaded BBEdit and made the changes there. Tested and found that the main continuity features I use worked. Airdrop - Works Handoff - Works
Thanks!
@Zayg94 It’s weird it doesn’t work with mine. I’ll try later with your plist editor. I only used a text editor, but it should still work.
@GilDev I initially tried with TextEdit but it didn't allow me to save any changes. BBEdit is the only one that let me.
Update: Universal Clipboard - Works Instant Hotspot - Works Continuity Camera - Works Auto Unlock - Apparently I need to have an AC wifi module. Seems there isn't one for the Early 2011 so I won't be able to enjoy that feature.
Well the file has definitely been updated, but still no AirDrop nor everything. Why won’t it work for me?!
@GilDev Do you use correct board number? Check: ioreg -l | grep "board-id" | awk -F\" '{print $4}'
Ps: I also used TextEdit (previously added permissions for folder and file)
May be it will help you
Yes it is the correct board number. I have used CAT yesterday in order to patch my MBP, and although I got a bunch of errors when installing the patch, I can now activate Handoff in System Settings and AirDrop works. But, Handoff, Continuity and everything still doesn’t work, only AirDrop… Now I tried uninstalling the patch from CAT app, in order to try to solve the errors it gave me, but it wont let me uninstall, instead it gives me this:
Restoring kexts... OK. No backups made with the tool were found, using the OS X Recovery Disk backups.
Mounting Recovery HD... OK
Reinstalling original Apple drivers... NOT OK
Applying correct permissions... OK
Updating kext caches... OK
Updating system caches... OK
Disabling any HCI switch behavior... OK
Verifying system kexts signatures... OK. 1 or more unsigned drivers were found. OS kext security protection won't be changed to prevent issues.
Patching ContinuitySupport... OK.
2018-11-22 01:04:00.423 osascript[2380:18442] isPrefsCreateCacheFromEnabledAndDefaultInputSources - can't find anything from GetInputSourceEnabledPrefs, use defaultASCIIKeyLayoutDict = <CFBasicHash 0x7fb3c8417430 [0x7fff9a1a98f0]>{type = mutable dict, count = 3,
entries =>
0 : <CFString 0x7fff9a217eb8 [0x7fff9a1a98f0]>{contents = "InputSourceKind"} = <CFString 0x7fff9a25d3f8 [0x7fff9a1a98f0]>{contents = "Keyboard Layout"}
1 : <CFString 0x7fff9a249538 [0x7fff9a1a98f0]>{contents = "KeyboardLayout ID"} = <CFNumber 0x812e17c757bd6b11 [0x7fff9a1a98f0]>{value = +1, type = kCFNumberSInt64Type}
9 : <CFString 0x7fff9a212bb8 [0x7fff9a1a98f0]>{contents = "KeyboardLayout Name"} = French
}
OK. Automatic continuity check disabled.
DONE. Please reboot now to complete the uninstallation.
And the patch stays activated…
Has anyone verified if machines theoretically non-Continuity compliant (unless they have the proper Bluetooth/Wi-Fi card) will continue to work in macOS 10.14 Mojave? Will the new Handoff/Continuity features work?