macOS 12 Monterey on Unsupported Macs Thread

[RogueB]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

 

[rehkram]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

Amazing... it worked! TYVM

 

[steverae]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

Back to beta 4 I go to try this on my 13,2 iMac too

 

[steverae]

Back to beta 4 I go to try this on my 13,2 iMac too

It only blooming works

 

[steverae]

Back to beta 4 I go to try this on my 13,2 iMac too

It only blooming works

 

[alfon_sico]

Now with OCLP I can get Sidecar feature in Mac mini 2012 and iPad Pro 9,7.
I think that I can't do it before

 

[adam25255]

From my experience (MBP 9,2)

1. I run sudo killall -9 BlueTool bluetoothd once in Terminal. Enter password.
2. Then once again. Without putting in the password.
3. Toggle bluetooth from menubar. Wait a few moments. max 10 secs
4. All devices come back on automatically.

It always works after two times and toggling the button in menubar. At the same time, when I have sys prefs open, all devices appear automatically.

Can confirm, it works.(Trust Xani BT mouse)

 

[jonnyv34]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

On my 2012 Macbook air the command sudo killall -9 BlueTool bluetoothd works, even of not at first try.
This one doesn’t, it says no processes found.

 

[Vacusuck]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

Yeah, this works! But, you will need to re-enter this on a reboot each time. Not a big deal until it's actually fixed in a new beta at some point.

 

[TheRevenantFromDoom2]

Can we use the software updater normally after installing Monterey on unsupported hardware?

edit: ok yes it works fine

edit 2: Am I being paranoid or is my mac running hotter since I'm on Monterey?

 

[stiltskin]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

I wish I knew how you got this command line to work. I tried this twice in terminal copy/pasting 'sudo kill -9 $(pgrep bluetoothd) without quotes and I get:

usage: kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...

so then I try 'sudo killall -9 $(pgrep bluetoothd)' (knowing 'killall ...' executed in a previous posted method) and I get:

No matching processes were found

...and I try it again (up arrow) and I get:

usage: killall [-delmsqvz] [-help] [-I] [-u user] [-t tty] [-c cmd] [-SIGNAL] [cmd]...
At least one option or argument to specify processes must be given.

I'm on a [cMP] Mac Pro 5,1, running Monterey beta 3, using OpenCore Legacy Patcher v0.2.4
Mini-PCI: Genuine Apple WiFi 802.11ac & Bluetooth 4.2 Upgrade Kit Adapter *Mac Pro 4,1/5,1 (works in Big Sur)

By the way, I also tried the 'sudo killall -9 BlueTool bluetoothd' method over 50 times for a couple of days, even shutting the computer down overnight (as one user said their bluetooth worked afterward). None of these worked.

 

[StarPlayrX]

With my Lenovo Intel Wireless Card idea on a Mac Pro 3,1, on Monterey Beta 2 & 3, I was able to get the card working very quickly.

The USB from the PCIe card, is hooked up to my USB 2.0 Hub. So far that is the best place for it as my USB 2.0 Hub is seen right away. I am not good at soldering so I thought, get a Lenovo card with Intel Wireless, get its open intel wireless source bluetooth driver and grab the Bluetool fix up kext as instructed and Bam! Bluetooth worked on the first try.

This setup worked so well, I decided to remove my BCM card completely and reboots via B2 and B3 seem to be more stable/successful. B2 also got handoff to work. Do not have it on B3 yet.

And what is strange is the Card works perfectly on Monterey but the card does not get a MAC address on Big Sur. I may be able to get the Broadcom card to live on BigSur and the Lenovo Card to live on Monterey with USB Mapping as needed.

Card cost 13.00 on eBay

Lenovo 4XC0T22657 Wi-Fi/Bluetooth Combo Adapter | eBay

Find many great new & used options and get the best deals for Lenovo 4XC0T22657 Wi-Fi/Bluetooth Combo Adapter at the best online prices at eBay! Free shipping for many products!

www.ebay.com

9-pin to USB-A. The Lenovo card is a 11-pin, but the 9pin adapter works. A 5-pin should work but the wiring is all mixed up. I had a 5 pin and a 9 pin and could not get an 11 pin adapter, so just skip the 5 pin.

