macOS 10.14 Mojave on Unsupported Macs Thread

[16v]

[doublepost=1538066204][/doublepost]

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.

No. No other mac or macos system.
Did a clean install...

 

[TimothyR734]

Indeed!
[doublepost=1538067037][/doublepost]
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.

In a previous post I think its strange I have 4 refi partitions after I upgraded from 10.14 to 10.14.1 and its still there even after I downgraded back to 10.14 and I get a white screen hang for a few mins while booting

 

[0403979]

Wi-Fi and apfs encryption on installers are still broken for me in the latest version of the patcher. I’ve tried my own fix again and it still works. Here’s the file: https://drive.google.com/open?id=1wjLFxXkzNmCQehqYp0L2GRZlQYEx0bDS Perhaps you can implement this. @dosdude1

Maybe each system needs it's own prelinkedkernel? Idk much about this subject but I know my patch works for me and yours don't. @dosdude1

 

[yeiyei0891]

#!/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!"

Now all looks better but 3 small things, i don´t know if this only happens on my Macbook 6,1:

1. Now when the screen is off and click to turn it on it happens a very strange blink.

2. the top bar is not transparent like in other versions? allways is black?

3. The search box in System Preference when is not on focus is ok, but when is on focus the text is not ok:

 

[dosdude1]

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 have strongly considered making the patcher's code public. The main thing I'm worried about, though, if I were to release it, is that somebody will take it, modify it for malicious purposes, and try to distribute it. It does, of course, make modifications to system files. Secondly, I don't like the idea of having untested or unnecessary patches added to it. For example, somebody earlier in this thread mentioned something about adding a "Mid 2010 MacBook Pro GPU Fix" patch to my tool for whatever reason. What obviously was not known by this person is that this "Mid-2010 MacBook Pro GPU issue" is a hardware issue, and that it's not actually an issue with the GPU itself. The actual cause is a failing capacitor on the GPU framebuffer power rail. Lastly, yes, documentation of all the patches included with the tool would be a good idea. I will more than likely write some sort of detailed documentation for it once I have a bit more free time. I'm currently at college, so my time is somewhat limited. Also, I get upwards of around 30 emails asking about some aspect of the patcher every day. I do try to respond to every one of them, which takes quite a bit of time.

 

[webg3]

Now all looks better but 3 small things, i don´t know if this only happens on my Macbook 6,1:

1. Now when the screen is off and click to turn it on it happens a very strange blink.

2. the top bar is not transparent like in other versions? allways is black?
View attachment 789676
3. The search box in System Preference when is not on focus is ok, but when is on focus the text is not ok:
View attachment 789679 View attachment 789680

this fix is for light mode only.

as described in the name itself.

in the dark mode, will work, but with reduced transparency, so you see.

 

[ASentientBot]

I have strongly considered making the patcher's code public. The main thing I'm worried about, though, if I were to release it, is that somebody will take it, modify it for malicious purposes, and try to distribute it. It does, of course, make modifications to system files. Secondly, I don't like the idea of having untested or unnecessary patches added to it. For example, somebody earlier in this thread mentioned something about adding a "Mid 2010 MacBook Pro GPU Fix" patch to my tool for whatever reason. What obviously was not known by this person is that this "Mid-2010 MacBook Pro GPU issue" is a hardware issue, and that it's not actually an issue with the GPU itself. The actual cause is a failing capacitor on the GPU framebuffer power rail. Lastly, yes, documentation of all the patches included with the tool would be a good idea. I will more than likely write some sort of detailed documentation for it once I have a bit more free time. I'm currently at college, so my time is somewhat limited. Also, I get upwards of around 30 emails asking about some aspect of the patcher every day. I do try to respond to every one of them, which takes quite a bit of time.

I understand your concerns about it. Honestly, the patcher itself? I don't really care if it's open sourced or not. If I wrote a useful GUI app, I wouldn't want people stealing it and doing whatever they wanted with it either. But things like the software update patch, NDRVShim, LegacyUSBInjector, and CoreBrightness patcher... The details of the actual modifications are what would really benefit the community to be well documented, publicly. I would be happy to help with some of that if you want!

Sorry about the slightly passive aggressive previous message. Thank you for your response. You're awesome.

 

[dosdude1]

I understand your concerns about it. Honestly, the patcher itself? I don't really care if it's open sourced or not. If I wrote a useful GUI app, I wouldn't want people stealing it and doing whatever they wanted with it either. But things like the software update patch, NDRVShim, LegacyUSBInjector, and CoreBrightness patcher... The details of the actual modifications are what would really benefit the community to be well documented, publicly. I would be happy to help with some of that if you want!

