macOS 10.14 Mojave on Unsupported Macs Thread

[yeiyei0891]

I thought that when I rebooted it would keep the configuration of these fonts.

Just add the command in LightMode (open it with the Text Editor)
[doublepost=1538047590][/doublepost]Final Cut Pro X gains official eGPU support in macOS Mojave

behind the last line? at the end of everything?

 

[ASentientBot]

You both aren't making any sense. Just some emotional rambling. Of course everyone is gratefull for someone giving effort and doing this but going opensource would be a godsend for this project. Not only it would take the load off the pioneer dosdude1 but also it would speed things up, provide transparency etc. Can't see any disadvantages.

I bothered him about open source on here a few times over the last couple months and he always responded with some non-answer. Perhaps he simply doesn't want to share it. It is his code and it's ultimately up to him. Can we really be that mad about that?

But I agree, it is not ideal for a tool like this to be closed source. Then it's just like a magical fix that you don't understand and can't troubleshoot yourself. cough tonymacx86 It makes it hard to learn for those of us that want to, and honestly if you're not willing to learn a bit, you shouldn't be patching an OS at all. Maybe you don't need to understand all the little details, but in my opinion, when you're messing with your computer, you should always know more or less what you're messing with. Things are bound to go wrong sooner or later, and you'll have to fix that.

I don't know if you know that the majority of patches can be done manually. I never use the patcher. It's really just a collection of fixes found by different users. Perhaps we can make a Google Doc/GitHub repo/whatever documenting the manual steps for each machine. There is no centralized source of information right now other than the patcher's code, which we may or may not get.

Just my 2¢. But don't hate on dosdude1. It's easy to label him as that guy who takes your discoveries, packages them with a GUI, and gets all the credit. But the amount of time and effort that he puts into building and maintaining that thing is massive. And don't forget his other contributions, like the APFS ROM patch. He knows this stuff better than most of us.

I dunno how this message got so long. Sorry...

 

[codesoho]

I guys I have a MID 2010 iMac 27" i7 16GB with ATI Radeon HD 5750.
What problems will I have by installing this Patch on my iMac model ? can they solve? I use the iMac for work, I would not have an iMac that works badly.
Thanks

I have the exact config as yours and Mojave is simply unusable atm. The UI will be slow and glitchy unless you swap the default GPU with something that supports Metal. I've had great experience with Alienware GTX765 so far.

 

[webg3]

behind the last line? at the end of everything?

#!/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
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

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

 

[crazy2]

Many thanks, dosdude1 and company! My flashed to 5,1 Mac Pro warhorse is still in the fight.

 

[ASentientBot]

defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO


a few pages ago someone posted the solution, I would like people to read a little, I know the thread is long, but at least 5 pages to be able to stand.

I somehow missed this until now. It actually helps a lot. Thank you!

 

[Starplayr]

You both aren't making any sense. Just some emotional rambling. Of course everyone is gratefull for someone giving effort and doing this but going opensource would be a godsend for this project. Not only it would take the load off the pioneer dosdude1 but also it would speed things up, provide transparency etc. Can't see any disadvantages.

If it goes open source, I will contribute and possibly have one fork splitting out some options while adding some others.

I think dosdude1’s Branch would still be the #1 area and site will people go to.

 

[Pressure]

Many thanks, dosdude1 and company! My flashed to 5,1 Mac Pro warhorse is still in the fight.

The Mac Pro 5,1 is officially supported though.

 

[jackluke]

I bothered him about open source on here a few times over the last couple months and he always responded with some non-answer. Perhaps he simply doesn't want to share it. It is his code and it's ultimately up to him. Can we really be that mad about that?

But I agree, it is not ideal for a tool like this to be closed source. Then it's just like a magical fix that you don't understand and can't troubleshoot yourself. cough tonymacx86 It makes it hard to learn for those of us that want to, and honestly if you're not willing to learn a bit, you shouldn't be patching an OS at all. Maybe you don't need to understand all the little details, but in my opinion, when you're messing with your computer, you should always know more or less what you're messing with. Things are bound to go wrong sooner or later, and you'll have to fix that.

I don't know if you know that the majority of patches can be done manually. I never use the patcher. It's really just a collection of fixes found by different users. Perhaps we can make a Google Doc/GitHub repo/whatever documenting the manual steps for each machine. There is no centralized source of information right now other than the patcher's code, which we may or may not get.

Just my 2¢. But don't hate on dosdude1. It's easy to label him as that guy who takes your discoveries, packages them with a GUI, and gets all the credit. But the amount of time and effort that he puts into building and maintaining that thing is massive. And don't forget his other contributions, like the APFS ROM patch. He knows this stuff better than most of us.

I dunno how this message got so long. Sorry...

