Jump to content
Denicio

Keep Bluetooth devices paired once between Mac/Windows

27 posts in this topic

Recommended Posts

Intro

 

You might have noticed that once you pair your Bluetooth devices in either Mac or Windows, you blatantly need to re-pair the same devices every time in order to utilize them. This is due to the fact, that, despite pairing these devices on the same BT adapter, each OS stores the pairing keys uniquely. My guide is a step-by-step procedure to remedy this problem. If you would like to learn more about the internals of the solution itself, please refer to the following:

 

- The original thread about fixing this problem can be found here by camoguy. Awesome work!

- The original code for automating the fix is hosted here. Congratulations on your work, I was able to learn Python because of you and your interesting project.

 

Procedure

 

A) Boot into Windows, open Bluetooth preferences.

B)Pair all Bluetooth devices that you plan on using on both Mac/Windows. You need to pair on Windows first because certain drivers are installed while you pair new devices.

 

r4loaEM.png

 

C) Restart into macOS, open your Bluetooth panel.

D) Pair once again the same Bluetooth devices. If you have trouble pairing, lookup how to enable Discovery Mode on your devices.

 

nRi3c8m.png

 

E) Open Terminal, run chmod +x ~/Desktop/bt.py (this file is attached on this post).

F) Run ~/Desktop/bt.py

 

U51pZmD.png

 

G) On you desktop you will find BTFix/BTFix.reg, copy this file on your Windows disk or an external USB disk.

 

uYVwaad.png

 

H) Reboot into Windows.

I) Download PSTools and extract it on your Downloads folder (or any other folder).

J) Run cmd.exe as Administrator, navigate to your PSTools folder.

K) Type psexec -s -i C:\Windows\regedit.exe

 

CUwUkhQ.png

 

L) Regedit is now open. Click File -> Import, and select your previously generated BTFix.reg file.

 

YNbPSQi.png

 

M) Restart Windows.

N) Check that all your Bluetooth devices connect successfully.

 

jcZzFaN.png

 

Notes

 

Bluetooth 4.0 devices are not covered with this version. As soon as I get a Bluetooth 4.0 capable device in order to experiment, I will update this thread with findings. Waiting for your input too!

bt (El Capitan, Sierra).zip

bt (High Sierra).zip

Share this post


Link to post
Share on other sites
Advertisement

Notes

 

Bluetooth 4.0 devices are not covered with this version. As soon as I get a Bluetooth 4.0 capable device in order to experiment, I will update this thread with findings. Waiting for your input too!

 

Thanks for your efforts (and the original guys).

So I have the Apple BCM943602CS wiFi-BT combo card. BT is 4.0. 

What would be different for BT 4.0 ?

Share this post


Link to post
Share on other sites

Thanks for your efforts (and the original guys).

So I have the Apple BCM943602CS wiFi-BT combo card. BT is 4.0. 

What would be different for BT 4.0 ?

The difference would be if the devices you connect to it are BT 4.0 capable. Give it a try, most of your devices will work with this method.

Share this post


Link to post
Share on other sites

The difference would be if the devices you connect to it are BT 4.0 capable. Give it a try, most of your devices will work with this method.

OK. Thanks. I figured it out without any mods.

This is what I had to do to get the my Apple Magic Keyboard and Apple wireless mouse (non-chargeable) to work in Win10 & macOS 10.13:

1. Boot macOS and disconnect & remove the kbd & mouse from bluetooth (used a wired kbd & mouse temporarily)

2. reboot to Win10 and install latest bootcamp drivers to Bluetooth, WiFi, wireless kbd & wireless mouse.

3. While in WIN10, add the kbd & mouse. Worked perfect (mouse touch scroll & volume keys displays up/down on screen just like macOS)

4. reboot to macOS and add kbd & mouse via System Pref->bluetooth and they both work perfect.

5. reboot to WIN10 and kbd & mouse still work.

 

I check the link keys in both WIN10 & macOS and they are both different for each kbd & mouse. So don't know how it's working.

