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.
Forgive me guys!

I didn't notice the following phrase of the tutorial.

Note: Only perform steps 5 and 6 if you intend to do a clean install. Otherwise, you can simply skip these steps and install to your volume containg a previous version of OS X, and it'll do an in-place upgrade.
 
I had that distributed via Patch Updater, but it caused Bluetooth to stop working completely on some systems (that had working Bluetooth with Mojave to begin with). So I'm not sure what to do. It's not limited to specific machines either, in fact it seems to be completely random. For example, when I had initially pushed that patch, some MacBookPro8,1 users reported that it fixed their issue, while others reported that it made Bluetooth stop working completely. This is the same with all the machines (iMacs, MacBook Airs, Mac Minis, etc); some users said it worked on their system, others said it broke Bluetooth on the exact same system. I have no idea how to reliably distribute this patch.
First post here but have been following Dosdude1’s threads on High Sierra and now Mojave to get my venerable Mac up with the latest OS. Using a Mac Pro 3.1 with evga GTX 680 and an updated WiFi/BT4 combined internal card so have had Hand Off and Continuity since El Capitan. HS went without a hitch. Mojave works very well except for BT and I suspect my BT4.0 card upgrade may be the problem. Got it fully working in 14.0 with replaced IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from HS 13.6. Also used Dosdude1’s Bluetooth patch when it came through on the patch updater and Bluetooth kept working . I assume the patch did the same kext replacement.

Now BT not working again with 14.1 and unfortunately replacing IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext with those from HS 13.6 does not work this time. I have gone further with also replacing IO80211Family.kext, AirPortBrcmNIC-MFG.kext and IO80211FamilyV2.kext from HS but still no BT. This is what I have with 14.1:

Menu bar - Bluetooth not available

From System info Bluetooth - no information found

From System info USB - BRCM20702 Hub:


Product ID: 0x4500

Vendor ID: 0x0a5c (Broadcom Corp.)

Version: 1.00

Speed: Up to 12Mb/sec

Manufacturer: Apple Inc.

Location ID: 0x7d100000 / 1

Current Available (mA): 500

Current Required (mA): 94

Extra Operating Current (mA): 0

Built-In: Yes


Bluetooth USB Host Controller:


Product ID: 0x828d

Vendor ID: 0x05ac (Apple Inc.)

Version: 1.44

Speed: Up to 12Mb/sec

Manufacturer: Apple Inc.

Location ID: 0x7d130000 / 4

Current Available (mA): 500

Extra Operating Current (mA): 0

Built-In: Yes



So system knows it is there on the USB bus but there must be some kext I need to change. Wifi is fine and working at ac speeds. I have not used the WiFi patch. Any help appreciated but staying with 14.0 for now.



On a different issue which I have solved but may help others who have the same problem. I noticed that with Mojave I could no longer use the keyboard (I like using a wired one) to get to the boot screen. In fact no keys worked until the OS was up and running. So impossible to set start drive, PRAM reset etc. I connected my keyboard via an Apple LED Cinema Display and it appears Mojave does not power the hub up quickly enough to recognise the keyboard. Connecting it directly to the Macs usb fixed this. I knew Apple’s USB keyboard extension would come it useful one day!
 
First post here but have been following Dosdude1’s threads on High Sierra and now Mojave to get my venerable Mac up with the latest OS. Using a Mac Pro 3.1 with evga GTX 680 and an updated WiFi/BT4 combined internal card so have had Hand Off and Continuity since El Capitan. HS went without a hitch. Mojave works very well except for BT and I suspect my BT4.0 card upgrade may be the problem. Got it fully working in 14.0 with replaced IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext from HS 13.6. Also used Dosdude1’s Bluetooth patch when it came through on the patch updater and Bluetooth kept working . I assume the patch did the same kext replacement.

Now BT not working again with 14.1 and unfortunately replacing IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext with those from HS 13.6 does not work this time. I have gone further with also replacing IO80211Family.kext, AirPortBrcmNIC-MFG.kext and IO80211FamilyV2.kext from HS but still no BT. This is what I have with 14.1:

Menu bar - Bluetooth not available

From System info Bluetooth - no information found

From System info USB - BRCM20702 Hub:


Product ID: 0x4500

Vendor ID: 0x0a5c (Broadcom Corp.)

Version: 1.00

Speed: Up to 12Mb/sec

Manufacturer: Apple Inc.

Location ID: 0x7d100000 / 1

Current Available (mA): 500

Current Required (mA): 94

Extra Operating Current (mA): 0

Built-In: Yes


