macOS 10.14 Mojave on Unsupported Macs Thread

[BookEmDanno]

I did the post install patches after the update didn't work and even tried installing the software patch from the post install updates from High Sierra so yeah I would wait until the firmware updates can be bypassed

OK, Thank You. I will wait.

 

[MacUnsupported]

tired watching the bar after installing mojave osx 10.14 and using the tool , the fans are full power and i dont know what to do! i USED TO HAVE BEFORE the beta version and it was working really good!

 

[jackluke]

Someone who has familiarity could validate the script and follow this step by step to automate properly at startup.

https://stackoverflow.com/questions...-off-or-restart-on-mac-os-x/27102949#27102949

I did tried something similar but hasn't worked properly, anyway I consider that procedure a bit invasive, but the most invasive is the one who suggested to rename the sbin shutdown unix exec using a custom shutdown binary, but I have to admit, an amazing idea after all.

 

[TimothyR734]

New File (script)
[doublepost=1537960700][/doublepost]I was able to do it automatically when I logged in.

Just added as per the screenshot.

Nice

View attachment 789020 '-)

Thanks will test it out

 

[ASentientBot]

How does it even run on plastic MacBooks? You’re better off on an older version like Mavericks, El Capitan or Sierra since the performance just can’t be good on a machine that old which wasn’t fast even when it was brand new.

You're wrong. I'm using Mojave every day on my MacBook7,1 and it runs perfectly well. Granted, I put in a SSD and upgraded the RAM. But this system is far from obsolete. And that is why this thread exist.

 

[TimothyR734]

tired watching the bar after installing mojave osx 10.14 and using the tool , the fans are full power and i dont know what to do! i USED TO HAVE BEFORE the beta version and it was working really good!

did you install the post install patches with the Mojave patcher

 

[16v]

did you accidentally install the 10.14.1

No...

Installed it using dosdude s patcher via usb stick.
And checked it after installing and patching. 391. So this is official release?

After booting first time, i re-installed all patches.
Then this error.

 

[MacUnsupported]

Yes i followed doedude video instructions ! i have an imac 10.1 and i install the patches! now my machine cant load the macosx !
[doublepost=1537981816][/doublepost]

did you install the post install patches with the Mojave patcher

Yes i followed doedude video instructions ! i have an imac 10.1 and i install the patches! now my machine cant load the macosx ! Ι posted a pic
[doublepost=1537982712][/doublepost]I followed all the instructions and i there was a problem with the proccess! it show that the bar is full but still loading and the fans are in full power!

 

[webg3]

No...

Installed it using dosdude s patcher via usb stick.
And checked it after installing and patching. 391. So this is official release?

After booting first time, i re-installed all patches.
Then this error.

in my case, only worked Patcher 1.2.0 (10.14 final)

 

[16v]

???
It worked!
It booted one time.

Then i re installed patches- game over.

 

[varad]

I have the same machine, I faced the same issue initially and the solution was to reformat with APFS instead of APFS(encrypted) ,try this it should work, however facetime camera is not working for me.
[doublepost=1537962845][/doublepost]

Will you be able to send me the .kext plz and how to rebuild kextcache? thanks for your help

Hi, Nope, didn't do any of the sort as using APFS is for those who used a patched macOS high sierra. (Or so was described in the directions of the mojave patch)
For me I just followed the directions.. thats all.

 

[TimothyR734]

No...

Installed it using dosdude s patcher via usb stick.
And checked it after installing and patching. 391. So this is official release?

After booting first time, i re-installed all patches.
Then this error.

you might try resetting the pram by holding down the command, option P and R buttons while booting up

 

[pkouame]

(LightMode v2)

Fixed bug Dock after reboot

(included the script in the Startup Items)


@dosdude1 @ASentientBot @jackluke @TimothyR734 @pkouame

Cool. This is reduce transparency in a script?

 

[16v]

you might try resetting the pram by holding down the command, option P and R buttons while booting up

Nope... dont help...

I had this issue while updating to last PB too.

 

[webg3]

Cool. This is reduce transparency in a script?

