Update images and .md
This commit is contained in:
parent
b3e15df7a8
commit
353121ec45
9 changed files with 27 additions and 5 deletions
Binary file not shown.
Binary file not shown.
BIN
docs/docs/assets/troubleshooting/dualboot/Registry1.png
Executable file
BIN
docs/docs/assets/troubleshooting/dualboot/Registry1.png
Executable file
Binary file not shown.
After Width: | Height: | Size: 13 KiB |
BIN
docs/docs/assets/troubleshooting/dualboot/Registry2.png
Executable file
BIN
docs/docs/assets/troubleshooting/dualboot/Registry2.png
Executable file
Binary file not shown.
After Width: | Height: | Size: 8.3 KiB |
Binary file not shown.
BIN
docs/docs/assets/troubleshooting/dualboot/bt_addresses.png
Normal file
BIN
docs/docs/assets/troubleshooting/dualboot/bt_addresses.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 85 KiB |
Binary file not shown.
BIN
docs/docs/assets/troubleshooting/dualboot/plist.png
Normal file
BIN
docs/docs/assets/troubleshooting/dualboot/plist.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 190 KiB |
|
@ -82,19 +82,29 @@ The workaround for this limitation is as follows:
|
|||
1. First, boot into Windows and pair your device. This creates the registry entry we will need to edit later on.
|
||||
1. Reboot into macOS
|
||||
1. In macOS, clear the profile on your keyboard and pair with your computer.
|
||||
1. Once paired, old Option + Control + Shift and click on the bluetooth icon in your menubar. Take note of the "Address" of your computer's bluetooth device (`65-FD-3B-1A-DB-48` here), as well as the address of the connected device (`E6-24-54-08-BC-A3` here).
|
||||
1. Once paired, hold Option + Control + Shift and click on the bluetooth icon in your menubar. Take note of the "Address" of your computer's bluetooth device (`65-FD-3B-1A-DB-48` here), as well as the address of the connected device (`E6-24-54-08-BC-A3` here).
|
||||
|
||||
|  |
|
||||
| :--------------------------------------------------------------------------: |
|
||||
| Bluetooth Context Menu |
|
||||
|
||||
1. Now open the terminal app (Applications/Utilities/Terminal.app) and paste the following command and enter your root password.
|
||||
|
||||
#### macOS High Sierra (10.13) and newer
|
||||
**macOS High Sierra (10.13) and newer**
|
||||
```
|
||||
sudo defaults read /private/var/root/Library/Preferences/com.apple.bluetoothd.plist
|
||||
```
|
||||
#### macOS Sierra (10.12) and older
|
||||
**macOS Sierra (10.12) and older**
|
||||
```
|
||||
sudo defaults read /private/var/root/Library/Preferences/blued.plist
|
||||
```
|
||||
|
||||
This will print the contents of the bluetooth plist file containing the pairing keys for your bluetooth devices.
|
||||
|
||||
|  |
|
||||
| :--------------------------------------------------------------------------: |
|
||||
| Bluetooth .plist |
|
||||
|
||||
1. Look for the section that starts with `SMPDistributionKeys =`. Below this, find your host's bluetooth address (`65-FD-3B-1A-DB-48` in this example) and then look for the address of your keyboard (`6-24-54-08-BC-A3` in this example).
|
||||
1. Under your keyboard address, find the value labeled LocalLTK (in the screenshot above it is `0x8968239e350b2cb7df16d8f47c774e2c`). Copy this value into a text file that you can access from Windows, this is the value we will need to enter into the registry later on.
|
||||
1. Reboot into Windows
|
||||
|
@ -104,18 +114,30 @@ sudo defaults read /private/var/root/Library/Preferences/blued.plist
|
|||
1. Enter the following, one at a time:
|
||||
|
||||
```
|
||||
cd Desktop
|
||||
cd c:\Users\<username>\Desktop
|
||||
psexec -s -i regedit
|
||||
```
|
||||
|
||||
Regedit will launch. Be careful in here as certain registry edits can cause your system to become unstable or unbootable! Edit only the entry shown in this guide.
|
||||
1. Navigate in the registry to this key
|
||||
|
||||
```HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys\```
|
||||
```
|
||||
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys\
|
||||
```
|
||||
|
||||
1. Inside "Keys", select the address of your host bluetooth device. It should be the same as it was in macOS (`65-FD-3B-1A-DB-48` in this example).
|
||||
1. Below that, find the address that matches your keyboard's from macOS (`6-24-54-08-BC-A3` in this example).
|
||||
|
||||
|  |
|
||||
| :--------------------------------------------------------------------------: |
|
||||
| Registry Key |
|
||||
|
||||
1. Under that, there should be a registry entry called "LTK". Double click on this entry to modify it. Regedit will pop up a hex editing window. Delete the contents to start with a blank value. Refer to the LocalLTK value you saved from macOS and enter it into this dialog box, omitting the "0x" at the beginning. Regedit will automatically advance you through the hex pairs. When you're done the window should look something like this:
|
||||
|
||||
|  |
|
||||
| :--------------------------------------------------------------------------: |
|
||||
| Registry Key Editor |
|
||||
|
||||
1. Select OK, exit Regedit, and reboot into Windows.
|
||||
1. Once rebooted, turn bluetooth back on, and make sure your keyboard is on the same profile you had selected in macOS. Your keyboard should connect and start working!
|
||||
1. Finally reboot into macOS and verify that your keyboard still works on the same profile here as well.
|
||||
|
|
Loading…
Add table
Reference in a new issue