Bluetooth USB Host Controller:


Product ID: 0x828d

Vendor ID: 0x05ac (Apple Inc.)

Version: 1.44

Speed: Up to 12Mb/sec

Manufacturer: Apple Inc.

Location ID: 0x7d130000 / 4

Current Available (mA): 500

Extra Operating Current (mA): 0

Built-In: Yes



So system knows it is there on the USB bus but there must be some kext I need to change. Wifi is fine and working at ac speeds. I have not used the WiFi patch. Any help appreciated but staying with 14.0 for now.



On a different issue which I have solved but may help others who have the same problem. I noticed that with Mojave I could no longer use the keyboard (I like using a wired one) to get to the boot screen. In fact no keys worked until the OS was up and running. So impossible to set start drive, PRAM reset etc. I connected my keyboard via an Apple LED Cinema Display and it appears Mojave does not power the hub up quickly enough to recognise the keyboard. Connecting it directly to the Macs usb fixed this. I knew Apple’s USB keyboard extension would come it useful one day!

Have you tried this ? : Mojave 10.14.0 untouched IOBluetooth kexts
If not try them, maybe they work for your machine.
If neither these will work, then I guess you have to re-install Mojave and de-select the "Wifi-patch", I know it sounds crazy, but with combo Wifi/BT4.0 the stock Mojave IO80211Family* kext is involved in detecting or powering correctly the BT 4.0 card.
 
  • Like
Reactions: TimothyR734
Working awesome
[doublepost=1541129635][/doublepost]
They will be available soon

If someone tries to use version 1.1 created for 10.14 of pkouame in 10.14.1, it may break the system, be aware of that. For the quickest, you can use my script created in Automator. It is less invasive and leave things in place (every time you switch between dark mode and clear mode, you will have to close the applications for the change to be made, in the dark mode there are still some smaller ones, which are the gray menus in applications that do not have dark mode by default).
 

Attachments

  • DarkMode_MOD.zip
    9.4 KB · Views: 138
  • Like
Reactions: TimothyR734
Mac Mini 4,1, APFS-formatted drive:
- OTA update to 14.1 = boot loop repeating every 2 seconds
- OTA update to 14.1 + patching the install from a new @dosdude1 1.2.3 patcher tool = boot progress bar stuck at 2/3 for 6 hours. No network connection up, so not even remote ssh.
- reinstall 14 to 14.1 using 1.2.3 patcher and 14.1 installer (including post-install patching) = boot progress bar stuck at 2/3 for 4 hours, no network connectivity as well.

Now rolling back to 14 from a backup, so it is a fail from me, but YMMV.

I did the reinstall of 14.1 over the existing 14 on my Mac Mini 4,1 using the 1.2.3 patcher and everything worked well. Whatever happened with the OTA update attempt probably screwed up your effort.
 
  • Like
Reactions: TimothyR734
not working here, Mac mini Server (Mid 2011)
To those who use Mojave on APFS file system, I have managed to "fix" the APFS Recovery Volume to make it bootable with CMD+R and mainly with USB input devices responsive, working wifi and everything else, just follow next steps, boot from a Mojave APFS Volume, launch Terminal and type:

diskutil apfs list
{locate your "APFS Recovery Volume" diskXs3 [for an internal "APFS Container" is typically mounted on disk1s3]}

diskutil mount diskXs3
open /Volumes/Recovery


landing on Finder, double tap on the "random-numbers-letters" folder, once inside rename these files:

prelinkedkernel into prelinkedkernelbackup
immutablekernel
into immutablekernelbackup
PlatformSupport.plist
into PlatformSupportbackup

Don't close Finder yet, once you renamed those 3 files, press CMD+N, then from this new Finder Window press CMD+SHIFT+G (or use "Go to Folder"): /System/Library/PrelinkedKernels/

while inside this path copy the file prelinkedkernel into the previous Finder Window, exactly were you renamed those 3 files, lastly rename this fresh copied file from prelinkedkernel to immutablekernel

Now you have a working APFS Recovery Volume.

edit:
On APFS scheme the "APFS Recovery Volume" is always on the 3rd (hidden) partition.


THANKS !

But not working here too on Imac 10,1.

yet all my partition shema is APFS ( 2 Internal SSD)

My boot drive is
Samsung SSD

Any idea ?



diskutil apfs list

APFS Containers (2 found)

|

+-- Container disk2 37D8A16C-697A-445F-A036-25581E864153

| ====================================================

| APFS Container Reference: disk2

| Size (Capacity Ceiling): 249849593856 B (249.8 GB)

