Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

macOS 10.14 Mojave on Unsupported Macs Thread

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.
hey guys, i have a Macbook Pro mid-2009 and it was working fine, TILL the update patcher said is a new LEGACY VIDEO PATCH and i installed it and now i cannot boot any more. at boot i am stuck at APPLE LOGO.
i've tried booting in verbose mode and this is the error i have and cannot boot anymore:
2MT7dJVl.jpg


any help would be greatly appreciated! cc @dosdude1
 
makima said:
hey guys, i have a Macbook Pro mid-2009 and it was working fine, TILL the update patcher said is a new LEGACY VIDEO PATCH and i installed it and now i cannot boot any more. at boot i am stuck at APPLE LOGO.
i've tried booting in verbose mode and this is the error i have and cannot boot anymore:


any help would be greatly appreciated! cc @dosdude1
Click to expand...

I guess this chain of errors followed after an incorrect patch framework version used or an incorrect framework overwriting/moving, from my little experience some core frameworks (Skylight, OpenCL, CoreDisplay, GPUWrangler and others) must be overwrited/moved only from single user mode or a Recovery/USBInstall environment, but not from the Finder or the GUI Mode, because from GUI mode their copy/update will fail for sure even using "sudo".

While instead some other core frameworks indeed can be replaced from GUI Mode "on-the-fly", I know because I've tested, and they are: OpenGL, GPUSupport, SiriUI, CoreUI, HIToolbox and some other, also CoreBrightness (for night shift) can be replaced on-the-fly, but surely CoreDisplay and GPUWrangler from my test cannot be replaced on-the-fly. In any case after a framework replacement a reboot is needed.

Instead I guess almost all the Extensions (kext) can be replaced on-the-fly from GUI Mode, because the majority are already pre-loaded in RAM (prelinkedkernel), but after replacing, of course they need permissions fixing and a new kextcache rebuild.

So if you search for a quick and easy fix to your issue, you should re-install 10.14.5 over your current volume and it will restore all the mismatched frameworks.
 
Last edited:
  • Like
Reactions: olad and Larsvonhier
Flacko said:
Hi upipes, I had no problem going from 14.4 to 14.5. First I made a new usb using the latest patcher (1.3.2) and a copy of Mojave using the tools download in the patcher. I like to have the latest patcher usb just in case. Then back up your drive (I make a clone using ccc). Now if anything goes wrong there is a good chance you can recover the situation. As I have an SSD using APFS I used the OTA update in preferences. Once the system has finished updating and goes for the final restart, hit the alt key and select the usb installer drive. Use the post install patches appropriate for your setup. If you have a metal graphics card make sure you do not select the legacy video patch. Also, if you have the APFS rom update make sure APFS patch is not selected. This will be automatically selected if your drive is APFS so make sure you deselect it if your mp3.1 has the rom update. Force cache rebuild and reboot. The first start may trigger the patch updater to warn about some patches being overwritten - in my case night shift. Allow it to fix the problem and reboot. You will then have a fully functioning 14.5.
Click to expand...

Hi Flacko, thank you again for answering.
I do have two questions about your reply... would you be so kind to help me a bit more?
What is the OTA update? where it is? what is this for?
I do have an SSD and when I did a fresh installation of 10.14.4, I have selected the APFS option: do this mean I have the "rom update" that are you referring? So, would this mean that when I update and then launch the OS patcher, I'd have to uncheck the APFS (if checked)? I mean, we don't want to re-apply the APFS, is that?

Thank you very much!
 
avz said:
Gatekeeper 166
MRT 1.41
XProtect 2103

How do you know when apple is "quietly" pushing the security updates? I just realised that I have all my automatic updates turned off. So I have to check for it manually but I guess it gives me the advantage of not turning my machine off during apple's "quiet" update.
Click to expand...
Thx.
When the machines gets suddenly slower, it may be a sign that is happening. After a fresh install, I ran the Terminal command and wait at least 20 minutes, to make sure all are installed. At least two times those updates failed and the functions of the updated components was broken.
 
