macOS 10.14 Mojave on Unsupported Macs Thread

[K two]

Anything that can run High Sierra natively, supports APFS.

An interesting comparison -

HFS+ on SSD

APFS on SSHD

Both Screen shots 5 mins. post boot

 

[avz]

It came with High Sierra, but I forgot to check, that the filesystem was HFS+ or APFS.

How many times I have to run the install, before I run the post-install? At first, it takes 17min, second 35min, every time than I've press alt to choose drive for booting, only yellow os base system appear (USB drive). When after the post-install (third run) I want select boot drive only USB seen. If I unplug it before reboot, only flashing folder seen.

It seems that the previous owner used Clover(for purpose of multi-booting, I guess) on your machine so that is why it behaves differently. Unfortunately I lack knowledge about Clover but maybe somebody with experience will chime in.
[doublepost=1567265486][/doublepost]

An interesting comparison - View attachment 855491
HFS+ on SSD View attachment 855492
APFS on SSHD

Both Screen shots 5 mins. post boot

The very first iteration of the 10.14.3 is the best I guess. It really only needed 2GB of RAM to run very well no matter the file system.

 

[K two]

It seems that the previous owner used Clover(for purpose of multi-booting, I guess) on your machine so that is why it behaves differently. Unfortunately I lack knowledge about Clover but maybe somebody with experience will chime in.
[doublepost=1567265486][/doublepost]

The very first iteration of the 10.14.3 is the best I guess. It really only needed 2GB of RAM to run very well no matter the file system.

I have found 14.3 will do everything 14.6 will do except News+ with less system overhead and lower CPU/Northbridge temps, overall. YMMV

 

[Cloud71]

It seems that the previous owner used Clover(for purpose of multi-booting, I guess) on your machine so that is why it behaves differently. Unfortunately I lack knowledge about Clover but maybe somebody with experience will chime in.
[doublepost=1567265486][/doublepost]

The very first iteration of the 10.14.3 is the best I guess. It really only needed 2GB of RAM to run very well no matter the file system.

I'm away from home, before I left, I did a internet recovery so I will start again from Lion. The question is, for the next Mojave install, should I force APFS, or I should remain on HFS+? I guess 10.14.6 is the last Mojave version, Catalina beta is out there awhile, so Apple wouldn't release furter updates, so system update restriction wouldn't play.

 

[avz]

I'm away from home, before I left, I did a internet recovery so I will start again from Lion. The question is, for the next Mojave install, should I force APFS, or I should remain on HFS+? I guess 10.14.6 is the last Mojave version, Catalina beta is out there awhile, so Apple wouldn't release furter updates, so system update restriction wouldn't play.

It is actually a very good question as people seem to have very different experiences with APFS and HFS+(even on the same hardware).
Being a noob I just followed dosdude1's instructions "to use APFS if your target drive is an SSD" and never had to regret it. APFS local snapshot is a very cool feature that allows you to restore your system to its previous state in 10 seconds with is important when you experimenting with unsupported system.

 

[Cloud71]

It is actually a very good question as people seem to have very different experiences with APFS and HFS+(even on the same hardware).
Being a noob I just followed dosdude1's instructions "to use APFS if your target drive is an SSD" and never had to regret it. APFS local snapshot is a very cool feature that allows you to restore your system to its previous state in 10 seconds with is important when you experimenting with unsupported system.

Then, because it came with an 500GB HDD, I prefer HFS+ instead.

Thanks.

 

[jasoncarle]

Isn't it because we use AppleGVA.framework from High Sierra in our Mojave installs?

Hell if I know...

 

[avz]

Hell if I know...

I believe the latest 1.3.3 patcher should have it. If you used older Mojave patcher previously you did not have that benefit.

 

[MTBnBeer]

Can confirm: After re-applying patches on the MBP4,1 the supplemental-2 build 18G95 works fine.
The separate backlight patch for CCFL is still needed, but also still working.

UPDATE: I reinstalled ALL the patches and rebooted... and Backlight and Sleep are working properly again.

Strange. I just installed macOS 10.14.6 (18G95) via OTA, applied macOS Mojave Patcher "patches" when prompted, rebooted... then ran @dosdude1 bkltpatch10.14.2 to restore backlight control via F1 and F2 keys on my MBP4,1 like I have after all the other Mojave updates.

