Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
@dosdude1 after recent bluetooth update (via patch updater) can't connect to bluetooth speakers. Although Apple wireless keyboard works fine. It tries to connect to speakers, connects for a couple of seconds (a led light on speakers confirms the connection, but without sound) and immediately disconnects. Is there a way to fix it or revert back to previous bluetooth driver?
 
Last edited:
@dosdude1 MacBookPro4,2 after recent bluetooth update (via pacth updater) can't connect to bluetooth speakers. Although Apple wireless keyboard works fine. It tries to connect to speakers, connects for a couple of seconds (a led light on speakers confirms the connection, but without sound) and immediately disconnects. Is there a way to fix it or revert back to previous bluetooth driver?

You should use these two kext IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext taking from a Mojave clean installation or late HighSierra, using those inside the USB Installer I guess won't work cause they are smaller in size so presumably can't cover all the BT devices.

In case you don't have, I attach both the Bluetooth kexts from a clean Mojave GoldenMaster, replace the ones inside your Mojave /System/Library/Extensions/ after you have to launch Terminal and type:

sudo chmod -R 755 /S*/L*/E*
sudo chown -R 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot
 

Attachments

  • IOBluetooth Mojave GM.zip
    2.5 MB · Views: 450
Last edited:
Yes, mostly because the macOS recoveries do a check through Internet on machine before allow to download the Installer (again) into the disk, maybe this check is patchable too, but then would remain a non-patched Installer with dangerous firmware.pkg inside (and without Post-Install), so both the HFS and APFS Recovery are just for Utilities fun, anyway from a Recovery Terminal can do a lot of things, even a partial manual patching of Mojave.
Good point. Didn’t think of that particular aspect. I always keep a full installer partition on my machine in case of problems.
 
You should use these two kext IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext taking from a Mojave clean installation or late HighSierra, using those inside the USB Installer I guess won't work cause they are smaller in size so presumably can't cover all the BT devices.

In case you don't have, I attach both the Bluetooth kexts from a clean Mojave GoldenMaster, replace the ones inside your Mojave /System/Library/Extensions/ after you have to launch Terminal and type:

sudo chmod -R 755 /S*/L*/E*
sudo chown -R 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot
Thanks a lot for your help, friend. I saw the first version of your reply and already used kexts from USB Installer disk. It seems to be working fine, everything is back to normal.
I also noticed that for some reason bluetooth kexts on USB Installer are version 6.0.8 while the ones installed on HD were 6.0.7.
 
Thanks a lot for your help, friend. I saw the first version of your reply and already used kexts from USB Installer disk. It seems to be working fine, everything is back to normal.
I also noticed that for some reason bluetooth kexts on USB Installer are version 6.0.8 while the ones installed on HD were 6.0.7.

You're welcome, no matter the version, on any USB macOS Installer you can find some Extensions and Framework but they are fork-ed version of a clean installation, even if in emergency they work sometimes, but I'd say they are "incomplete", however if they are working for you, can keep them quietly.
 
Those who wish to use Wi-Fi on their patched macOS Mojave installers, please read the above post.

What exactly does this fix? Wifi has always been fine when patching using @dosdude1's tool.
[doublepost=1538839374][/doublepost]
You should use these two kext IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext taking from a Mojave clean installation or late HighSierra, using those inside the USB Installer I guess won't work cause they are smaller in size so presumably can't cover all the BT devices.

In case you don't have, I attach both the Bluetooth kexts from a clean Mojave GoldenMaster, replace the ones inside your Mojave /System/Library/Extensions/ after you have to launch Terminal and type:

sudo chmod -R 755 /S*/L*/E*
sudo chown -R 0:0 /S*/L*/E*
sudo kextcache -i /
sudo reboot

Not that it matters really, but will this prompt eventually for an updated bluetooth patch? Thanks.
 
What exactly does this fix? Wifi has always been fine when patching using @dosdude1's tool.
[doublepost=1538839374][/doublepost]

Not that it matters really, but will this prompt eventually for an updated bluetooth patch? Thanks.
It allows you to use WiFi on the installer drive. I don't have devices to test so I don't know the details but there are issues with WiFi on the installer drives. Anyone who tests those files. Please lemme know if it works.
 
Had anyone tried this on an Xserve yet? I will be trying it on my 2,1 once I get a compatible video card (I’m eyeing a quadro k5000 but if anyone knows of a cheaper one that’ll work, please let me know)
 
  • Like
Reactions: TimothyR734
Had anyone tried this on an Xserve yet? I will be trying it on my 2,1 once I get a compatible video card (I’m eyeing a quadro k5000 but if anyone knows of a cheaper one that’ll work, please let me know)
GTX 680 is what most people go with. Though every Kepler based card should work without boot screen.
[doublepost=1538844032][/doublepost]
 
Hello: Somebody test this?

Oh my fault, didn't know sorry.

@arqueox try these steps they 100% work this time to increase from stock 512 MB to 1536 MB VRAM:

cd /S*/L*/Ext*/AppleIntelSNBGraphicsFB.kext/C*/M*

sudo cp AppleIntelSNBGraphicsFB AppleIntelSNBGraphicsFB.backup

sudo perl -pi -e 's|\xC7\x45\xD0\x00\x00\x00\x20|\xC7\x45\xD0\x00\x00\x00\x60|g' AppleIntelSNBGraphicsFB

sudo touch /S*/L*/Extensions


edit:
thanks to @arqueox for having tested the Info.plist
before reboot/restart you have to edit this file:

/System/Library/Extensions/AppleIntelHD3000Graphics.kext/Contents/Info.plist