upipes said:
Hi Flacko, thank you again for answering.
I do have two questions about your reply... would you be so kind to help me a bit more?
What is the OTA update? where it is? what is this for?
I do have an SSD and when I did a fresh installation of 10.14.4, I have selected the APFS option: do this mean I have the "rom update" that are you referring? So, would this mean that when I update and then launch the OS patcher, I'd have to uncheck the APFS (if checked)? I mean, we don't want to re-apply the APFS, is that?

Thank you very much!
Click to expand...
The OTA update ( over the air) is only available in preferences if you have an APFS formatted drive. Click on preferences and you will see software update. It will show you if it has any updates. Right click on drive and select info. It will tell you what format the drive is using.
You will know if you carried out a ROM update for APFS as that is a specific operation that dosdude1 has outlined on page 1. If you have not got an APFS ROM then you need to use the APFS patch. You normally can tell if you have the patch as you get some scrolling text during startup. You only need this if your drive is formatted APFS. If your drive is formatted HFS+ then you do not need the APFS patch but you will not get the OTA update. In which case, boot with the updated patcher usb and install 14.5 over the top of your present system. When the final boot happens boot back into the usb and apply the patches.
 
  • Like
Reactions: olad and roronl
TimothyR734 said:
Aerial and Flurry screensavers are working on my iMac 9,1 News+ crashes
Click to expand...

But you can open the news app right?

Yiorlis59 said:
Hold down fn+f1 or f2,or uncheck the box
In keyword in sys prefs
Click to expand...

It is already uncheck. When I open the news app after 5 seconds it crashes.

This is the crash log;
Code: 
Process:               News [3263]
Path:                  /Applications/News.app/Contents/MacOS/News
Identifier:            News
Version:               4.3 (2133)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           News [3263]
User ID:               501

Date/Time:             2019-05-15 13:43:20.023 +0300
OS Version:            Mac OS X 10.14.5 (18F132)
Report Version:        12
Anonymous UUID:        809D4478-7CAE-B0C9-884C-B74EC2383F74


Time Awake Since Boot: 2700 seconds

System Integrity Protection: disabled

Crashed Thread:        19  Dispatch queue: com.apple.root.user-initiated-qos

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

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

VM Regions Near 0:
-->
    __TEXT                 0000000108a83000-0000000108fcd000 [ 5416K] r-x/r-x SM=COW  /Applications/News.app/Contents/MacOS/News

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib            0x00007fff7350122a mach_msg_trap + 10
1   libsystem_kernel.dylib            0x00007fff7350176c mach_msg + 60
2   com.apple.CoreFoundation          0x00007fff47408e6d __CFRunLoopServiceMachPort + 327
3   com.apple.CoreFoundation          0x00007fff474083da __CFRunLoopRun + 1619
4   com.apple.CoreFoundation          0x00007fff47407b35 CFRunLoopRunSpecific + 459
5   com.apple.GraphicsServices        0x00007fff632edcd7 GSEventRunModal + 295
6   com.apple.GraphicsServices        0x00007fff632ed9ec GSEventRun + 108
7   com.apple.UIKitCore               0x000000010d427d84 UIApplicationMain + 159
8   com.apple.news                    0x0000000108cb46a4 0x108a83000 + 2299556
9   libdyld.dylib                     0x00007fff733cc3d5 start + 1

Thread 1:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 4:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 5:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 6:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 7:: com.apple.uikit.eventfetch-thread
0   libsystem_kernel.dylib            0x00007fff7350122a mach_msg_trap + 10
1   libsystem_kernel.dylib            0x00007fff7350176c mach_msg + 60
2   com.apple.CoreFoundation          0x00007fff47408e6d __CFRunLoopServiceMachPort + 327
3   com.apple.CoreFoundation          0x00007fff474083da __CFRunLoopRun + 1619
4   com.apple.CoreFoundation          0x00007fff47407b35 CFRunLoopRunSpecific + 459
5   com.apple.Foundation              0x00007fff496898ef -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280
6   com.apple.Foundation              0x00007fff49759bea -[NSRunLoop(NSRunLoop) runUntilDate:] + 114
7   com.apple.UIKitCore               0x000000010d429585 -[UIEventFetcher threadMain] + 118
8   com.apple.Foundation              0x00007fff4967f6d2 __NSThread__start__ + 1194
9   libsystem_pthread.dylib           0x00007fff735c02eb _pthread_body + 126
10  libsystem_pthread.dylib           0x00007fff735c3249 _pthread_start + 66
11  libsystem_pthread.dylib           0x00007fff735bf40d thread_start + 13

