Got a tip for us?
Let us know
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
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Hi, after rebooting (installing beta8 update) i had a this screen, what can I do now?
did you repatch using post installer and force reboot. thats what I did after installing new update via software update
Known issue, or your Machine ID isn't on the platform support plist, or the no_compat_check has been overridden by the fresh installation upgrade.
To fix try follow this step:
booting from High Sierra Recovery HD or Mojave USB Installer launch Terminal and type:
csrutil disable
nvram boot-args="-v -no_compat_check"
reboot
if you for some reason don't like the verbose mode and prefer to see only the Apple loading logo, drop the "-v" and leave only "-no_compat_check"
Last edited:
Thanks for the reply, unfortunately I decided to save a few bucks and go with two GTX 660 2GBs for both of my machines, I got two 660s for the price of one 680, I thought they would work fine for my needs for being Kepler cards, but both rgwoehr & saudor have pointed out that there is problem with 650ti/660/660ti cards with the VRAM Saturation since 10.13 High Sierra.
Hi, after rebooting (installing beta8 update) i had a this screen, what can I do now?
Did you reboot from the USB installer and perform the Post-Install patches for you particular MBP model?
Did you apply the post install patches from the Mojave PatcherHi, after rebooting (installing beta8 update) i had a this screen, what can I do now?
Yes, but after instaling the update the variable "-no_compat_check" has been overridden by the fresh installation upgrade.
I follow jackluke's instruction and its work!
That's pretty much what I do every time. I posted a tutorial for a completely manual patch a while ago that doesn't involve a bootable USB at all. You can run the patched OSInstall.mpkg directly from High Sierra and install it to a certain partition. Don't you remember us talking about this like 200 pages ago?
[doublepost=1535149414][/doublepost]you can probably use the tool from Insanelymac, it downloads the current (Mojave) OS and creates special InstallESD. I myself can not use it, I'm not really looking through what exactly this tool (terminal script) does exactly. You have more idea, maybe it helps you.
Hey - had a second to dig a little deeper in the new Mojave Finder. Did you notice that Mojave Finder has an extra NSVisualEffectView? It is sandwiched right after the initial (and all-encompassing) NSThemeFrame.That's pretty much what I do every time. I posted a tutorial for a completely manual patch a while ago that doesn't involve a bootable USB at all. You can run the patched OSInstall.mpkg directly from High Sierra and install it to a certain partition. Don't you remember us talking about this like 200 pages ago?
Virtualization? You can run most any Windows in a VM on macOS, this isn't news. But very nice!
These EEPROMs are less than a $1 each on eBay out of Hong Kong.
So even if the patch messes up, the fix is not expensive!
So even if the patch messes up, the fix is not expensive!
I haven't had a chance to look at Finder in any kind of detail. That's very interesting! But why are you focusing on Finder? It's not a Finder-specific thing. Any app that uses the sidebar or appearanceBased or light material will have the grey appearance.
It is made with a electron app I found it on softpedia 125 mb download about 450 mb expanded
Oh not focusing on Finder per se. It's just a good use case, right? A core app (from many) to test...
Per our previous discussions, yes it is systemic and OS wide (so obviously a framework as we suspect). Here's another tid bit, you'll find interesting:
I disabled metal on my metal-supported card (pro 3.1 + GTX 680) and got Dark mode to glitch - the same way it does in Light mode. So it's definitely at the display framework +OpenGL framework. I think I eliminated for good the possibility of this being an AppKit or app bug. Good news. So back to OpenGL calls. I think NSVisualEffectView (as we were positing) is a red herring. It's at even a lower level.
By the way, to display metal processing on a metal supported card:
1. sudo defaults write /Library/Preferences/com.apple.CoreDisplay useMetal -boolean no
2. sudo defaults write /Library/Preferences/com.apple.CoreDisplay useIOP -boolean no
3. restart
Since the MBA 13" mid-2011 supports HS, presumably it gets the genuine Apple APFS boot ROM when installing HS and therefore does not need the dosdude1 APFS boot ROM patch for Mojave. Or is this faulty logic?
nothing better to do at 4:AM in the morning.
Oh, that's good. Want to say that it can be fixed just by patching the OpenGL framework?
My GTX 680 has been rock solid on all Mojave betas (same pro 3.1) And the 660 vs 680 are SO similar (almost the card I bought) Pretty weird. The fact that it glitches over time may indicate some sort of hardware issue. What exactly are the UI glitches you are experiencing? This forum is getting confusing with all the various types of glitches being discussed ...
My GTX 680 has been rock solid on all Mojave betas (same pro 3.1) And the 660 vs 680 are SO similar (almost the card I bought) Pretty weird. The fact that it glitches over time may indicate some sort of hardware issue. What exactly are the UI glitches you are experiencing? This forum is getting confusing with all the various types of glitches being discussed ...
Hi the glitches are caused by improper utilization of VRAM in both High Sierra and now in my case so far in Mojave beta as well.
Folks at tonymacx86 discovered this with High Sierra,
Nvidia GTX 660 Ti Not Working In High Sierra With\without Nvidia Web Drivershttps://www.tonymacx86.com/threads/nvidia-gtx-660-ti-not-working-in-high-sierra-with-without-nvidia-web-drivers.234457/
CoreDisplay and/or OpenGL. May even be kext'able. Reproducing a problem at will means one is close to a solution. Need a nap. Later guys.
[doublepost=1535173175][/doublepost]
Ouch! I remember that. Is upgrading to a 680 an option for you?
O.k. guys heres another couple peculiar situations I'm in, this time its not my Mac Pros but my MacBooks.
13 inch 2008 MacBook 5,1 (Mojave Beta 8) and 13 inch 2009 MacBook Pro 5,5 (Mojave Beta 4) to be exact
I'll start with the first problem, the issue is with the Trackpads on both machines, dosdude has mentioned this problem already before:
Trackpad (MacBook5,2 affected only). Trackpad multi-finger gestures on the MacBook5,2 not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
However I'm getting this on my MB 5,1 & MBP 5,5 is there some thing I did wrong when installing the Mojave Patch? Because the trackpads are simply not detected on the machines. What complicates things for me is that the clicking mechanisms on both trackpads are broken because of battery swelling, so I cant even use them as standard mice. I'm able to tap click on the MBP 5,5 for some reason but not on the MB 5,1. In El Capitan I can go in System Preferences and enable "tap clicking" or "three finger drag" but without the trackpads being detected I cant enable these functions in Mojave.
The Second problem is just specific to the MB 5,1 Keyboard: The 7,8,9,u,i,o,j,k,m and the > keys don't work on the keyboard, when I boot into El Capitan however, the Keys work perfectly fine.
Thank you guys, ill be great full for any input on both these issues. I have attached screenshots from both MB 5,1 and MBP 5,5.
13 inch 2008 MacBook 5,1 (Mojave Beta 8) and 13 inch 2009 MacBook Pro 5,5 (Mojave Beta 4) to be exact
I'll start with the first problem, the issue is with the Trackpads on both machines, dosdude has mentioned this problem already before:
Trackpad (MacBook5,2 affected only). Trackpad multi-finger gestures on the MacBook5,2 not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
However I'm getting this on my MB 5,1 & MBP 5,5 is there some thing I did wrong when installing the Mojave Patch? Because the trackpads are simply not detected on the machines. What complicates things for me is that the clicking mechanisms on both trackpads are broken because of battery swelling, so I cant even use them as standard mice. I'm able to tap click on the MBP 5,5 for some reason but not on the MB 5,1. In El Capitan I can go in System Preferences and enable "tap clicking" or "three finger drag" but without the trackpads being detected I cant enable these functions in Mojave.
The Second problem is just specific to the MB 5,1 Keyboard: The 7,8,9,u,i,o,j,k,m and the > keys don't work on the keyboard, when I boot into El Capitan however, the Keys work perfectly fine.
Thank you guys, ill be great full for any input on both these issues. I have attached screenshots from both MB 5,1 and MBP 5,5.
Attachments
Hello, I was on the verge of installing this patcher on my MacBook 7,1 Core2Duo (A1342). Will it work or not?
Which patcher are you referring to? APFS to the Mojave installer itself ? I think High Sierra is officially supported on that model so apfs should also be supported natively . you might have to upgrade your efi through apple if its not seeing apfs drive
https://www.ifixit.com/Answers/View/464212/SSD+not+detected+by+EFI
As for the Mojave installer Dosudes site does say the installer is supported on the 7,1 MacBook
https://www.ifixit.com/Answers/View/464212/SSD+not+detected+by+EFI
As for the Mojave installer Dosudes site does say the installer is supported on the 7,1 MacBook