Sorry about the slightly passive aggressive previous message. Thank you for your response. You're awesome.

Ahh, I understand. I definitely agree with you on that. I'll try to get a documentation page up on my site within the next couple weeks or so.

 

[Starplayr]

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.

Do you have a metal Video Card that works with Apple’s Mojave drivers? That would be the only think Apple would block.

 

[BartmanEH]

Answering to myself: the issue is related to TimeMachine.
When launching PatcherTool it probably scan for the available drives in /Volumes and fails (sandbox error) to get the metadata of the TimeMachine network mounted drives. Unmounting this drive and relaunching Patchertool was the solution.

I still have this problem. Patcher only shows Item 1, Item 2 and Item 3--it does not show the external USB key that Disk Utility shows that was erased with Journaled HFS+. Any ideas? I've unmounted all disks leaving only the main disk and the USB key drive. Full disclosure, this is a High Sierra VM.
[doublepost=1538072924][/doublepost]

Ahh, I understand. I definitely agree with you on that. I'll try to get a documentation page up on my site within the next couple weeks or so.

I have always wondered what is behind this statement: "System updates, such as 10.14.1, should install normally if "Software Update Patch" was selected in the macOS Post Install tool,..." How does the Software Update Patch tool work in conjunction with updates done through the MAS? Realtime monitoring and patching of updates done via MAS?

 

[pkouame]

10.4.1 System Update

Ok - worrying about the 10.4.1 system update, I tried it myself on my bookpro 5,3.

TL;DR - it worked

1. Downloaded the 10.14.1 beta utility from the developer site
2. Preferences system update kicked off immediately - downloaded (~1.99Gb I think) - then restarted
3. Got the no entry due to kernel panic of course
4. Applied latest post-install (checked off the APFS Patch just for kicks ?)
5. Rebooted - took a while - but eventually booted right up - Phew!

Observations:

1. APFS boot and verbose messages changed - haven't dug into these
2. In between initial install and post, I booted back up from the patcher stick to dig around and noticed a strange EFI configuration + beaucoup phantom disk images loaded. Disappeared though after successful post-install and reboot. Now my diskutil list looks fine
3. For some reason Apple doesn't have developer release notes for 10.4.1 up. Still trying to figure out what changed. Anyone have any insights into the changes?

 

[PBear.SF]

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

Not always true. I have downloaded the installer to my Applications folder every single time I've run the patcher and it has worked perfectly each time. There must be other, unknown factors that make the Applications folder unworkable on certain Macs or installations.

 

[crazy2]

Do you have a metal Video Card that works with Apple’s Mojave drivers? That would be the only think Apple would block.

The video card specs are:
Chipset Model: AMD Radeon HD 7950
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 3072 MB
Vendor: AMD (0x1002)
Device ID: 0x679a
Revision ID: 0x0000
ROM Revision: 113-E2080C-101
VBIOS Version: 113-C3810100-U01
EFI Driver Version: 01.00.624
Metal: Supported, feature set macOS GPUFamily2 v1

Failed Mojave installer attempts gave the message "installer resources could not be located" with different downloaded Mojave installers, both on upgrades to HS 10.13.6 and fresh installs to ssd.

 

[whaffle]

10.4.1 System Update

Ok - worrying about the 10.4.1 system update, I tried it myself on my bookpro 5,3.

TL;DR - it worked

Does graphics switching still work? Dosdude1 posted a video during the first beta releases and he couldn’t get it to switch between the 9600 and 9400 chips.

 

[Luigi222]

It's repairable, but requires soldering and an EEPROM programmer. I bricked one of my machines during testing, and had to recover it this way.

Just briked my Mac mini 3,1 with the APFS tool, I opended the Mac mini ti check the EEPROM Numbers, choose the right one, Patched it, and now nothing, just beeps a bunch of times and flashes the Light...

Now I nave the added trouble of living in Portugal, meaning that Im screwed because there is no place to fix this thing...

Oh well, next time I’ll just go for a jog instead of messing around with this thing...

 

[Luckygreek]

Not always true. I have downloaded the installer to my Applications folder every single time I've run the patcher and it has worked perfectly each time. There must be other, unknown factors that make the Applications folder unworkable on certain Macs or installations.