BAIRONG Black 9-Pin USB IDC Dupont Male Header to Single USB 2.0 Type A Male Cable 7.8 Inches

I got this idea from the Broadcom mods, but I felt this was easier and safer and can probably keep my Broadcom card as is for Big Sur and use this new card for Monterey.

the hardest part of this madness is the super tiny antenna prongs.

Kext's used with release links:
My Lenovo Intel Wireless combo 802.11ac/BT4LE card 13 USD off eBay works with just three kext's AirportItlwm.kext 2.0.0 (Monterey) and IntelBluetoothFirmware.kext v1.1.3, BlueToolFixup.kext v2.6.0.

p.s.

After getting Monterey working, I was able to get Big Sur 11.2.3 BT and WiFi working with the same card and meshing with a combination of Apple's drivers and the Open Source Firmware via Open Core. Really happy with the mod. I am getting a newer Lenovo WiFi/BT4.2 card for a 2009 4,1 that I am getting soon.

Releases · 1hbb/OpenIntelWireless-Factory

Open Intel Wireless Factory . Contribute to 1hbb/OpenIntelWireless-Factory development by creating an account on GitHub.

github.com

Releases · OpenIntelWireless/IntelBluetoothFirmware

Intel Bluetooth Kernel Extensions for macOS. Contribute to OpenIntelWireless/IntelBluetoothFirmware development by creating an account on GitHub.

github.com

Releases · acidanthera/BrcmPatchRAM

Contribute to acidanthera/BrcmPatchRAM development by creating an account on GitHub.

github.com

 

[JoeOIVOV]

Any trick to getting this Bluetooth card working for Monterey on 5,1?

This is 11.5.1:

Or should I order a different card?

I couldn't use BT on Monterey I setup with OCLP, worked as expected once I reverted.

 

[JoeOIVOV]

Hello,

****A Working fix for Bluetooth problems with Monterey beta 4***

(At least on my iMac 13,2, where all bluetooth functionality has been restored)

In terminal post the following command:

sudo kill -9 $(pgrep bluetoothd)

It is similar, but not equivalent to "similar" commands listed in other posts.

It immediately activated Bluetooth.

Note that I did run some commands before hand, which may have an influence on outcome, but not likely.

Hope this helps