Thread 8:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 9:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 10:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 11:: Dispatch queue: FCAssetManager.downloadCallbackQueue (QOS: UNSPECIFIED)
0   libobjc.A.dylib                   0x00007fff71bfb36a objc_release + 106
1   com.apple.CoreFoundation          0x00007fff47417ebe -[__NSArrayI dealloc] + 61
2   libobjc.A.dylib                   0x00007fff71bfc11a (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 710
3   com.apple.CoreFoundation          0x00007fff473db32e _CFAutoreleasePoolPop + 22
4   com.apple.Foundation              0x00007fff496993ce -[__NSOperationInternal _start:] + 1182
5   com.apple.Foundation              0x00007fff496c3197 __NSOQSchedule_f + 227
6   libdispatch.dylib                 0x00007fff7337e5f8 _dispatch_call_block_and_release + 12
7   libdispatch.dylib                 0x00007fff7337f63d _dispatch_client_callout + 8
8   libdispatch.dylib                 0x00007fff73381de6 _dispatch_continuation_pop + 414
9   libdispatch.dylib                 0x00007fff733814a3 _dispatch_async_redirect_invoke + 703
10  libdispatch.dylib                 0x00007fff7338d3bc _dispatch_root_queue_drain + 324
11  libdispatch.dylib                 0x00007fff7338db46 _dispatch_worker_thread2 + 90
12  libsystem_pthread.dylib           0x00007fff735bf6b3 _pthread_wqthread + 583
13  libsystem_pthread.dylib           0x00007fff735bf3fd start_wqthread + 13

Thread 12:: JavaScriptCore bmalloc scavenger
0   libsystem_kernel.dylib            0x00007fff7350486a __psynch_cvwait + 10
1   libsystem_pthread.dylib           0x00007fff735c356e _pthread_cond_wait + 722
2   libc++.1.dylib                    0x00007fff70607b31 std::__1::condition_variable::__do_timed_wait(std::__1::unique_lock<std::__1::mutex>&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > >) + 93
3   com.apple.JavaScriptCore          0x000000010f1504e5 std::__1::cv_status std::__1::condition_variable::wait_until<std::__1::chrono::steady_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > >(std::__1::unique_lock<std::__1::mutex>&, std::__1::chrono::time_point<std::__1::chrono::steady_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > > const&) + 117
4   com.apple.JavaScriptCore          0x000000010f1503af std::__1::cv_status std::__1::condition_variable_any::wait_until<std::__1::unique_lock<bmalloc::Mutex>, std::__1::chrono::steady_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > >(std::__1::unique_lock<bmalloc::Mutex>&, std::__1::chrono::time_point<std::__1::chrono::steady_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > > const&) + 95
5   com.apple.JavaScriptCore          0x000000010f14f0b5 bmalloc::Scavenger::threadRunLoop() + 261
6   com.apple.JavaScriptCore          0x000000010f14e7f9 bmalloc::Scavenger::threadEntryPoint(bmalloc::Scavenger*) + 9
7   com.apple.JavaScriptCore          0x000000010f150197 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (*)(bmalloc::Scavenger*), bmalloc::Scavenger*> >(void*) + 39
8   libsystem_pthread.dylib           0x00007fff735c02eb _pthread_body + 126
9   libsystem_pthread.dylib           0x00007fff735c3249 _pthread_start + 66
10  libsystem_pthread.dylib           0x00007fff735bf40d thread_start + 13

Thread 13:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 14:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 15:: Dispatch queue: com.apple.queue.shared.concurrent (QOS: UTILITY)
0   libsystem_kernel.dylib            0x00007fff7350127e semaphore_timedwait_trap + 10
1   libdispatch.dylib                 0x00007fff7337fc99 _dispatch_sema4_timedwait + 76
2   libdispatch.dylib                 0x00007fff73380378 _dispatch_semaphore_wait_slow + 58
3   libswiftDispatch.dylib            0x00007fff72ecc51f OS_dispatch_semaphore.wait(wallTimeout:) + 15
4   libswiftDispatch.dylib            0x00007fff72edaf89 OS_dispatch_semaphore.wait(timeout:) + 9
5   com.apple.NewsUI2                 0x000000010b87ae92 0x10b70a000 + 1511058
6   com.apple.NewsUI2                 0x000000010b8782f3 0x10b70a000 + 1499891
7   com.apple.news                    0x0000000108e7a2b4 0x108a83000 + 4158132
8   com.apple.news                    0x0000000108e79d1d 0x108a83000 + 4156701
9   com.apple.news                    0x0000000108b37489 0x108a83000 + 738441
10  com.apple.news                    0x0000000108b35567 0x108a83000 + 730471
11  com.apple.newscore                0x000000010c233fa1 -[FCFeedViewportExpandGapOperation operationWillFinishWithError:] + 912
12  com.apple.newscore                0x000000010c20df42 -[FCOperation _finishOperationWithError:] + 935
13  com.apple.newscore                0x000000010c20db85 -[FCOperation _finishedPerformingOperationWithError:] + 305
14  com.apple.newscore                0x000000010c20da1a -[FCOperation finishedPerformingOperationWithError:] + 86
15  com.apple.newscore                0x000000010c22dbd3 __52-[FCFeedViewportExpandGapOperation performOperation]_block_invoke + 666
16  com.apple.newscore                0x000000010c291be6 -[FCFeedViewportExpandGroupGapOperation operationWillFinishWithError:] + 161
17  com.apple.newscore                0x000000010c20df42 -[FCOperation _finishOperationWithError:] + 935
18  com.apple.newscore                0x000000010c20db85 -[FCOperation _finishedPerformingOperationWithError:] + 305
19  com.apple.newscore                0x000000010c20da1a -[FCOperation finishedPerformingOperationWithError:] + 86
20  com.apple.newscore                0x000000010c260619 -[FCFeedViewportExpandGroupGapOperation performOperation] + 3655
21  com.apple.newscore                0x000000010c2063f3 -[FCOperation _startIfNeeded] + 1020
22  com.apple.newscore                0x000000010c205eeb -[FCOperation start] + 45
23  com.apple.newscore                0x000000010c225110 -[FCFeedViewportExpandGapOperation performOperation] + 2202
24  com.apple.newscore                0x000000010c2063f3 -[FCOperation _startIfNeeded] + 1020
25  com.apple.newscore                0x000000010c205eeb -[FCOperation start] + 45
26  com.apple.news                    0x0000000108b34cd0 0x108a83000 + 728272
27  com.apple.newscore                0x000000010c2063f3 -[FCOperation _startIfNeeded] + 1020
28  com.apple.newscore                0x000000010c205eeb -[FCOperation start] + 45
29  com.apple.news                    0x0000000108b0272a 0x108a83000 + 522026
30  com.apple.newscore                0x000000010c2063f3 -[FCOperation _startIfNeeded] + 1020
31  com.apple.newscore                0x000000010c205eeb -[FCOperation start] + 45
32  com.apple.news                    0x0000000108b611f7 0x108a83000 + 909815
33  com.apple.newscore                0x000000010c2063f3 -[FCOperation _startIfNeeded] + 1020
34  com.apple.newscore                0x000000010c205eeb -[FCOperation start] + 45
35  com.apple.news                    0x0000000108cc864c 0x108a83000 + 2381388
36  com.apple.newscore                0x000000010c2063f3 -[FCOperation _startIfNeeded] + 1020
37  com.apple.newscore                0x000000010c205eeb -[FCOperation start] + 45
38  com.apple.Foundation              0x00007fff496c3197 __NSOQSchedule_f + 227
39  libdispatch.dylib                 0x00007fff7338acea _dispatch_block_async_invoke2 + 83
40  libdispatch.dylib                 0x00007fff7337f63d _dispatch_client_callout + 8
41  libdispatch.dylib                 0x00007fff73381de6 _dispatch_continuation_pop + 414
42  libdispatch.dylib                 0x00007fff733814a3 _dispatch_async_redirect_invoke + 703
43  libdispatch.dylib                 0x00007fff7338d3bc _dispatch_root_queue_drain + 324
44  libdispatch.dylib                 0x00007fff7338db46 _dispatch_worker_thread2 + 90
45  libsystem_pthread.dylib           0x00007fff735bf6b3 _pthread_wqthread + 583
46  libsystem_pthread.dylib           0x00007fff735bf3fd start_wqthread + 13

Thread 16:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 17:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 18:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib            0x00007fff7350122a mach_msg_trap + 10
1   libsystem_kernel.dylib            0x00007fff7350176c mach_msg + 60
2   com.apple.CoreFoundation          0x00007fff47408e6d __CFRunLoopServiceMachPort + 327
3   com.apple.CoreFoundation          0x00007fff474083da __CFRunLoopRun + 1619
4   com.apple.CoreFoundation          0x00007fff47407b35 CFRunLoopRunSpecific + 459
5   com.apple.CFNetwork               0x00007fff4636e380 -[__CoreSchedulingSetRunnable runForever] + 210
6   com.apple.Foundation              0x00007fff4967f6d2 __NSThread__start__ + 1194
7   libsystem_pthread.dylib           0x00007fff735c02eb _pthread_body + 126
8   libsystem_pthread.dylib           0x00007fff735c3249 _pthread_start + 66
9   libsystem_pthread.dylib           0x00007fff735bf40d thread_start + 13

Thread 19 Crashed:: Dispatch queue: com.apple.root.user-initiated-qos
0   com.apple.CoreImage               0x00007fff47ef934e CI::GLContext::init() + 122
1   com.apple.CoreImage               0x00007fff47ef8714 CI::GLContext::GLContext(CI::GLContext::ShareContextInfo, CGColorSpace*, CGColorSpace*, CI::PixelFormat, bool, unsigned long, bool, bool) + 56
2   com.apple.CoreImage               0x00007fff47ef8380 +[CIContext(Internal) internalContextWithCGLContext:pixelFormat:options:] + 1282
3   com.apple.CoreImage               0x00007fff47ed026f -[CIContext initWithOptions:] + 1126
4   com.apple.CoreImage               0x00007fff47f5c3ac +[CIContext contextWithOptions:] + 50
5   com.apple.UIKitCore               0x000000010d528971 -[UIImage drawInRect:blendMode:alpha:] + 1285
6   com.apple.TeaUI                   0x000000010b45ce53 0x10b39d000 + 786003
7   com.apple.NewsFeed                0x000000010aef3c24 0x10ad8e000 + 1465380
8   com.apple.NewsFeed                0x000000010aef2653 0x10ad8e000 + 1459795
9   com.apple.NewsFeed                0x000000010aef2513 globalinit_33_5367A6ABDD88C481608153529FC50473_func28 + 19
10  libdispatch.dylib                 0x00007fff7337f63d _dispatch_client_callout + 8
11  libdispatch.dylib                 0x00007fff73380d4c _dispatch_once_callout + 20
12  libswiftCore.dylib                0x00007fff72e057e9 swift_once + 25
13  com.apple.NewsFeed                0x000000010ae5af29 0x10ad8e000 + 839465
14  com.apple.NewsFeed                0x000000010affa7cd 0x10ad8e000 + 2541517
15  com.apple.NewsFeed                0x000000010affd785 0x10ad8e000 + 2553733
16  com.apple.NewsFeed                0x000000010affd760 0x10ad8e000 + 2553696
17  com.apple.TeaTemplate             0x00000001139224a0 0x113912000 + 66720
18  com.apple.TeaTemplate             0x0000000113922f45 0x113912000 + 69445
19  com.apple.TeaTemplate             0x0000000113922d41 0x113912000 + 68929
20  com.apple.TeaTemplate             0x0000000113947515 0x113912000 + 218389
21  com.apple.TeaTemplate             0x000000011393eac5 0x113912000 + 182981
22  com.apple.TeaTemplate             0x0000000113922e1e 0x113912000 + 69150
23  com.apple.TeaTemplate             0x000000011393eac5 0x113912000 + 182981
24  com.apple.TeaTemplate             0x000000011393eac5 0x113912000 + 182981
25  com.apple.TeaTemplate             0x000000011393eac5 0x113912000 + 182981
26  com.apple.TeaTemplate             0x00000001139440c6 0x113912000 + 204998
27  com.apple.TeaTemplate             0x0000000113943e6c 0x113912000 + 204396
28  com.apple.NewsFeed                0x000000010aff981b 0x10ad8e000 + 2537499
29  com.apple.NewsFeed                0x000000010affaf05 0x10ad8e000 + 2543365
30  com.apple.NewsFeed                0x000000010b16dbb9 0x10ad8e000 + 4062137
31  com.apple.NewsUI2                 0x000000010b94692c 0x10b70a000 + 2345260
32  com.apple.NewsUI2                 0x000000010b9461ff 0x10b70a000 + 2343423
33  com.apple.NewsUI2                 0x000000010b94c940 0x10b70a000 + 2369856
34  com.apple.TeaUI                   0x000000010b4e82ab 0x10b39d000 + 1356459
35  com.apple.TeaUI                   0x000000010b4e9dd1 0x10b39d000 + 1363409
36  com.apple.TeaUI                   0x000000010b3bc1d0 0x10b39d000 + 127440
37  libdispatch.dylib                 0x00007fff7337e5f8 _dispatch_call_block_and_release + 12
38  libdispatch.dylib                 0x00007fff7337f63d _dispatch_client_callout + 8
39  libdispatch.dylib                 0x00007fff7338d509 _dispatch_root_queue_drain + 657
40  libdispatch.dylib                 0x00007fff7338db46 _dispatch_worker_thread2 + 90
41  libsystem_pthread.dylib           0x00007fff735bf6b3 _pthread_wqthread + 583
42  libsystem_pthread.dylib           0x00007fff735bf3fd start_wqthread + 13

Thread 20:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 21:
0   libsystem_pthread.dylib           0x00007fff735bf3f0 start_wqthread + 0

Thread 19 crashed with X86 Thread State (64-bit):
  rax: 0x006000200000e300  rbx: 0x0000000000000000  rcx: 0xff80008800000003  rdx: 0xffbffe0000000000
  rdi: 0x001ffe2000000000  rsi: 0xfffffff000000001  rbp: 0x000070000d82c5c0  rsp: 0x000070000d82c5a0
   r8: 0x0000a53ba005a070   r9: 0x0000000000000000  r10: 0x0000000100000000  r11: 0x000060000026a850
  r12: 0x00007fd96775c590  r13: 0x000060000113e460  r14: 0x00006000022754d0  r15: 0x0000000000000000
  rip: 0x00007fff47ef934e  rfl: 0x0000000000010202  cr2: 0x0000000000000000
 
Logical CPU:     1
Error Code:      0x00000004
Trap Number:     14
 
My MBP 2010 15" seems to have issues with trackpad/magic mouse 1. It lags/stutters during high CPU usage (e.g. when mdworker is churning away). Even under low CPU usage, the acceleration curves seem to be way off and i keep missing the target (perhaps this could be a symptom of the lag)

Started with 10.14.5. It was fine on 10.14.4 and earlier. Same issue with a new user account and magic mouse. Maybe something's up with USB

Went back to 10.14.2 fixed it and everything is smooth again
 
Last edited:
Flacko said:
The OTA update ( over the air) is only available in preferences if you have an APFS formatted drive. Click on preferences and you will see software update. It will show you if it has any updates. Right click on drive and select info. It will tell you what format the drive is using.
You will know if you carried out a ROM update for APFS as that is a specific operation that dosdude1 has outlined on page 1. If you have not got an APFS ROM then you need to use the APFS patch. You normally can tell if you have the patch as you get some scrolling text during startup. You only need this if your drive is formatted APFS. If your drive is formatted HFS+ then you do not need the APFS patch but you will not get the OTA update. In which case, boot with the updated patcher usb and install 14.5 over the top of your present system. When the final boot happens boot back into the usb and apply the patches.
Click to expand...
Yes, I do have the scrolling text, and I choose that APFS when formatting and fresh installing 10.14.4. But what I understand is that as my SSD is "already" with APFS file system, I have to "uncheck" that feature when applying the patch after updating to 14.5?
 
vwranger said:
mbp7,1 mid2010 running 10.14.4 on filevault-enabled apfs volume with dosdude1 patcher installed (1.3.0 at the time when i installed it, probably self-updated since then):

i have probably done something very wrong (at least did not understand the instruntions) and allowed macos to begin installing 10.14.5 - it ran until it needed to reboot and then never booted back, keeping on rebooting on my every attempt.

1) am i still able to repair it? and roll 10.14.5 over it? or time to grab my time machine drive?
2) what is a proper way to install an OS update with patcher-installed OS?
3) i heard i no longer have recovery partition - does it mean i need to boot from patcher usb stick?