Maybe, the latest bootcamp drivers are tolerant of dual booting.

 

My only problem with BCM943602CS is that the Apple kbd & Apple mouse do not work during cold boot & restarts to access the BIOS & Clover.

I have Gigabyte Z77X-UP5 motherboard. It's a real pain when dual booting as I have to have another keyboard handy.

Share this post


Link to post
Share on other sites

OK. Thanks. I figured it out without any mods.

This is what I had to do to get the my Apple Magic Keyboard and Apple wireless mouse (non-chargeable) to work in Win10 & macOS 10.13:

1. Boot macOS and disconnect & remove the kbd & mouse from bluetooth (used a wired kbd & mouse temporarily)

2. reboot to Win10 and install latest bootcamp drivers to Bluetooth, WiFi, wireless kbd & wireless mouse.

3. While in WIN10, add the kbd & mouse. Worked perfect (mouse touch scroll & volume keys displays up/down on screen just like macOS)

4. reboot to macOS and add kbd & mouse via System Pref->bluetooth and they both work perfect.

5. reboot to WIN10 and kbd & mouse still work.

 

I check the link keys in both WIN10 & macOS and they are both different for each kbd & mouse. So don't know how it's working.

Maybe, the latest bootcamp drivers are tolerant of dual booting.

 

My only problem with BCM943602CS is that the Apple kbd & Apple mouse do not work during cold boot & restarts to access the BIOS & Clover.

I have Gigabyte Z77X-UP5 motherboard. It's a real pain when dual booting as I have to have another keyboard handy.

Way to go...! Actually, that's what I do, I keep a small USB keyboard handy for these type of situations :)

Share this post


Link to post
Share on other sites

Way to go...! Actually, that's what I do, I keep a small USB keyboard handy for these type of situations :)

 

Just found a fix.

Gigabyte had released a beta BIOS F13a a long time ago but I never used it at the time as I had some issues overclocking it to 4.8Ghz so have been running F12j-Mod9.

I just installed the F13a BIOS and both apple kbd & mouse are working in BIOS and hence Clover.

 

So looks like it's a BIOS issue.

 

Apple kbd & mouse continue to work with both Windows and macOS without any regedits with the F13a BIOS.

Share this post


Link to post
Share on other sites

Just found a fix.

Gigabyte had released a beta BIOS F13a a long time ago but I never used it at the time as I had some issues overclocking it to 4.8Ghz so have been running F12j-Mod9.

I just installed the F13a BIOS and both apple kbd & mouse are working in BIOS and hence Clover.

 

So looks like it's a BIOS issue.

 

Apple kbd & mouse continue to work with both Windows and macOS without any regedits with the F13a BIOS.

Amazing, next time I will opt for a Gigabyte (currently have ASRock).

Thanks, man. I finally find the solution in High Sierra. 

Glad I could be of help.

Share this post


Link to post
Share on other sites

Okay so i followed this guide and its amazing what you have done. But for some reason my keyboard connects but doesnt do anything in windows HOWEVER, if i turn my keyboard off and i check the registry the Key is there but there is nothing is in the Key if that  make sense (key in this case meaning folder in registry). But when i import the key file it shows up. Please help i really dont like using this amazon basics keyboard lmao.


After i add the reg key it connects to an unknown bluetooth device then goes to my full name ______ 's Keyboard and it says connected but i cant use it and after like 2 min it goes from connected to paired.

Share this post


Link to post
Share on other sites

Okay so i followed this guide and its amazing what you have done. But for some reason my keyboard connects but doesnt do anything in windows HOWEVER, if i turn my keyboard off and i check the registry the Key is there but there is nothing is in the Key if that  make sense (key in this case meaning folder in registry). But when i import the key file it shows up. Please help i really dont like using this amazon basics keyboard lmao.

After i add the reg key it connects to an unknown bluetooth device then goes to my full name ______ 's Keyboard and it says connected but i cant use it and after like 2 min it goes from connected to paired.

 

Try to attach on a reply the output files from the patch, I will take a look.

Share this post


Link to post
Share on other sites

