TimothyR734
macrumors 68030
I noticed if you boot in verbose with the patcher you can see something like this is not compatible with i2018 from patcher 1.2.3 and this is not compatible with 12019 with patcher 1.3.0
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
carlcaulkett
macrumors member
I think I’ve found the answer to the infinite “too many corpses” loop. The steps are:
- Boot onto the USB drive
- Select the Terminal
- Run “cd /Volumes/“HDD NAME”/var/db/caches/opendirectory”
- Then “mv ./mbr_cache ./mbr_cache-old”
- Reboot
Hello to all,
Tried to update a 10.14.4 installation on MacBook Pro 5,2 to ==> 10.14.5 (2)
I booted into verbose mode, after applying the update, and patching, to try do discern why machine booted into dark screen with white cogwheel spinning for few seconds, disappearing, then reappearing; a sure sign of a "infinite" loop.
In verbose mode I've noted specific and repeating pattern - an appleKeystore function crash, followed by window server crash, interlaced with "couldn't unlock window" message. That pattern appeared to be behind the dark screen with "appearing and disappearing" cogwheel.
Just few points to add to the data already presented in this thread regarding the failure of the 10.14.5 update process on unsupported macs.
Hope this may be of help.
Tried to update a 10.14.4 installation on MacBook Pro 5,2 to ==> 10.14.5 (2)
I booted into verbose mode, after applying the update, and patching, to try do discern why machine booted into dark screen with white cogwheel spinning for few seconds, disappearing, then reappearing; a sure sign of a "infinite" loop.
In verbose mode I've noted specific and repeating pattern - an appleKeystore function crash, followed by window server crash, interlaced with "couldn't unlock window" message. That pattern appeared to be behind the dark screen with "appearing and disappearing" cogwheel.
Just few points to add to the data already presented in this thread regarding the failure of the 10.14.5 update process on unsupported macs.
Hope this may be of help.
I read awhile back that there may be issues with 10.14.4. I'm currently at 10.14.3 on my 2008 MacPro and it's working fine. Is it safe to upgrade to 10.14.4?
Also.. I downloaded v1.3.0 of the patcher, but when I have it download the latest MacOS, after it downloads, it crashes the patcher. The Install macOS Mojave is only 22.8MB which isn't big enough. Anyone else notice this?
Also.. I downloaded v1.3.0 of the patcher, but when I have it download the latest MacOS, after it downloads, it crashes the patcher. The Install macOS Mojave is only 22.8MB which isn't big enough. Anyone else notice this?
Last edited:
TimothyR734
macrumors 68030
I download 10.14.4 earlier this evening and its only 6.0 gb
Attachments
jackluke
macrumors 68040
Do you want an easy way to boot the Mojave .5 beta GUI from an unsupported (Penryn cpu) mac ?
Then next time you update to .5 beta3 , just don't use the Video Patch, the only required patches are IOUSB* kext and telemetry.plugin (Legacy Platform) and you will land to Mojave desktop.
Otherwise if have .5 beta2, use the content from the folder "10145b2" , replace your files inside SLE and the PrivateFrameworks one, then reboot from your target Mojave in single user mode CMD+S and type this:
mount -uw /
nvram boot-args="-no_compat_check"
chown -R 0:0 /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -i /
reboot
at next reboot you'll reach the loginUI.
edit:
"appleKeystore function" crashes very often even on a supported Mojave Mac. So that's not the case.
Last edited:
alphascorp
macrumors 6502
Hello pkouame,
I was as surprised as you and I asked myself a lot of questions about this version 18E2034 which is obviously not the same as all of you, I simply downloaded on March 26 with the app store under 10.14.3. I used the patch of dosdue1 1.3.0 successfully and then installed this version on my MBP5,3 and my iMac 8.1 without any problems, I found that on these 2 machines 10.14.4 and much more stable than 10.14.3 because under 10.14.3 I regularly had very long starts 3-4 minutes whereas with 10.14.4, 17 small seconds are enough to reach the desktop (I specify that Mojave is installed on SSD Samsung 860 EVO and formatted in HFS +)
Last edited:
avz
Suspended
What about Flurry screensaver, Siri's soundwave and Chess.app? Does it work on your 18E2034 build?
alphascorp
macrumors 6502
Hello avz,
The same as you, Flurry screensaver did not work
Siri had to be repaired by replacing SiriUI.framework
iSight also had to be repaired by replacing IOUSBFamily.kext
Chess.app does not crash but I get an empty black window
News worked under 10.14.3 but not anymore and News + crash like everyone else
However, since getting full transparency (with the replacement of CoreUI and HIToolbox) no more screensaver works
avz
Suspended
Are you saying that after replacing CoreUI and HIToolbox none of your screensavers are working?
TianjinMBP
macrumors newbie
You downloaded the "installer." I have a 2009 MBP and have no problems with .4, but I can't speak for everyone.
Run the Patcher and download the full version from the menu. It's a pretty fast download.
jackluke
macrumors 68040
For Chess.app with GL acceleration use this good workaround by @Larsvonhier Chess app version 3.13 from 10.11.6
It works fine on the "buggy" 10.14.4 .
However I can assure that these "GL issues" don't depend from .3 OpenGL/GPUSupport , the same occur also using .4 OpenGL/GPUSupport .
[doublepost=1555076468][/doublepost]
On my machine replacing CoreUI and HIToolbox don't affect the screensavers, neither caused those "GL side effects". Maybe that build 18E2034 has something different.
Last edited:
BuffyzDead
macrumors 6502
THIS #14142
worked for me
[doublepost=1555078796][/doublepost]
Yes for me. …On three different Mac mini 3.1's Late 2009's
THIS #14142
worked for me
In the end, I believe Onyx cleared prior application states.
If I knew Terminal Commands, I may have been able to do the same
But in my three cases, all three mini's are running reliably
pkouame
macrumors 65816
Ok. Seems like you got a "special" version of 10.14.4 that shipped with 2019 iMacs (according to this article) : https://discussions.apple.com/thread/250270135
Go figure?
[doublepost=1555081886][/doublepost]
I looked at your files for dual gpu (.5b2) and I matched all their versions to stock .5b2 kexts and frameworks the post-install patcher retrogrades (except for GPUWrangler) . So I believe you are assuming someone OTA software updated to .5b2 and post-installed using the latest patcher right ? Otherwise why the need to restore them to stock...If so, OpenGL and GPUSupport are still the .3 versions in this patched configuration.
jackluke
macrumors 68040
No, I have used GPUWrangler, OpenGL and GPUSupport from .4 for 10.14.4 and from .5 for 10.14.5 beta2 .
For single and dual GPUs system you can use the .4 folder for 10.14.4 . This allow using stock .4 OpenGL and GPUSupport.
For single GPUs system you can use the .4 folder also for 10.14.5 beta, this will load Framebuffer too.
From dualGPUs system you can use the .5b2 folder for 10.14.5 beta.
In both cases I don't use NDRVShim.kext, but for single GPU it is loaded correctly I guess.
I attached for mistake the .3 frameworks versions compiled by apple around February 5th, while the right .4 versions are compiled on March 28th and .5 versions are compiled on April 6th.
I have edited my previous attach.
It's very important to chmod/chown/kextcache directly from the Mojave single user mode.
Last edited:
I upgraded to 10.14.4 in my MacPro 3,1 with Metal graphics card and it works well. AFAIK the problem only exists with unsupported graphic cards. If you have a supported GTX 680 or 770 or similar, you should be good to go
Last edited:
Frodotg
macrumors newbie
Hello!!! I made a new patch install ver. 1.3.0 and updated to 10.14.4, then I tried to run the post install patcher and now I cannot run the patcher install, I only get a forbidden sign for the usb drive... Any idea
[doublepost=1555090122][/doublepost]
Hello!!! I made a new patch install ver. 1.3.0 and updated to 10.14.4, then I tried to run the post install patcher and now I cannot run the patcher install, I only get a forbidden sign for the usb drive... Any idea??? thanks!!!
TimothyR734
macrumors 68030
Could be the reason I can't get 10.14.4 to stay up on my iMac think Apple doesn't want the same repeat as last year when the 2018 iMacs and MP came out no one could update to Mojave some bricked theirs
jackluke
macrumors 68040
@pkouame I've tried to compile this: https://github.com/calumr/flurry, adding to Xcode 10.1 the MacOSX10.5 SDK taken from here: https://github.com/phracker/MacOSX-SDKs/releases
then I have removed the ppc, leaving only i386 and adding x86_64 architecture to the build deployment settings, then needed to set
#include <Texture.h> #include <PTypes.h> as "Texture.h" and "PTypes.h"
also trying to target to macOSX 10.6 , but I still get one error about "-fobjc-weak" or "clang: error" can't figure it out.
I wanted to remove the linked OpenGL.framework from the project cause Flurry screensaver also work with only CoreImage rendering.
Tried also to edit the .4 Flurry binary and NOP many GL init and GL functions, but still get the grey screensaver.
I've tried also the edit its Info.plist adding something like this setting bool FALSE:
https://developer.apple.com/documentation/spritekit/skview/requesting_the_opengl_renderer
I found an old already compiled flurry from this original source but of course doesn't supported on these modern macOSs.
As funny workaround (but it is a great work), here is flurry for those who were missing it from 10.14.4 : http://roycurtis.github.io/Flurry-WebGL/
then I have removed the ppc, leaving only i386 and adding x86_64 architecture to the build deployment settings, then needed to set
#include <Texture.h> #include <PTypes.h> as "Texture.h" and "PTypes.h"
also trying to target to macOSX 10.6 , but I still get one error about "-fobjc-weak" or "clang: error" can't figure it out.
I wanted to remove the linked OpenGL.framework from the project cause Flurry screensaver also work with only CoreImage rendering.
Tried also to edit the .4 Flurry binary and NOP many GL init and GL functions, but still get the grey screensaver.
I've tried also the edit its Info.plist adding something like this setting bool FALSE:
https://developer.apple.com/documentation/spritekit/skview/requesting_the_opengl_renderer
I found an old already compiled flurry from this original source but of course doesn't supported on these modern macOSs.
As funny workaround (but it is a great work), here is flurry for those who were missing it from 10.14.4 : http://roycurtis.github.io/Flurry-WebGL/
Last edited:
alphascorp
macrumors 6502
alphascorp
macrumors 6502
I confirm Chess version 3.15 of HighSierra works great under 10.14.4
I just tried Chess version 3.16 of 10.14.3, 10.14.2, 10.14.1 and 10.14, none works.
I also tried Flurry of 10.14.3, 10.14.2, 10.14.1, 10.14, HighSierra 10.13.6 and Elcapitan 10.11.6 none works.
Last edited:
jackluke
macrumors 68040
Ok, just opened from .4 three version of Chess.app all together 3.13, 3.14, 3.15 and they work correctly, so it's only an issue about GL from 3.16 .
Last edited:
pkouame
macrumors 65816
Cool that you tried a rebuild. I never got a chance to, but I'm not sure how current that Flurry code is anyway. I think the calumr/flurry project needs to be updated completely for Xcode 10.2 and 10.14. I'll give it a go to see what I get. However, I'm not sure what that will tell us about OpenGL incompatibilities.