thanks in advance.
Click to expand...

took me a while to realize what exactly i did and what i should really do :)

i think i have repaired it - by creating a 1.3.2 usb stick, booting from it, mounting the drive since it is encrypted, installing 10.14.5 into existing partition, reboot from usb stick again, mount the drive, apply the patch, reboot again - all worked well, and i do not seem to see graphics artifacts, slowness and so on that i have been seeing with 1.3.0 + 10.14.4 after installing legacy graphics driver update last night.

cheers.
sergey.
 
upipes said:
Yes, I do have the scrolling text, and I choose that APFS when formatting and fresh installing 10.14.4. But what I understand is that as my SSD is "already" with APFS file system, I have to "uncheck" that feature when applying the patch after updating to 14.5?
Click to expand...
It looks like you are using the APFS patch so you must continue to use it - so when you select the drive during the post install patch the patcher will automatically select the APFS patch and you must leave it ticked (selected). Only if you have the ROM update is there is no need to select the APFS patch. From what you have said I do not think you have the APFS ROM. However, as your disk is APFS you should have had the OTA update in preferences.
 
@0403979 Your macOS Patcher seems to be not working on my MacBook5,1. After installing and patching (even a fresh install), it creates a chain of errors (can be seen in verbose mode) and the machine refuses to boot.
 