I am enough agree, I also have done until now manual patching, even if mine is simpler cause I rely on Metal supported mac, so I can easily upgrade on APFS, clone without reinstall, un-patch and so on. I like Terminal ways to do "things", but taking a look at the dosdude1's patcher it's a very comfort zone for those who don't care nothing of patching process, everything is there under a mouse click, and the USB Patcher itself acts as an improved RecoveryHD. Anyway I'd advise him into Post-Install to separate the GPUs patches (and some other) distinguishing between Nvidia, AMD etc, and especially you deserve to be mentioned for Nvidia Tesla, C2D and iSight patches into the Mojave Patcher (probably dosdude1 already did), because with your amazing fixes at least 50% of the legacy machines today can boot Mojave with OpenGL QE/CI on Penryn architecture.
[doublepost=1538056894][/doublepost]

#!/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
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO

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

Why you repeat twice the transparency reduction script ? To force more than once?

I guess once is suffice:

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

 

[ASentientBot]

I am enough agree, I also have done until now manual patching, even if mine is simpler cause I entrust on Metal supported mac, so I can easily upgrade on APFS, clone without reinstall, un-patch and so on. I like Terminal ways to do "things", but taking a look at the dosdude1's patcher it's a very comfort zone for those who don't care nothing of patching process, everything is there under a mouse click, and the USB Patcher itself acts as an improved RecoveryHD. Anyway I'd advise him into Post-Install to separate the GPUs patches (and some other) distinguishing between Nvidia, AMD etc, and especially you deserve to be mentioned for Nvidia Tesla, C2D and iSight patches into the Mojave Patcher (probably dosdude1 already did), because with your amazing fixes at least 50% of the legacy machines today can boot Mojave with OpenGL QE/CI on Penryn architecture.

You're right, it is very user friendly and the way he managed to automate the whole process is truly impressive. Open sourcing the patcher is really not necessary, in my opinion. That is his project. He owns it. He can do with it whatever he pleases! Openly documenting what the patcher does, though, would be nice. It would make troubleshooting, manual patching, and future OS patching that much easier...

I wasn't going to go into that, but yeah, it would be nice if he gave credit. Not just to me, but to you, parrotgeek1, Czo, Badruzeus, iphone2g&3gfan, and everyone else who was involved in figuring out these patches. Not just the people who actually wrote the code, but those who figured out the methods too.

What it really comes down to is, we're all in this together. And we will be more successful if we share our knowledge & respect each other

 

[webg3]

Why you repeat twice the transparency reduction script ? To force more than once?

I guess once is suffice:

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

because I apply it during startup and it has not yet started the Dock / Finder so there are no problems, so a second chance is needed.

If the script took at least 5 seconds before starting, after logging in, I think it would solve the problem, so you have the breaks.

 

[FlorisVN]

Im getting, problems with downloading MacOS Mojave Application.
Download goes succesfull, when using Dosdude1 tool, but when i want to use it, it says that its not valid !

How to fix this ?

I have also used dosdude1 high sierra patcher, and get exact same error when download macos high sierra installation..
also not valid..

I download to Applications folder..

What am I doing wrong here ?

 

[crazy2]

The Mac Pro 5,1 is officially supported though.

Albeit many attempts, my Mac Pro 4,1 flashed to 5,1 would not load Mojave. Although the patch tool stated the my Mac Pro supported Mojave and did not require the tool, I used it with a successful load on the 1st time.

 

[16v]

Probably faulty, BT version doesn't matter, I have MM2 working fine with BT 2.1 and BT 4.0 , but I have a doubt are you sure that yours is a MagicMouse1 ?

Check on the web MagicMouse 2 they are identical except the MM1 hasn't a lithium battery, but the design is identical, if yours is not identical to MagicMouse 2 then you don't have a MagicMouse1 but only a simple apple wireless mouse formerly Apple Mighty Mouse Bluetooth

This is why i m asking.
Cause it is normal that it is recognized as apple wireless mouse?

Model no a1296 3vdc is written at the bottom.
It has 2 aa batteries.
And looks like the mm2.

 

[Mikki77]

I'm running successfully Mojave 12.14. Thanks for the great effort!
I have one weird glitch though. iTunes 12.9 does not run some locally stored movies (just still black picture with playhead not moving) in its library. All movies have been transcoded using Handbrake with AppleTV 3 presets. It also seems not an issue of framerate or video size (as also higher framerate movies are fine). Some random movies don't work (always the same ones). They run perfectly fine playing directly in QuickTime X, QuickTime 7 and VLC though! Movie trailers from iTunes store seem all fine as well.

I also tried to delete iTunes 12.9 and installing iTunes 12.6.5 from Sierra (which actually works by using the old library.itl), but the glitches remain the same! Anyone came across the same issue?! Any help?

System is iMac 27" i7 Late 2009 with ATI RADEON HD 4850 512MB and upgraded Airport Broadcom card. Mojave 12.14 (fresh install with data&applications migrated from Sierra).

 

[OGNerd]

Im getting, problems with downloading MacOS Mojave Application.
Download goes succesfull, when using Dosdude1 tool, but when i want to use it, it says that its not valid !

How to fix this ?

I have also used dosdude1 high sierra patcher, and get exact same error when download macos high sierra installation..
also not valid..

I download to Applications folder..

What am I doing wrong here ?