This time bkltpatch10.14.2 did NOT work: screen in at full brightness but F1 & F2 keys don't dim / brighten my CCFL backlight.

Not a big deal since the brightness is fine... but would really like to be able to dim using the F1 & F2 keys again.

 

[Cloud71]

Then, because it came with an 500GB HDD, I prefer HFS+ instead.

Thanks.

Well, I defeated the beast
The installer worked with HFS+ filesystem.

 

[jasoncarle]

I believe the latest 1.3.3 patcher should have it. If you used older Mojave patcher previously you did not have that benefit.

Whatever did it, it worked.

 

[learnmedia1]

APFS local snapshot is a very cool feature that allows you to restore your system to its previous state in 10 seconds with is important when you experimenting with unsupported system.

What is this APFS local snapshot about which you speak?

 

[avz]

What is this APFS local snapshot about which you speak?

https://support.apple.com/en-us/HT204015

 

[xbomber2002]

Hi,
Cannot update from 10.14.5 to 10.14.6. Black screen when I boot from my usb stick install media. Currently I have a Mac Pro 3,1 with non efi Nvidia gt710 card...Don’t want to re use my old stock ati 2600xt for that job if not mandatory.

 

[rotarypower101]

How do you get “Hey Siri” working on an older Mac? The old Dictation trick does
Not work anymore

Does anyone know how to get hey Siri working on a MP3,1 or even if it can work?

"Hey Siri" activates Siri for me using AirPods2, and in system preferences>sound>Input level the system seems to see the audio coming in over the input line, but Siri replies"Sorry Im having trouble hearing you"

 

[johnsawyercjs]

Has anyone been seeing repeated daily instances of "NotificationCenter quit unexpectedly", and if so, whether something in our patched code could have anything to do with this? I'm running MacOS 10.14.4 on a Mid 2009 Macbook (5,2), that I installed using dosdude1's MacOS Mojave Patcher 1.3.0, onto a 500GB Samsung SSD formatted as HFS+.

Here's the crash report:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000004e00000009
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [13227]

And:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libswiftCore.dylib 0x00007fff7a449c63 _swift_release_(swift::HeapObject*) + 19
1 libdispatch.dylib 0x00007fff7a9865f8 _dispatch_call_block_and_release + 12
2 libdispatch.dylib 0x00007fff7a98763d _dispatch_client_callout + 8
3 libdispatch.dylib 0x00007fff7a99268d _dispatch_main_queue_callback_4CF + 1135
4 com.apple.CoreFoundation 0x00007fff4e51c4a6 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
5 com.apple.CoreFoundation 0x00007fff4e51bbd3 __CFRunLoopRun + 2300
6 com.apple.CoreFoundation 0x00007fff4e51b085 CFRunLoopRunSpecific + 459
7 com.apple.HIToolbox 0x00007fff4d7f99db RunCurrentEventLoopInMode + 292
8 com.apple.HIToolbox 0x00007fff4d7f9715 ReceiveNextEventCommon + 603
9 com.apple.HIToolbox 0x00007fff4d7f94a6 _BlockUntilNextEventMatchingListInModeWithFilter + 64
10 com.apple.AppKit 0x00007fff4bb93ffb _DPSNextEvent + 965
11 com.apple.AppKit 0x00007fff4bb92d93 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
12 com.apple.AppKit 0x00007fff4bb8ceb0 -[NSApplication run] + 699
13 com.apple.AppKit 0x00007fff4bb7c3f0 NSApplicationMain + 777
14 com.apple.notificationcenterui 0x000000010cc08eb7 0x10cbaa000 + 388791
15 com.apple.notificationcenterui 0x000000010cc09bbe 0x10cbaa000 + 392126
16 libswiftObjectiveC.dylib 0x00007fff7a741f4f autoreleasepool<A>(invoking + 47
17 com.apple.notificationcenterui 0x000000010cc0869a 0x10cbaa000 + 386714
18 libdyld.dylib 0x00007fff7a9d43d5 start + 1

 

[avz]

Has anyone been seeing repeated daily instances of "NotificationCenter quit unexpectedly", and if so, whether something in our patched code could have anything to do with this? I'm running MacOS 10.14.4 on a Mid 2009 Macbook (5,2), that I installed using dosdude1's MacOS Mojave Patcher 1.3.0, onto a 500GB Samsung SSD formatted as HFS+.

Here's the crash report:

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000004e00000009
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [13227]

And:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libswiftCore.dylib 0x00007fff7a449c63 _swift_release_(swift::HeapObject*) + 19
1 libdispatch.dylib 0x00007fff7a9865f8 _dispatch_call_block_and_release + 12
2 libdispatch.dylib 0x00007fff7a98763d _dispatch_client_callout + 8
3 libdispatch.dylib 0x00007fff7a99268d _dispatch_main_queue_callback_4CF + 1135
4 com.apple.CoreFoundation 0x00007fff4e51c4a6 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
5 com.apple.CoreFoundation 0x00007fff4e51bbd3 __CFRunLoopRun + 2300
6 com.apple.CoreFoundation 0x00007fff4e51b085 CFRunLoopRunSpecific + 459
7 com.apple.HIToolbox 0x00007fff4d7f99db RunCurrentEventLoopInMode + 292
8 com.apple.HIToolbox 0x00007fff4d7f9715 ReceiveNextEventCommon + 603
9 com.apple.HIToolbox 0x00007fff4d7f94a6 _BlockUntilNextEventMatchingListInModeWithFilter + 64
10 com.apple.AppKit 0x00007fff4bb93ffb _DPSNextEvent + 965
11 com.apple.AppKit 0x00007fff4bb92d93 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
12 com.apple.AppKit 0x00007fff4bb8ceb0 -[NSApplication run] + 699
13 com.apple.AppKit 0x00007fff4bb7c3f0 NSApplicationMain + 777
14 com.apple.notificationcenterui 0x000000010cc08eb7 0x10cbaa000 + 388791
15 com.apple.notificationcenterui 0x000000010cc09bbe 0x10cbaa000 + 392126
16 libswiftObjectiveC.dylib 0x00007fff7a741f4f autoreleasepool<A>(invoking + 47
17 com.apple.notificationcenterui 0x000000010cc0869a 0x10cbaa000 + 386714
18 libdyld.dylib 0x00007fff7a9d43d5 start + 1

You are using an outdated versions of the patcher and Mojave. So the question kind of become pointless.

 

[deeveedee]

UPDATE: I reinstalled ALL the patches and rebooted... and Backlight and Sleep are working properly again.

Strange. I just installed macOS 10.14.6 (18G95) via OTA, applied macOS Mojave Patcher "patches" when prompted, rebooted... then ran @dosdude1 bkltpatch10.14.2 to restore backlight control via F1 and F2 keys on my MBP4,1 like I have after all the other Mojave updates.

This time bkltpatch10.14.2 did NOT work: screen in at full brightness but F1 & F2 keys don't dim / brighten my CCFL backlight.

Not a big deal since the brightness is fine... but would really like to be able to dim using the F1 & F2 keys again.

I had a similar experience with my HackBookPro5,1 (actually a Thinkpad T61). After applying the 10.14.6 supplemental update, my brightness slider / keys did not work and the GPU temp / core frequency were not visible in HWMonitor. I used DosDude Mojave Patcher to apply the Legacy Video Patch, Platform Compatibility Patch and Atheros Patch (not sure any or all were necessary) and rebooted. I still could not adjust brightness or view the GPU in HWMonitor. I then ran 'sudo kextcache -i /' in a terminal and rebooted. Brightness adjustment now works perfectly and the GPU is visible in HWMonitor. Everything appears to be working fine after the 10.14.6 supplemental update.

 

[johnsawyercjs]

You are using an outdated versions of the patcher and Mojave. So the question kind of become pointless.

Not pointless. dosdude1's Patch Updater 1.2.0 is installed on my Macbook (it's still the latest version, installed by MacOS Mojave Patcher 1.3.0 through 1.3.3), and it's been keeping all of his patches up to date on my Macbook, according to Patch Updater. From what I understand (or maybe assumed), because of this, if Patch Updater is working properly on a slightly older version of Mojave, you don't need to create and use a new patched installer volume using the latest version of Mojave and dosdude1's MacOS Mojave Patcher just to get his latest patches. For instance, Patch Updater reports that my Macbook has the 'Legacy iSight/Webcam Patch' installed, even though that's installed by versions of dosdude1's 'MacOS Post Install' later than 1.3.0, which I haven't used yet.

I'm asking whether this problem has been seen with a patched version of 10.14.4 because I'd like to know if anyone knows if updating past 10.14.4 is the fix for this crash. If not, then I'd have no real incentive to update to 10.14.6 since everything else is running fine--I'd rather not update if there's no real need for it, and run the risk of encountering some other problem.

 

[avz]

Not pointless. dosdude1's Patch Updater 1.2.0 is installed on my Macbook (it's still the latest version, installed by MacOS Mojave Patcher 1.3.0 through 1.3.3), and it's been keeping all of his patches up to date on my Macbook, according to Patch Updater. From what I understand (or maybe assumed), because of this, if Patch Updater is working properly on a slightly older version of Mojave, you don't need to create and use a new patched installer volume using the latest version of Mojave and dosdude1's MacOS Mojave Patcher just to get his latest patches. For instance, Patch Updater reports that my Macbook has the 'Legacy iSight/Webcam Patch' installed, even though that's installed by versions of dosdude1's 'MacOS Post Install' later than 1.3.0, which I haven't used yet.