Agreed, it was in apps folder & that's where it remains. High Sierra was exactly the same in terms of where App Store determines where to download OS's. Perhaps in some circumstances moving OS to another folder is a workaround.

 

[dosdude1]

The video card specs are:
Chipset Model: AMD Radeon HD 7950
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 3072 MB
Vendor: AMD (0x1002)
Device ID: 0x679a
Revision ID: 0x0000
ROM Revision: 113-E2080C-101
VBIOS Version: 113-C3810100-U01
EFI Driver Version: 01.00.624
Metal: Supported, feature set macOS GPUFamily2 v1

Failed Mojave installer attempts gave the message "installer resources could not be located" with different downloaded Mojave installers, both on upgrades to HS 10.13.6 and fresh installs to ssd.

You need to boot from the patched USB installer, NOT run the "Install macOS Mojave" app.

 

[webg3]

10.4.1 System Update

Ok - worrying about the 10.4.1 system update, I tried it myself on my bookpro 5,3.

TL;DR - it worked

1. Downloaded the 10.14.1 beta utility from the developer site
2. Preferences system update kicked off immediately - downloaded (~1.99Gb I think) - then restarted
3. Got the no entry due to kernel panic of course
4. Applied latest post-install (checked off the APFS Patch just for kicks ?)
5. Rebooted - took a while - but eventually booted right up - Phew!

Observations:

1. APFS boot and verbose messages changed - haven't dug into these
2. In between initial install and post, I booted back up from the patcher stick to dig around and noticed a strange EFI configuration + beaucoup phantom disk images loaded. Disappeared though after successful post-install and reboot. Now my diskutil list looks fine
3. For some reason Apple doesn't have developer release notes for 10.4.1 up. Still trying to figure out what changed. Anyone have any insights into the changes?

We may think that Apple will further modify the system so that unsupported macs are getting more and more distant, but it still supports some 2010 models, so as long as it keeps those models, we will be grateful.

 

[DuncanGarp]

#!/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!"

Is it necessary to terminate Terminal at the end? (bolded on). Thanks.

 

[0403979]

Wi-Fi and apfs encryption on installers are still broken for me in the latest version of the patcher. I’ve tried my own fix again and it still works. Here’s the file: https://drive.google.com/open?id=1wjLFxXkzNmCQehqYp0L2GRZlQYEx0bDS Perhaps you can implement this. @dosdude1

Maybe you can investigate this? I have a MacBook7,1 btw. @dosdude1 Thank you.

 

[Larsvonhier]

Just briked my Mac mini 3,1 with the APFS tool, I opended the Mac mini ti check the EEPROM Numbers, choose the right one, Patched it, and now nothing, just beeps a bunch of times and flashes the Light...

Now I nave the added trouble of living in Portugal, meaning that Im screwed because there is no place to fix this thing...

Oh well, next time I’ll just go for a jog instead of messing around with this thing...

Try to get hold of the Apple EFI-Recovery CD image for your mini, burn it onto CD and try to pre-boot this from internal optical drive.

 

[dosdude1]

Maybe you can investigate this. I have a MacBook7,1 if that helps. @dosdude1 Thank you.

It will be looked into when I get some free time. No need to spam the thread.

 

[DuncanGarp]

Is it necessary to terminate Terminal at the end? (bolded on). Thanks.

Never mind. It's needed for startup on boot, so that line is required. Sorry to bother.

 

[0403979]

It will be looked into when I get some free time. No need to spam the thread.

It’s not urgent. I have a fix that works for me atm and I don’t want to take away from your free time.

 

[DuncanGarp]

10.4.1 System Update

Ok - worrying about the 10.4.1 system update, I tried it myself on my bookpro 5,3.

TL;DR - it worked

1. Downloaded the 10.14.1 beta utility from the developer site
2. Preferences system update kicked off immediately - downloaded (~1.99Gb I think) - then restarted
3. Got the no entry due to kernel panic of course
4. Applied latest post-install (checked off the APFS Patch just for kicks ?)
5. Rebooted - took a while - but eventually booted right up - Phew!

Observations:

1. APFS boot and verbose messages changed - haven't dug into these
2. In between initial install and post, I booted back up from the patcher stick to dig around and noticed a strange EFI configuration + beaucoup phantom disk images loaded. Disappeared though after successful post-install and reboot. Now my diskutil list looks fine
3. For some reason Apple doesn't have developer release notes for 10.4.1 up. Still trying to figure out what changed. Anyone have any insights into the changes?

This is good news. I will try it on my MBP that is currently on 10.14 final release.