Credit to coolaj86 (it is a single line from author's write-up on github (https://gist.github.com/nicolasembleton/afc19940da26716f8e90#gistcomment-2682108)

Going to try it. TY.

 

[StarPlayrX]

Going to try it. TY.

I had zero luck with commands. Zero luck with CSR and BCM bluetooth dongles. Good luck so far with a Lenovo Intel Wireless card combo PCIe card. Go figure. (Beta 4 is still elusive... will see how Beta 5 does)

 

[StarPlayrX]

Any trick to getting this Bluetooth card working for Monterey on 5,1?

This is 11.5.1:
View attachment 1815759

Or should I order a different card?

I couldn't use BT on Monterey I setup with OCLP, worked as expected once I reverted.

Apple wrote new drivers. Your card will work on Monterey Beta 1 but those drivers do not seem portable. the new thing is Bluetool and sometimes BluetoolFixup.kext will work on Beta 2 and later. I am currently experimenting with a Lenovo Intel Wireless 802.11ac/BT4.2 card and having good success thus far. The only real con is giving up a PCIe slot and running an internal cable out the back with a 9 pin USB adapter cable and hooking that up to a USB 2.0 hub out the back. Gonna try my USB 3.0 card and see if that works.

 

[JoeOIVOV]

Apple wrote new drivers. Your card will work on Monterey Beta 1 but those drivers do not seem portable. the new thing is Bluetool and sometimes BluetoolFixup.kext will work on Beta 2 and later. I am currently experimenting with a Lenovo Intel Wireless 802.11ac/BT4.2 card and having good success thus far. The only real con is giving up a PCIe slot and running an internal cable out the back with a 9 pin USB adapter cable and hooking that up to a USB 2.0 hub out the back. Gonna try my USB 3.0 card and see if that works.

Tried the BluetoolFixup.kext, It wouldn't boot anymore, just get stuck at the apple logo. Luckily I can boot into Windows and edit the config.plist and remove the entry and it boots just fine.

Nothings working yet, Bluetooth is dead for now.

 

[RogueB]

Can confirm, it works.(Trust Xani BT mouse)

There is a high probability that response to specific Blue Tooth control command is hardware (and possibly OS beta version) related. What works on one system may not be viable on another.

 

[RogueB]

I wish I knew how you got this command line to work. I tried this twice in terminal copy/pasting 'sudo kill -9 $(pgrep bluetoothd) without quotes and I get:

usage: kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...

so then I try 'sudo killall -9 $(pgrep bluetoothd)' (knowing 'killall ...' executed in a previous posted method) and I get:

No matching processes were found

...and I try it again (up arrow) and I get:

usage: killall [-delmsqvz] [-help] [-I] [-u user] [-t tty] [-c cmd] [-SIGNAL] [cmd]...
At least one option or argument to specify processes must be given.

I'm on a [cMP] Mac Pro 5,1, running Monterey beta 3, using OpenCore Legacy Patcher v0.2.4
Mini-PCI: Genuine Apple WiFi 802.11ac & Bluetooth 4.2 Upgrade Kit Adapter *Mac Pro 4,1/5,1 (works in Big Sur)

By the way, I also tried the 'sudo killall -9 BlueTool bluetoothd' method over 50 times for a couple of days, even shutting the computer down overnight (as one user said their bluetooth worked afterward). None of these worked.

This may by hardware related; what works on one system may fail to activate Bluetooth on another machine setup.
I actually just pasted command into terminal, provided required password, and it worked. Others with 13,2 iMacs had same success (see some preceding posts on this page). Consider checking Bluetooth card type in your system vs. Bluetooth module installed in iMac 13,2 (and similar.) Note, that there are no quotes around any portion of the command --> sudo kill -9 $(pgrep bluetoothd)

Possibly reinstall Monterey beta 4 (without data loss), and then run the command before using any other solutions(?)

 

[il-rollino]

edit 2: Am I being paranoid or is my mac running hotter since I'm on Monterey?

My Mac runs hotter too. Don’t know if it’s due to running beta OSes or because of its obsolete hardware.

 

[RogueB]

On my 2012 Macbook air the command sudo killall -9 BlueTool bluetoothd works, even of not at first try.
This one doesn’t, it says no processes found.

Hardware dependency is possible (Bluetooth module), however, try reinstalling Beta 4 and run this command before any other listed.

 

[Tockman]

Since some of Monterey betas my USB ports are defined incorrectly and therefore USB devices (e.g. WiFi adapter) work with 2.0 specification instead of supported 3.0. Is there any simple and effective way to correct this? Thank you all.

 

[Tronstar]

More sacrilege is you can install monterey on Late 2013 MacBook Pro without patcher and Without OPLP only with OpenCore on EFI ?

Plain OpenCore would suffice?
What did you add when you created the EFI without patcher?

I thought that OCLP stood for OpenCore Legacy Patcher.
I would prefer the manual method as well so do you want to share your approach?

 

[chris1111]

Plain OpenCore would suffice?
What did you add when you created the EFI without patcher?

I thought that OCLP stood for OpenCore Legacy Patcher.
I would prefer the manual method as well so do you want to share your approach?

I would not want to post answers which do not relate to the present subject I would rather create an independent subject and share my EFI file which contains OpenCore on this same subject, it will be more judicious.
For the moment what I can tell you is very simple, my EFI folder does not contain any kext and aml file injected by OpenCore and the SIP on my mac is fully activated.
I was going to create the subject after my return from vacations next week

 

[Tronstar]

I would not want to post answers which do not relate to the present subject I would rather create an independent subject and share my EFI file which contains OpenCore on this same subject, it will be more judicious.
For the moment what I can tell you is very simple, my EFI folder does not contain any kext and aml file injected by OpenCore and the SIP on my mac is fully activated.
I was going to create the subject after my return from vacations next week

Thanks, I'm looking forward to it! Well maybe it's still on topic here because mbpr late 2013 IS an unsupported Mac but I agree it could help a lot to start a new topic with this. I'm very curious because I'm planning to do the same and was wondering if a plain general OpenCore EFI partition would suffice. If it is, it must have something in it that makes the Monterey installer work.
When you create a new topic I will watch it and share my findings or results as well.
Enjoy the vacation!