Yes, but it's not good enough to start the login, I need a more clinical look, so I marked all of you.

 

[lullabri]

I have the same machine, but iSight camera doesn´t work on FaceTime.
[doublepost=1537978843][/doublepost]
My iSight camera doesn't work on FaceTime. Should it?

iMac 21.5 late 2009. Same problem. Only iSight camera doesn't work. Any solution?

 

[jackluke]

Yes, but it's not good enough to start the login, I need a more clinical look, so I marked all of you.

I just tried your binary applescripts, LightMode-v1 and LightMode-v2, it seems v1 works too, but both lack "Notification Center" transparency, in my opinion that gives a better overall look, not only the Dock and Spotlight.

 

[varad]

I just tried your binary applescripts, LightMode-v1 and LightMode-v2, it seems v1 works too, but both lack "Notification Center" transparency, in my opinion that gives a better overall look, not only the Dock and Spotlight.

Hi, I also tried the script and I have the same findings. Can you concise all of the methods to semi-fix Light Mode in one reply please?

Would be helpful for people(like me) are trying a lot of things.

 

[jackluke]

Hi, I also tried the script and I have the same findings. Can you concise all of the methods to semi-fix Light Mode in one reply please?

Would be helpful for people(like me) are trying a lot of things.

You could try my comfortless method on page 279 , it won't work as login item but will give much customised control from Terminal.

 

[webg3]

You could try my comfortless method on page 279 , it won't work as login item but will give much customised control from Terminal.

Here is a dirty correction.

What I did was repeat the same lines with a pause, it worked.


#!/bin/bash
echo “Reduce Transparency of Menus and Finder, keep the Dock transparent.”
# Run on.
defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight
defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight

kill `ps -A | grep -w Terminal.app | grep -v grep | awk '{print $1}'`
echo "Done!"

 

[varad]

Here is a dirty correction.

What I did was repeat the same lines with a pause, it worked.


#!/bin/bash
echo “Reduce Transparency of Menus and Finder, keep the Dock transparent.”
# Run on.
defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight
defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight

kill `ps -A | grep -w Terminal.app | grep -v grep | awk '{print $1}'`
echo "Done!"

I think just doing :

defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight

Should work.

 

[webg3]

I think just doing :

defaults write com.apple.universalaccess reduceTransparency -bool false
killall Finder
killall Dock
killall NotificationCenter
sleep 3
defaults write com.apple.universalaccess reduceTransparency -bool true
killall Finder
killall Spotlight

Should work.

It works, but not when you start with the system, it loses the transparency of the Dock and NotificationCenter

Only when I repeat the script that works, at least for me.

 

[OGNerd]

How does it even run on plastic MacBooks? You’re better off on an older version like Mavericks, El Capitan or Sierra since the performance just can’t be good on a machine that old which wasn’t fast even when it was brand new.

Because the machines are capable. Mojave runs admirably on my white polycarbonate 2009 MacBook 5,2.

 

[pkouame]

Yes, but it's not good enough to start the login, I need a more clinical look, so I marked all of you.

As far as reduce transparency via command line, what about @jackluke 's version/approach?

I have a more involved approach that cuts transparency at the AppKit l(Cocoa's GUI) level - leaving Dock and other panels that implement their own transparency alone (not as system wide as the accessibility setting(s) which is like turning the master switch OFF).
[doublepost=1537987509][/doublepost]

Because the machines are capable. Mojave runs admirably on my white polycarbonate 2009 MacBook 5,2.

Yes, the fact that our old clunkers are running even better on these new OSes (IMHO) means 1) lots of bloat and bugs in old OSes 2) still quite a bit of headroom with the old logic boards...Good news for us.

 

[webg3]

As far as reduce transparency via command line, what about @jackluke 's version/approach?

I have a more involved approach that cuts transparency at the AppKit l(Cocoa's GUI) level - leaving Dock and other panels that implement their own transparency alone (not as system wide as the accessibility setting(s) which is like turning the master switch OFF).

After restarting the system, it loses its configuration, so its approach is more interesting, but the only thing that matters with transparency is the Dock and NotificationCenter, at least for me.