Try to attach on a reply the output files from the patch, I will take a look.

There sorry for bothering thanks for taking a look. Also i forgot to add when windows says unknown bluetooth device it detects its a keyboard then goes to __________'s Keyboard connected then it goes to paired i forgot to mention it detects its a keyboard. Also while it says connected i cant type anything its weird. but it works perfectly in OSX it auto pairs and everything. Im using a hackintosh if that makes a difference 

BTFix.zip

Share this post


Link to post
Share on other sites

Were you able to find anything?

I checked your generated reg file for Windows and everything seems OK. Did you follow the steps sequentially as they appear on the guide?

Share this post


Link to post
Share on other sites

Im going to try to reinstall windows any version of windows you recommend? For me i dont care tbh as long as i have a windows partition lol.

I personally install Windows 10 LTSB. It's a minimal version of Windows 10 that doesn't include any of the extras like Store, Maps, Mail apps etc. You just install yourself whatever you need.

Share this post


Link to post
Share on other sites

So i found what my issue was you need to install the Regisry key before you install the Bootcamp drivers if you already installed the drivers right click on the .MSI file you used to install it and click uninstall and install the registry key and once it connects automatically once then install the bootcamp drivers then everything works I dont know if this works for others but for me this is what worked

Share this post


Link to post
Share on other sites

I am not sure what how I did it. But following this guide and the others, I have bluetooth working in BIOS on the z270n gaming 5 along with CLOVER macOS High Sierra and Windows 10. Amazing. I did replace the wifi bt card with a legit Apple one and adapter. Thanks!

Share this post


Link to post
Share on other sites

I am not sure what how I did it. But following this guide and the others, I have bluetooth working in BIOS on the z270n gaming 5 along with CLOVER macOS High Sierra and Windows 10. Amazing. I did replace the wifi bt card with a legit Apple one and adapter. Thanks!

Nice going! Glad it worked for you.

Share this post


Link to post
Share on other sites

Great Work! But can not for  Bluetooth 4.0 LE/Smart. 

I'll try to pair my MiMouse (it's a Bluetooth 4.0 LE/Smart mouse) on windows 10 and import the keys on the Ubuntu & MacOS side, For day and day I  solved this problem!

You can use  Wireshark to capture & analysis Bluetooth data packets on each platform,now you can finder the answer.

For my platform is Windows 10+Ubuntu16.04+MacOS HighSierria。 For Bluetooth 4.0 LE/Smart mouse does not need  link key, The IRK LTK RAND EDIV Address Value data need. For different platforms the Value data may need convert。My paired keys config each platform list in below,You can use it as an example.

 

Config files:

==========================================================================================================================
Windows 10 Registry
==========================================================================================================================

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys\c8ff2840fec4]
"18dc56001a6f"=hex:9f,63,4d,7f,83,58,a9,15,21,d9,07,85,e9,ef,31,48

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys\c8ff2840fec4\ce995d228b53]
"LTK"=hex:5e,75,65,20,d4,27,da,d5,b8,fc,ec,b9,2d,60,e4,52
"KeyLength"=dword:00000000
"ERand"=hex(b):b2,41,8f,ac,43,e6,67,d2
"EDIV"=dword:000058ba
"IRK"=hex:b2,af,08,39,62,d8,99,69,49,ed,d9,6a,f8,ad,e7,4c
"Address"=hex(b):53,8b,22,5d,99,ce,00,00
"AddressType"=dword:00000001
"AuthReq"=dword:00000001

=============================================================================================================================
Linux /var/lib/blutooth/XX:XX:XX:XX:XX/XX:XX:XX:XX:XX/info
=============================================================================================================================
[General]
Name=MiMouse
Appearance=0x03c2
AddressType=static
SupportedTechnologies=LE;
Trusted=true
Blocked=false
Services=00001530-1212-efde-1523-785feabcd123;00001800-0000-1000-8000-00805f9b34fb;00001801-0000-1000-8000-00805f9b34fb;0000180a-0000-1000-8000-00805f9b34fb;0000180f-0000-1000-8000-00805f9b34fb;00001812-0000-1000-8000-00805f9b34fb;