| Capacity In Use By Volumes: 141923258368 B (141.9 GB) (56.8% used)

| Capacity Not Allocated: 107926335488 B (107.9 GB) (43.2% free)

| |

| +-< Physical Store disk0s2 59811FB6-09E0-4ABB-96FA-B24C99000F06

| | -----------------------------------------------------------

| | APFS Physical Store Disk: disk0s2

| | Size: 249849593856 B (249.8 GB)

| |

| +-> Volume disk2s1 0608AF9E-CDC3-4D01-8520-ED1DD50C8D22

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk2s1 (No specific role)

| | Name: Samsung SSD (Case-insensitive)

| | Mount Point: /

| | Capacity Consumed: 141238292480 B (141.2 GB)

| | FileVault: No

| |

| +-> Volume disk2s2 2768D573-F7CB-4089-8450-0AF0E07058BA

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk2s2 (Preboot)

| | Name: Preboot (Case-insensitive)

| | Mount Point: Not Mounted

| | Capacity Consumed: 9732096 B (9.7 MB)

| | FileVault: No

| |

| +-> Volume disk2s3 1A6041BE-D1BB-4B21-A42E-2C4C529E6326

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk2s3 (Recovery)

| | Name: Recovery (Case-insensitive)

| | Mount Point: Not Mounted

| | Capacity Consumed: 536891392 B (536.9 MB)

| | FileVault: No

| |

| +-> Volume disk2s4 5EB78781-79AA-4109-BDC4-E2F7002ED7F2

| ---------------------------------------------------

| APFS Volume Disk (Role): disk2s4 (VM)

| Name: VM (Case-insensitive)

| Mount Point: /private/var/vm

| Capacity Consumed: 20480 B (20.5 KB)

| FileVault: No

|

+-- Container disk3 794C6862-5095-48D6-9A13-C6AF119FD8F0

====================================================

APFS Container Reference: disk3

Size (Capacity Ceiling): 274854445056 B (274.9 GB)

Capacity In Use By Volumes: 221975134208 B (222.0 GB) (80.8% used)

Capacity Not Allocated: 52879310848 B (52.9 GB) (19.2% free)

|

+-< Physical Store disk1s2 57542241-EAB8-4161-BF14-E2AA86016E7C

| -----------------------------------------------------------

| APFS Physical Store Disk: disk1s2

| Size: 274854445056 B (274.9 GB)

|

+-> Volume disk3s1 3C5707EA-6F54-4F63-9CE4-620850C228FB

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s1 (No specific role)

| Name: Macintosh SSD (Case-insensitive)

| Mount Point: /Volumes/Macintosh SSD

| Capacity Consumed: 221286653952 B (221.3 GB)

| FileVault: No

|

+-> Volume disk3s2 F4D7A65C-1A04-4071-9EBD-D618F5235772

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s2 (Preboot)