Download it to your Documents or Downloads folder, the patcher will not run properly if the install app is located in the Applications folder.

 

[marcinsf]

This "Mid-2010 GPU issue" is a hardware issue. It needs to be repaired properly, NOT "fixed" via software. I will never implement such fixes in my patcher. I have a video on my YouTube channel here showing what needs to be done to actually fix the issue. On another note, I may consider making the patcher open source... I'm still working out the best way to do so at this time.

Exactly, I’ve done the hardware repair and thoroughly tested before and after repair. The Tantalum capacitor is the culprit typically. A lot of time, effort, tools and $6 capacitor and MBPro 2010 is like new!

 

[Doppelherz]

On my Mac Pro 3.1 Mojave works fine with one small thing:

• The app EyeTV works (32 bit), streams from the archive from the Mac Pro to my iPad, but the usb receiver won´t be found. In the system profiler the receiver is still found without issues.
• Back in High Sierra all is functional.
• USB sticks are still working
• USB Sound Sticks are still working
• iSight is working

Does anybody has an idea? Thanks in advance!
Uli

 

[Jack Ryan]

I'm starting to think that to those who iSight doesn't work, if they don't have a Mac natively supported till HighSierra 10.13.x, so I gamble the idea probably to make isight work they should use very legacy IOUSB*** for example from El Capitan 10.11.x.

My iMac late 2009 (11.1) is HighSierra supported.

 

[TimothyR734]

Wait for the real updater. I am sure the developer ones now are unstable.
[doublepost=1538048181][/doublepost]
There’s really no sense in installing developer betas at this point. We were lucky the previews and betas before the GM were so stable. More than likely Apple is trying new things out in the developer betas and will be unstable.

I agree with you there

 

[jackluke]

My iMac late 2009 (11.1) is HighSierra supported.

but have you tried to replace all the 5 IOUSB***.kext from HighSierra into Mojave /S/L/E/ if you retain HighSierra 10.13.6 copy from there otherwise check here: 5 IOUSB kexts by @TimothyR734

right after it's very important to fix permissions in /S/L/E/ and rebuild the kextcache from Mojave Terminal, it can be done in many ways, here is another:

sudo -s
chown -r 0:0 /S*/L*/E*
chmod -r 755 /S*/L*/E*
kextcache -i /
reboot

to me this fixed everything, if your iSight still won't work I guess there is some third party app that keeps usb hub or camera bus busy.

 

[TimothyR734]

The 2 things I have noticed while booting in versos mode is the APFS.Kext is a much higher version then before and I get a lot of APFS errors

 

[jackluke]

Thank's man... unfortunately this method did not work for me. Mac crashed on reboot and I ran out of options except back to the High Sierra.

Have you fixed booting Mojave with previous methods?

If not, could you post a picture on verbose mode (hold CMD+V at power-on) of your Mojave crash on boot ?

About your bluetooth issue, before find a right fix for your mac you should identify your Bluetooth hardware, you have to do this check from HighSierra open Terminal and type:

system_profiler SPBluetoothDataType

From the result report here only Vendor ID and Product ID
[doublepost=1538066204][/doublepost]

This is why i m asking.
Cause it is normal that it is recognized as apple wireless mouse?

Model no a1296 3vdc is written at the bottom.
It has 2 aa batteries.
And looks like the mm2.

Ok you have MagicMouse1, could you test your MM1 touch features from another Mac or another macOS, and have you upgraded from HighSierra to Mojave or clean install ? You should try a clean install maybe to fix some previous conflicts.

 

[pkouame]

You're right, it is very user friendly and the way he managed to automate the whole process is truly impressive. Open sourcing the patcher is really not necessary, in my opinion. That is his project. He owns it. He can do with it whatever he pleases! Openly documenting what the patcher does, though, would be nice. It would make troubleshooting, manual patching, and future OS patching that much easier...

I wasn't going to go into that, but yeah, it would be nice if he gave credit. Not just to me, but to you, parrotgeek1, Czo, Badruzeus, iphone2g&3gfan, and everyone else who was involved in figuring out these patches. Not just the people who actually wrote the code, but those who figured out the methods too.

What it really comes down to is, we're all in this together. And we will be more successful if we share our knowledge & respect each other

Indeed!
[doublepost=1538067037][/doublepost]

The 2 things I have noticed while booting in versos mode is the APFS.Kext is a much higher version then before and I get a lot of APFS errors

Same here. My APFS boot messages changed. For GM it is the first time I used the most up to date version of the patcher with dude's apfs patch (it is on by default). I don't know if that had anything to do with it.

 

[Blackriton]

I upgraded from High Sierra to Mojavewith dosdude1's patch my Mac Pro 3,1 with a Nvidia 680 GPU Card without any hitch !!!!!!

Everything looks fine and working for now..........but exploration of apps not finished.........

Many thanks for Dosdude1 amazing work and the help of all the others on this forum . Only negative point for me : the ROM patcher didn't work so upgrading 10.14.1 may be more tricky if a new solution is not found.