I'm asking whether this problem has been seen with a patched version of 10.14.4 because I'd like to know if anyone knows if updating past 10.14.4 is the fix for this crash. If not, then I'd have no real incentive to update to 10.14.6 since everything else is running fine--I'd rather not update if there's no real need for it, and run the risk of encountering some other problem.

From what I understand 10.14.4 is considered to be the "bottom" so you can only go up from here. But as they say YMMV, proceed at your own caution. I don't have any experience with the MacBook5,2 to give you any definite answers.

 

[C Punkt]

Hi everybody, this is my first post here and I registered because I installed the Mojave patch on my iMac8.1 (after adding 2x2gb ram and an SSD) Now the WiFi won't Show up, apparently it does not recognize the Adapter... I'm not sure if the Hardware is just not supported or if there is a way to make it work (otherwise I you could recommend me a working small WiFi-usb stick?) in the System report I can't look up the interface info on "Wifi" as in the Picture of Dosdude's Homepage where it tells you to look up if you have a working Card, Looking there and then checking whether it says (0x14E4, 0x8C) or else.. In that window it only Show the "sorfware versions:" column but noch the "interface" column.. however I could look up in the terminal I have the BCM4328 WiFi module and not the BCM4321 WiFi module, which gives me hope.

(at least according to the info on the Sierra patch for WiFi, in the info for the mojave patch it doesn't say anything About WiFi incompatibilites..)

Help would be awesome! Thanks!

 

[deeveedee]

I need to remove the "APFS Patch" that I installed with the DosDude Mojave Patcher (1.33). Does anyone know what files I need to remove and/or modify in order to completely uninstall the APFS Patch? Thank you.

 

[K two]

From what I understand 10.14.4 is considered to be the "bottom" so you can only go up from here. But as they say YMMV, proceed at your own caution. I don't have any experience with the MacBook5,2 to give you any definite answers.

10.14.4 18E226 Too many random KPs compared to 10.14.2,3,5,6. All rock solid on a variety of Macs - 09 Minis, MB5,1, iMac11,2 - dot4 not.

 

[Flacko]

I need to remove the "APFS Patch" that I installed with the DosDude Mojave Patcher (1.33). Does anyone know what files I need to remove and/or modify in order to completely uninstall the APFS Patch? Thank you.

Here you go. You will need to mount the efi drive. To find which one it is use:

sudo diskutil list

This will display your drives and you can identify the efi partition. In my case it is disk0s1. Then mount this partition:

sudo diskutil mount disk0s1

After a moment the efi drive should appear on your desktop. You can then use finder to delete the following: apfs.efi, /BOOT/BOOTX64.EFI and startup.nsh.

 

[deeveedee]

Here you go. You will need to mount the efi drive. To find which one it is use:

sudo diskutil list

This will display your drives and you can identify the efi partition. In my case it is disk0s1. Then mount this partition:

sudo diskutil mount disk0s1

After a moment the efi drive should appear on your desktop. You can then use finder to delete the following: apfs.efi, /BOOT/BOOTX64.EFI and startup.nsh.

Thank you! Can I simply delete the APFS app from the Applications folder or is there more to it than that?