| Name: Preboot (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 18886656 B (18.9 MB)

| FileVault: No

|

+-> Volume disk3s3 38311B91-9E09-427F-9DA6-B13E6E996C24

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s3 (Recovery)

| Name: Recovery (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 528928768 B (528.9 MB)

| FileVault: No

|

+-> Volume disk3s4 322BFAB2-8E8F-4AEE-9630-1ABC6B49AC8A

---------------------------------------------------

APFS Volume Disk (Role): disk3s4 (VM)

Name: VM (Case-insensitive)

Mount Point: Not Mounted

Capacity Consumed: 20480 B (20.5 KB)

FileVault: No
 
  • Like
Reactions: TimothyR734
THANKS !

But not working here too on Imac 10,1.

yet all my partition shema is APFS ( 2 Internal SSD)

My boot drive is
Samsung SSD

Any idea ?



diskutil apfs list

APFS Containers (2 found)

|

+-- Container disk2 37D8A16C-697A-445F-A036-25581E864153

| ====================================================

| APFS Container Reference: disk2

| Size (Capacity Ceiling): 249849593856 B (249.8 GB)

| Capacity In Use By Volumes: 141923258368 B (141.9 GB) (56.8% used)

| Capacity Not Allocated: 107926335488 B (107.9 GB) (43.2% free)

| |

| +-< Physical Store disk0s2 59811FB6-09E0-4ABB-96FA-B24C99000F06

| | -----------------------------------------------------------

| | APFS Physical Store Disk: disk0s2

| | Size: 249849593856 B (249.8 GB)

| |

| +-> Volume disk2s1 0608AF9E-CDC3-4D01-8520-ED1DD50C8D22

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk2s1 (No specific role)

| | Name: Samsung SSD (Case-insensitive)

| | Mount Point: /

| | Capacity Consumed: 141238292480 B (141.2 GB)

| | FileVault: No

| |

| +-> Volume disk2s2 2768D573-F7CB-4089-8450-0AF0E07058BA

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk2s2 (Preboot)

| | Name: Preboot (Case-insensitive)

| | Mount Point: Not Mounted

| | Capacity Consumed: 9732096 B (9.7 MB)

| | FileVault: No

| |

| +-> Volume disk2s3 1A6041BE-D1BB-4B21-A42E-2C4C529E6326

| | ---------------------------------------------------

| | APFS Volume Disk (Role): disk2s3 (Recovery)

| | Name: Recovery (Case-insensitive)

| | Mount Point: Not Mounted

| | Capacity Consumed: 536891392 B (536.9 MB)

| | FileVault: No

| |

| +-> Volume disk2s4 5EB78781-79AA-4109-BDC4-E2F7002ED7F2

| ---------------------------------------------------

| APFS Volume Disk (Role): disk2s4 (VM)

| Name: VM (Case-insensitive)

| Mount Point: /private/var/vm

| Capacity Consumed: 20480 B (20.5 KB)

| FileVault: No

|

+-- Container disk3 794C6862-5095-48D6-9A13-C6AF119FD8F0

====================================================

APFS Container Reference: disk3

Size (Capacity Ceiling): 274854445056 B (274.9 GB)

Capacity In Use By Volumes: 221975134208 B (222.0 GB) (80.8% used)

Capacity Not Allocated: 52879310848 B (52.9 GB) (19.2% free)

|

+-< Physical Store disk1s2 57542241-EAB8-4161-BF14-E2AA86016E7C

| -----------------------------------------------------------

| APFS Physical Store Disk: disk1s2

| Size: 274854445056 B (274.9 GB)

|

+-> Volume disk3s1 3C5707EA-6F54-4F63-9CE4-620850C228FB

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s1 (No specific role)

| Name: Macintosh SSD (Case-insensitive)

| Mount Point: /Volumes/Macintosh SSD

| Capacity Consumed: 221286653952 B (221.3 GB)

| FileVault: No

|

+-> Volume disk3s2 F4D7A65C-1A04-4071-9EBD-D618F5235772

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s2 (Preboot)

| Name: Preboot (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 18886656 B (18.9 MB)

| FileVault: No

|

+-> Volume disk3s3 38311B91-9E09-427F-9DA6-B13E6E996C24

| ---------------------------------------------------

| APFS Volume Disk (Role): disk3s3 (Recovery)

| Name: Recovery (Case-insensitive)

| Mount Point: Not Mounted

| Capacity Consumed: 528928768 B (528.9 MB)

| FileVault: No

|

+-> Volume disk3s4 322BFAB2-8E8F-4AEE-9630-1ABC6B49AC8A

---------------------------------------------------

APFS Volume Disk (Role): disk3s4 (VM)

Name: VM (Case-insensitive)

Mount Point: Not Mounted

Capacity Consumed: 20480 B (20.5 KB)

FileVault: No

It's a bit weird your APFS Scheme, I mean there is no trace of any disk1sY
Before I tell how to re-adjust your Recovery, what do you have on "Macintosh SSD" disk3s1 ? Another Mojave or HighSierra in APFS ?

And if you can post also simplified: diskutil list

Anyway, you should boot from your Samsung SSD Mojave, and follow my APFS Recovery part2.
 
  • Like
Reactions: TimothyR734
It's a bit weird your APFS Scheme, I mean there is no trace of any disk1sY
Before I tell how to re-adjust your Recovery, what do you have on "Macintosh HD" disk3s1 ? Another Mojave or HighSierra in APFS ?

And if you can post also simplified: diskutil list


Thanks jackluke for help.

There is only data on Macintosh SSD
first time i had install Mojave on it, this is the reason why there another recovery partition

OS Mojave is on Samsung SSD

Here is my list

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *250.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk2 249.8 GB disk0s2


/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *275.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_APFS Container disk3 274.9 GB disk1s2


/dev/disk2 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +249.8 GB disk2

Physical Store disk0s2

1: APFS Volume Samsung SSD 141.3 GB disk2s1

2: APFS Volume Preboot 9.7 MB disk2s2

3: APFS Volume Recovery 536.9 MB disk2s3

4: APFS Volume VM 20.5 KB disk2s4


/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +274.9 GB disk3

Physical Store disk1s2

1: APFS Volume Macintosh SSD 221.3 GB disk3s1

2: APFS Volume Preboot 18.9 MB disk3s2

3: APFS Volume Recovery 528.9 MB disk3s3

4: APFS Volume VM 20.5 KB disk3s4


/dev/disk4 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *275.1 GB disk4

1: EFI EFI 209.7 MB disk4s1

2: Apple_APFS Container disk5 274.9 GB disk4s2


/dev/disk5 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +274.9 GB disk5

Physical Store disk4s2

1: APFS Volume Preboot 20.5 KB disk5s2

2: APFS Volume Recovery 20.5 KB disk5s3

3: APFS Volume VM 1.1 GB disk5s4

4: APFS Volume Clone Samsung SSD 10.0 GB disk5s1
 
Last edited:
  • Like
Reactions: TimothyR734
Thanks jackluke for help.

On Macintosh HD i have ONLY my Data ( its is an SSD too, do not trust name)
first time i had install Mojave on it, this is the reason why there another recovery partition

OS Mojave is on Samsung SSD

Here is my list

diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *250.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk2 249.8 GB disk0s2


/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *275.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_APFS Container disk3 274.9 GB disk1s2


/dev/disk2 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +249.8 GB disk2

Physical Store disk0s2

1: APFS Volume Samsung SSD 141.3 GB disk2s1

2: APFS Volume Preboot 9.7 MB disk2s2

3: APFS Volume Recovery 536.9 MB disk2s3

4: APFS Volume VM 20.5 KB disk2s4


/dev/disk3 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +274.9 GB disk3

Physical Store disk1s2

1: APFS Volume Macintosh SSD 221.3 GB disk3s1

2: APFS Volume Preboot 18.9 MB disk3s2

3: APFS Volume Recovery 528.9 MB disk3s3

4: APFS Volume VM 20.5 KB disk3s4


/dev/disk4 (external, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *275.1 GB disk4

1: EFI EFI 209.7 MB disk4s1

2: Apple_APFS Container disk5 274.9 GB disk4s2


/dev/disk5 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +274.9 GB disk5

Physical Store disk4s2

1: APFS Volume Preboot 20.5 KB disk5s2

2: APFS Volume Recovery 20.5 KB disk5s3

3: APFS Volume VM 1.1 GB disk5s4

4: APFS Volume Clone Samsung SSD 10.0 GB disk5s1

Ok, but another weird thing is that even on disk3s3 you have another Recovery filled.

Anyway before attempt this unplug any external USB hard disks, USB drive and unmount any DMG (also eventually DMG app you were installing) mounted on your desktop.

Then try this (only for @tchek current APFS scheme not valid for the others) boot Mojave from your Samsung SSD normally, then launch Terminal and type:

diskutil mount disk2s3

diskutil apfs changeVolumeRole disk2s3 R

diskutil apfs updatePreboot disk2s1

then type: open /Volumes/Recovery/0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/

landing on Finder using TextEdit or any other plain-text editor launch com.apple.boot.plist

Inside it first check the green part if matches with your file, in this place add the orange part (in one line) close and save:

<string>root-dmg=file:///0608AF9E-CDC3-4D01-8520-ED1DD50C8D22/BaseSystem.dmg -no_compat_check -v</string>

Now, reboot and hold CMD+R after power-on chime, if you still can't reach APFS Recovery, post here a picture of your verbose screen.
 
Last edited:
Good catch and thank you for your quick response.

So, APFS support requiring High Sierra to be installed first certainly makes good sense -> perhaps this could be added to your FAQ or the APFS formatting section on the patcher page? It may be useful information for others who like myself have tried to go straight to Mojave, skipping High Sierra.

I've dropped the original (Lion) HDD back in and will download and install High Sierra. It seems the Internet's preferred method for getting a copy of High Sierra is using your Patcher tool available from dosdude1.com :)



Thanks for the feedback, that is good to know. I have preferred to buy standalone mSATA SSDs (mini-PCIe keyed) and then drop them into adapter cases e.g. "mSATA to SATA" or "mSATA to 2.5" IDE/PATA" depending on my needs. This has made good sense for me given that I have quite a range of older non-SATA Macs which I have upgraded and didn't want to get stuck with overpriced SSDs constrained to the old PATA interface.

I actually skipped High Sierra and am now running 10.14.1, everything so far so good...
I just used the Disk Utility from dosdude's 10.14 installer to convert my boot drive to APFS, afterwards I created the new installer with the latest version, since 10.14.1 would not boot after updating via system prefs, no matter what I tried...
Hope this won't affect me in the long run... Anyway, congrats and many thanks to dosdude!
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.