[DeviceID]
Source=2
Vendor=10007
Product=64
Version=35

[IdentityResolvingKey]
Key=B2AF083962D8996949EDD96AF8ADE74C

[LongTermKey]
Key=5E756520D427DAD5B8FCECB92D60E452
Authenticated=0
EncSize=16
EDiv=22714
Rand=15161339848898331058

[ConnectionParameters]
MinInterval=6
MaxInterval=9
Latency=100
Timeout=600

=======================================================================================================
MacOS com.apple.bluetoothd.plist
=======================================================================================================
{
    "SMPCloudLocalPrivateKey" = <4edf5681 31d2e5e2 0fbe80a2 7d28bb57 ae6f395b 932dbad7 60bbd490 1464348e 56da0fff b0777a3a f96c4148 eed126c5 3a9f8c9e 36820b25 e2d6766b 719bd79c 20fe862d df67e763 b1a544f2 75394731 4508c726 d9cea622 e17fdf79 e0eeb082>;
    "MagicCloudPairingMasterHint" = <d4b84bee f7db21e8 9cffc1b7 8b6759d9>;
    SMPDistributionKeys = {
        "c8-ff-28-40-fe-c4" = {
            "ce-99-5d-22-8b-53" = {
                AddressType = 1;
                MITMProtection = NO;
                OriginalAddressType = 1;
                LTKLength = <10>;
                RAND = <b2418fac 43e667d2>;
                IRK = <4ce7adf8 6ad9ed49 6999d862 3908afb2>;
                Address = <ce995d22 8b53>;
                EDIV = <ba58>;
                LTK = <5e756520 d427dad5 b8fcecb9 2d60e452>;
            };
        };
    };
    SMPCloudLocalNonce = <d40e7747 ba393789 0da2933c 2ff11b17>;
    LinkKeys = {
        "c8-ff-28-40-fe-c4" = {
            "4c-74-bf-64-06-f3" = <b05de895 fe4aeb5b c2dba041 547bcc7b>;
            "d8-9a-34-29-b9-85" = <dd8e162b bc6676af f6590315 f0e48a31>;
            "30-22-23-01-e8-1f" = <56dd3519 d1519956 eb6ff5f3 c2bdc2f1>;
            "18-dc-56-00-1a-6f" = <a4d18428 e04d25a6 a5e236c7 53255653>;
        };
    };
    "MagicCloudPairingMasterKey" = <2d6445ca aaafa3c9 efa77256 a7e75dc9>;
    "SMPCloudLocalPublicKey" = <4edf5681 31d2e5e2 0fbe80a2 7d28bb57 ae6f395b 932dbad7 60bbd490 1464348e 56da0fff b0777a3a f96c4148 eed126c5 3a9f8c9e 36820b25 e2d6766b 719bd79c>;
}
 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.1_18B75
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
       
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
       
      InstallInfo.plist_edited_10.14.1.zip
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.
       



      3.  Quit DU and choose Macintosh HD to install El Capitan on.
       

      4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…
       

      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
       


      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
       


      7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By unixb0y
      Bluetooth + AirDrop + Apple Watch "Auto Unlock" + Continuity / Handoff
      BCM20702 / TP-Link T9E (AC1900)
       
      I have a little update on getting BCM20702 running in Mojave:
       
      Without kext files, nothing worked "OOB" with my USB dongle. So I got "BrcmFirmwareStore" and "BrcmPatchRAM2" from RehabMan.
      I tried putting the kext files in /L/E , didn't work so I tried /S/L/E. * While that didn't work at first, I then tried to refresh the kext cache; the files didn't show up in kextstat.
      I used this command:
      sudo kextcache -invalidate / which told me 2 error messages: BrcmFirmwareStore and BrcmPatchRAM2 had the wrong permissions. This is fixed like so:
      sudo chown -R 0:0 /System/Library/Extensions/BrcmPatchRAM2.kext/ sudo chmod -R 755 /System/Library/Extensions/BrcmPatchRAM2.kext/ sudo chown -R 0:0 /System/Library/Extensions/BrcmFirmwareRepo.kext/ sudo chmod -R 755 /System/Library/Extensions/BrcmFirmwareRepo.kext/ Reboot and be happy! 
      Both the actual Bluetooth entry in System Preferences, that was missing before as well as an entry in System Report > Bluetooth finally appeared!
      I have a TP-Link Archer T9E WiFi card and now in conjunction, AirDrop does work like a charm! 
      Cheers, Dave 
       
      * EDIT:
      RehabMan replied to me on GitHub and it's not recommended to use /S/L/E and you should let that folder remain reserved for Apple original kext files. So I tried putting the files (with the correct permissions) back into /Library/Extensions and Bluetooth and AirDrop both still work fine!
      So I would recommend to put the files either into EFI/EFI/CLOVER/kexts/Other or - like me - into /Library/Extensions and after (or before) copying the two kext files, set the permissions like shown above for both files with chown and chmod.
       
      EDIT2: 
      I totally forgot to mention that even unlock via Apple Watch works! I assumed it would not work, until the "iMac" itself saw my Watch and kindly asked if I wanted to activate it  I immediately turned the feature on and it's working like a charm!
      What also perfectly works is Handoff. It's a feature that I never found really useful, especially between iOS and Mac, however when I have a Safari window open on my iPhone, the Hackintosh shows me the handoff Safari icon in the App switcher as well as in the dock (only tested Safari for now) and it behaves just like on my MacBook Pro!
      Universal Clipboard is also working as well as SMS / MMS.
      I couldn't test "Cellular Calls" and the "Continuity Camera" as I don't have a second phone and it's quite late here right now for calling someone on the telephone and I don't have any iOS 12 devices either. The "Instant Hotspot" did not work, but I think that anybody going the TP-Link T9E + BCM20702 way is building a PC that is permanently attached to WLAN or even LAN (Ethernet), so that's not an issue. I think laptop Hackintoshers should just use a MacBook WiFi card as they probably already have the connector etc. etc. (no adapter or Motherboard-dependent solutions needed).
    • By DarkHarthur
      DH67CL
      R7 250
      2 discos duros
      En el 1: Windows 10 y una partición de datos
      En el 2: High Sierra y una particion de datos
       
      Hola, mi problema es el siguiente Clover ya no me muestra EFI Windows; Tenia todo funcionando bien con High Sierra 10.13.6, quise actualizar a Mojave y como tuve muchos problemas decidí volver a High Sierra con el disco duro USB en el que había hecho una copia con Carbon Copy;
      La situacion es algo así, en la carpeta EFI si dejo la carpeta Microsoft, al encender la PC entra directo a Windows, si elimino la carpeta Microsoft si entra con Clover pero no aparece la entrada EFI Windows, ya active legacy en Clover Configurator pero solo me aparecen otras entradas de Windows pero no EFI, todo esto desde el disco duro supuestamente restaurado a como lo tenia antes.
      Si entro con el disco duro USB que tiene la copia que había hecho, me aparecen todas las opciones.
      Si conecto un pendrive tampoco me aparece la opción EFI Windows. 
      Probablemente paso después de desconectar el disco duro de Windows, pero recuerdo que me seguía apareciendo EFI Windows después de haberlo desconectado. Saludos
    • By dan_oninho
      Fala pessoal
       
      Tenho as seguintes configurações:
       
      CPU: FX 8300
      Mobo: M5A78BL-MPlus/usb3
      Memoria: 8GB
      Placa de Video: GT 1030

      Quero fazer hackintosh nele, mas não sei qual versão de SO melhor para instalar e também sei que AMD não vai sem modificação, então preciso de uma grande ajuda vinda de vocês
       
      Obs: Vou mudar depois do GT 1030 pra GTX 770
      Obs: Tenho só 1 HD, queria fazer um dualboot com Windows, sei que vai dar trabalho, mas seria possivel?

       
×