Minh_Ton said:
@0403979 Your macOS Patcher seems to be not working on my MacBook5,1. After installing and patching (even a fresh install), it creates a chain of errors (can be seen in verbose mode) and the machine refuses to boot.
Click to expand...
What version of macOS and what disk format did you use? Please attach a picture of the errors you get.
 
makima said:
so reinstall using the patcher once again?
Click to expand...

Yes, possibly using the last patcher version with the last 10.14.5 Mojave installer, and reinstalling over your current volume doesn't delete your personal datas.

Probably after reinstallation completes, you will need to re-apply the Post-Install patches for your machine.
 
Flacko said:
It looks like you are using the APFS patch so you must continue to use it - so when you select the drive during the post install patch the patcher will automatically select the APFS patch and you must leave it ticked (selected). Only if you have the ROM update is there is no need to select the APFS patch. From what you have said I do not think you have the APFS ROM. However, as your disk is APFS you should have had the OTA update in preferences.
Click to expand...
Yes, I had the update in preferences as you said. I unchecked the APFS box in the "after update patch" and now I'm running 10.14.5. (it seems I do have that ROM you 're talking about)
Thanks for your help!

PD: As I usually edit with Final Cut Pro, I have to say that I don't have any advance in performance, after upgrading my video card. Many users are reporting better performance than mine on similar hardware setups. I'm 100% slower than when I had my 1Gb Ati 5770. Now, with a flashed 2Gb GTX680 the experience is still worse... Do you use FCP?
 