Adding after these strings,
this part:

<key>VRAMMethod</key>
<integer>0</integer>
<key>VRAMOverride</key>
<integer>0</integer>

<key>VRAMSize</key>
<integer>1536</integer>

after edited the plist from Terminal type:

sudo chown -R 0:0 /System/Library/Extensions && sudo chmod -R 755 /System/Library/Extensions

sudo kextcache -i /

sudo reboot
 
  • Like
Reactions: TimothyR734
  • Like
Reactions: TimothyR734
Dear All:

Im very happy with it. I don not want install Majave yet becase use VectorWorks 2017 that is not supported by 10.14.
My MacBook Pro is a 17" early 2011, and its AMD GPU have failed three times. Then disconnected at all by software.

My choice was add more shared VRAM using your advice!! and WORKS!!!!

Thanks a lot to all who help me.

Regards




Yes, it works, instead of manual patching, you can use this: IntelHD3000 already patched VRAM combinations for Mojave
[doublepost=1538853153][/doublepost]

Yes, I guess like for Wifi there can't be an universal BT kext that covers all the legacy machines.
 

Attachments

  • Screenshot 2018-10-06 16.22.02.png
    Screenshot 2018-10-06 16.22.02.png
    51.4 KB · Views: 346
I tried installing 10.14.1 beta 2 on Wednesday. Everytime I tried the computer failed to boot afterwards, even after applying patches. I kept reinstalling and trying again but to no avail. Has anyone successfully gotten either version of 10.14.1 working?
 
  • Like
Reactions: TimothyR734
I do not really this in a clear way. But I prefer maintain my Mac in High Sierra for the compatibility with 3th party software.

Unfortunately, VectorWorks 2017 fail with the VRAM patch.

Try to make a render with Open GL and freeze


I tried installing 10.14.1 beta 2 on Wednesday. Everytime I tried the computer failed to boot afterwards, even after applying patches. I kept reinstalling and trying again but to no avail. Has anyone successfully gotten either version of 10.14.1 working?
 
  • Like
Reactions: TimothyR734
I do not really this in a clear way. But I prefer maintain my Mac in High Sierra for the compatibility with 3th party software.

Unfortunately, VectorWorks 2017 fail with the VRAM patch.

Try to make a render with Open GL and freeze

To use this software VectorWorks 2017 in rendering you need a powerful high end video card, IntelHD3000 is very inapt, probably your previous AMD failed for that reason too, however regarding IntelHD3000 VRAM you can try these pre-patched files they work also for HighSierra: IntelHD3000 already patched VRAM combinations for Mojave and HighSierra
 
  • Like
Reactions: TimothyR734
It allows you to use WiFi on the installer drive. I don't have devices to test so I don't know the details but there are issues with WiFi on the installer drives. Anyone who tests those files. Please lemme know if it works.
OK, by 'installer drive' I presume you mean the drive on which macOS Mojave is installed? I will try it out on my MBP4,1 that, I mentioned a while ago, needs a restart (OFF-ON) of the WiFi if the laptop goes to sleep for more than 3 hours. Will give a feedback when I have so done.
 
  • Like
Reactions: TimothyR734
OK, by 'installer drive' I presume you mean the drive on which macOS Mojave is installed? I will try it out on my MBP4,1 that, I mentioned a while ago, needs a restart (OFF-ON) of the WiFi if the laptop goes to sleep for more than 3 hours. Will give a feedback when I have so done.
I mean the drive you use to install macOS. The installer drive.
 
  • Like
Reactions: TimothyR734
Hello:
I patched my Integrated GPU and now works from 512 to 1536 Mb.
Using GFXCard Status 2.4.4i I set Integrated Only.

Then Open VectorWorks and all start Ok until change the view Model for example: to Front.

Then the screen produce only garbage and can't quits or restart. The mouse cursor is shown.

I will try again and if doesn't work will use the AMD card again.

Regards.



To use this software VectorWorks 2017 in rendering you need a powerful high end video card, IntelHD3000 is very inapt, probably your previous AMD failed for that reason too, however regarding IntelHD3000 VRAM you can try these pre-patched files they work also for HighSierra: IntelHD3000 already patched VRAM combinations for Mojave and HighSierra
 

Attachments

  • Screenshot 2018-10-06 19.00.13.png
    Screenshot 2018-10-06 19.00.13.png
    56.5 KB · Views: 334
  • Screenshot 2018-10-06 19.00.30.png
    Screenshot 2018-10-06 19.00.30.png
    38.6 KB · Views: 249
  • Like
Reactions: TimothyR734
One minor issue: Switching from the dGPU back to the integrated GPU does not appear to work. Gets stuck on a black screen. MacbookPro5,2
 
  • Like
Reactions: TimothyR734
Yes and Yes! I have a private github repo you can sign up for to follow the progress. Some have already joined. PM me for details. If you were capable enough to find the same HIToolbox byte, we can talk...;)
Thanks for your research on this issue! We are all waiting for new information and a patch of course)
 
Last edited:
  • Like
Reactions: TimothyR734
Successfully installed Mojave on my MacBook5,1. It seems to work better than High Sierra for me(putting aside a well known graphic anomalies). I will be watching this space before downloading any updates through software updates though. Thanks @dosdude1!
 
  • Like
Reactions: TimothyR734
Sorry for maybe "stupid question"....

If I disable on my Macbook Pro 8,2 15" AMD 6490 GPU Card by software.... that have effect in my two OS (High Sierra official & Mojave patched) or only in the OS where will execute the commands on Console mode and Recovery partition??

Regards
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.