upipes said:
Yes, I had the update in preferences as you said. I unchecked the APFS box in the "after update patch" and now I'm running 10.14.5. (it seems I do have that ROM you 're talking about)
Thanks for your help!

PD: As I usually edit with Final Cut Pro, I have to say that I don't have any advance in performance, after upgrading my video card. Many users are reporting better performance than mine on similar hardware setups. I'm 100% slower than when I had my 1Gb Ati 5770. Now, with a flashed 2Gb GTX680 the experience is still worse... Do you use FCP?
Click to expand...
Yes, you must have the APFS ROM as otherwise the system would not recognise your disk without the patch. You should also now not have the scrolling text during startup.
Unfortunately I do not run FCP so cannot advise you there. It does seem strange that the GTX680 is running slower for you than the 5770 as the 680 is a much more capable card. Did you try using the display port?
 
0403979 said:
What version of macOS and what disk format did you use? Please attach a picture of the errors you get.
Click to expand...

Well, I cloned the OS back using the backup disk. The macOS version is 10.14.5 and my disk is APFS (APFS ROM). The error is: After patching, I stuck in the middle of the progress bar as well as a spinning circle under it.
 
Flacko said:
You should also now not have the scrolling text during startup.
Click to expand...
The scrolling text is still here! why it shouldn't be? I'm trying to upload a video that I recorded with my phone, in order to show you a complete start up but I'm not allowed by this forum or other unknown reason (video format, size, ???)
I enclose a picture about the post install tool, after installing 10.14.5
As you suggested, I unchecked the APFS box, as I already had this done in 10.14.4... but, what if I check it and apply the patch?
As you said that I should not have the scrolling test on this version, do I guess that this new patch it would overwrite the old one, with the "non scrolling test" benefit?
Or if I check it, will I go into troubles?
 

Attachments

  • IMG_4145.JPG
    IMG_4145.JPG
    4.3 MB · Views: 160
Last edited:
99% successful upgrade of MacBook Pro (17-inch, Early 2008) MacBookPro4,1 from 10.14.3 to 10.14.5 using freshly downloaded macOS Mojave Patcher 1.3.2 on USB flash drive to download fresh copy of Mojave 10.14.5. Updated via System Preferences: Software Update on MacBookPro4,1 then ran Post Install Patches from Mojave Patcher USB to finalize. Amazing !!!

Chess & Flurry screensaver work fine.

News+ works for a while then crashes.

https://forums.macrumors.com/members/669685/ Only remaining issue is the CCFL backlight on this 17" MacBookPro4,1 doesn't work. Do I have to re-run your CCFL Backlight Control Patch (bkltpatch10.14.2 referenced in post #11156) that I successfully ran previously following my 10.14.2 installation? Or do I need an updated bkltpatch10.14.5 for macOS 10.14.5 ?

macOS 10.14.5 on 17" MBP4,1.png
 
Last edited:
Minh_Ton said:
Well, I cloned the OS back using the backup disk. The macOS version is 10.14.5 and my disk is APFS (APFS ROM). The error is: After patching, I stuck in the middle of the progress bar as well as a spinning circle under it.
Click to expand...
What version of the patcher did you use?
 
0403979 said:
Try patching with the -v flag to show verbose logs during the patch process and send them to me.
Click to expand...

Oh... Seems like I erased my patched USB... Will create a new one tomorrow...

EDIT: I only have the one with the old version of your macOS Patcher. However, the old version works fine. The machine was able to boot. Maybe there is an error somewhere.
 
Do you experience: The scrolling text is still here! why it shouldn't be?
Try this: Go to System Preferences --> Startup Disk --> select your Mac Startup Disk and restart without the scrolling text upon startup.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back