macOS 10.14 Mojave on Unsupported Macs Thread

[mocteo]

Hello, i installed Mojave on a late 2009 iMac (21,5 3,06) and I got no problem for about a month, but now there are problems with the shutdown, sleep mode and sound.
I can go in sleep mode only one time, after it won't work, the sound settings on the keyboard won't work and the shutdown and sleep mode option in the apple menu won't work too. I need to force shutdown. Sometimes I go out of sleep mode and the screen is black with only the mouse cursor.
is it a problem with my Mac or it's "normal" ?
thanks

 

[0403979]

Hello, i installed Mojave on a late 2009 iMac (21,5 3,06) and I got no problem for about a month, but now there are problems with the shutdown, sleep mode and sound.
I can go in sleep mode only one time, after it won't work, the sound settings on the keyboard won't work and the shutdown and sleep mode option in the apple menu won't work too. I need to force shutdown. Sometimes I go out of sleep mode and the screen is black with only the mouse cursor.
is it a problem with my Mac or it's "normal" ?
thanks

Try repatching your machine.

 

[Aletancredo]

The software update contains boot rom upgrades which breaks the installation process on unsupported Macs so everyone will just have to wait until 10.14.1 is released to install via the full installer.

Thanks for your help...I tried ...but it is not working.

 

[w1z]

@dosdude1 Something broke with the high sierra patcher running on Mojave/supported hardware (tested on 2 machines with SIP enabled and disabled) as I have exhausted all options to create a working USB flash stick and internal partition high sierra installer.

I am re-downloading high sierra installer directly on a HFS+ formatted partition instead of APFS on Mojave .. I am suspecting Apple may have done some changes to either the High Sierra installer or added some additional protections to Mojave.

Update: Latest attempt failed - attaching screenshot.

Update2: No problem creating a Mojave installer with your Mojave Patcher. Issue is only with High Sierra Patcher as I was able to create a normal USB installer using Apple's creatinstallmedia instructions.

 

[nubie]

APFS ROM patcher question:
I updated my MacBookPro 5,5 mid 2009 to Mojave - works nicely. My SSD is already on APFS and starts up with the APFS patched Mojave installer.
Now I am thinking about patching my ROM. Downloaded the ROMTool 2.0 to do a backup. It says:
"EEPROM Has Multiple Definitions"
It suggests to use MX25L3206E. I opened up my MBP and found a chip reading MX25L3205DM2I, see attached photo. @dosdude1 Which choice in the ROMTool shall I take?

Edit: SUCCESS!
After having read the attached PDF by MX I was sure that the MX25L3205DM2I indeed is a version of the MX25L3205D. So I gave the APFS ROM patcher a try... and it worked.
Finally I mounted the EFI partition and deleted the "BOOT" folder and "apfs.efi".
Now I looks like my MBP is not aged at all.
A very big thank you to you @dosdude1
A tip is already on the way via your donation page ;-)

 

[fintematic]

The following patch would apply to any machine with issues with the iSight camera... if you also have installed Virtual Box (currently 5.2.18 but I presume all versions will break iSight).
I noticed that after a clean install the builtin isight camera didi work ok, but stopped after a while. Looking around I found that uninstalling VirtualBox does bring the camera back to life!

How to get both working ? Well, it looks VirtualBox has a kext that breaks the camera.
Found a way to partially disable that kext, but keeping the camera and Virtualbox working at the same time. This unobtrusibe and clean touch/fix will get broken if you install a newer version of Virtualbox and you'd have to do the changes to the file again.

See highlighted the commented lines on the Virtual Box file, then restart your machine and enjoy the Camera and VirtualBox.

File to patch:
"/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh"

Look for the section below
ConsoleMessage "Loading ${VBOXUSB}.kext"

Enter comments to the kextload section.:
#if ! kextload -d "/Library/Application Support/VirtualBox/${VBOXDRV}.kext" "/Library/Application Support/VirtualBox/${VBOXUSB}.kext"; then
# ConsoleMessage "Error: Failed to load /Library/Application Support/VirtualBox/${VBOXUSB}.kext"
# VBOX_RC=1
#fi


Hope this helps somebody out there

Perhaps dosdude1 could update his main documentation with some notes re this fixes if found helpful or relevant. i.e. iSight "hit & miss" will definitely not work if VirtualBox installed.
Thanks for this development, it has renewed my MBP 5,2 and works much better with 10.14 vs the last "supported" 10.11 !!!

Hope this helps somebody out there!

I uninstalled virtual box, i don't use it.
Thank you man, i solved my problem with isight! Thx Thx Thx

 

[jackluke]

What's your Mac?

For you is different, cause your mac supports natively until El Capitan, so probably you should use El Capitan IOUSB***.kext to make iSight respond.

 

[puremind2000]

I uninstalled virtual box, i don't use it.
Thank you man, i solved my problem with isight! Thx Thx Thx

Well, if you don't use Virtualbox, uninstalling is easier solution
Unfortunately, I need it for some old Windows application and to run Docker (via Docker Toolbox) , as this machine is too old for the regular docker daemon.

Also, for VirtualBox users, note that the fix will disable USB for VirtualBox, if you want that you'll need to revert.

Happy it has helped!

 

[webg3]

I'm relentless to find the solution to my workflow.

I found this quite interesting, but it's a paid tool.

http://dssw.co.uk/powermanager

 

[jackluke]

Well, if you don't use Virtualbox, uninstalling is easier solution
Unfortunately, I need it for some old Windows application and to run Docker (via Docker Toolbox) , as this machine is too old for the regular docker daemon.

Also, for VirtualBox users, note that the fix will disable USB for VirtualBox, if you want that you'll need to revert.

Happy it has helped!

Agree, I also have a Mojave USB SSD that I use practically everywhere, both in almost any virtualization software, on real machines unsupported and supported, in VirtualBox I use it as RawDisk, anyway, at least on my Mac supported natively until HighSierra 10.13.x , I don't have that issue with VirtualBox guest kext (even with Vmware), but maybe your fix for iSight is useful to those with mac supported natively until 10.11.x , good work.

 

[Mikki77]

anyone got success on iMac Late 2009? (iMac 10,1)

No issues whatsoever except for the known graphics glitches on the menus using the light mode. But can be kind of fixed with the script here. I have one weird glitch in itunes though that some of my own transcoded movies don't play (for no apparent reason). However, they work when playing with quicktime. iSight camera, bluetooth and wifi with continuity patch works (I have an upgraded airport card) as well as all my apps. I have an iMac 11,1 i7 (also late 2009) though.

 

[fintematic]

For you is different, cause your mac supports natively until El Capitan, so probably you should use El Capitan IOUSB***.kext to make iSight respond.

No man, my mac supports natively until HighSierra

 

[puremind2000]

No issues whatsoever except for the known graphics glitches on the menus using the light mode. But can be kind of fixed with the script here. I have one weird glitch in itunes though that some of my own transcoded movies don't play (for no apparent reason). However, they work when playing with quicktime. iSight camera, bluetooth and wifi with continuity patch works (I have an upgraded airport card) as well as all my apps. I have an iMac 11,1 i7 (also late 2009) though.

Have you tried the below?
#8250

 

[jackluke]

No man, my mac supports natively until HighSierra

Ok, then I understood, the Virtualbox guest kext in your case was embedded into the prelinkedkernel so that's why your camera bus was busy and not responding, anyway I'm glad @puremind2000 fixed it.

 

[puremind2000]

Ok, then I understood, the Virtualbox guest kext in your case was embedded into the prelinkedkernel so that's why your camera bus was busy and not responding, anyway I'm glad @puremind2000 fixed it.

Well, it's only a patch... perhaps something else more "robust" could be put in place... or the VB developers fix this permanently! At least we cannot blame Mojave or dosdude1 for the iSight to not work...

 

[0403979]

APFS ROM patcher question:
I updated my MacBookPro 5,5 mid 2009 to Mojave - works nicely. My SSD is already on APFS and starts up with the APFS patched Mojave installer.
Now I am thinking about patching my ROM. Downloaded the ROMTool 2.0 to do a backup. It says:
"EEPROM Has Multiple Definitions"
It suggests to use MX25L3206E. I opened up my MBP and found a chip reading MX25L3205DM2I, see attached photo. @dosdude1 Which choice in the ROMTool shall I take?

Use whichever one is on your chip.
[doublepost=1538219364][/doublepost]

I'm relentless to find the solution to my workflow.

I found this quite interesting, but it's a paid tool.

http://dssw.co.uk/powermanager

What are you trying to do?

 

[Jack Ryan]

What's your Mac?

iMac 27" late 2009

 

[Balaur]

anyone got success on iMac Late 2009? (iMac 10,1)

yes. Details on post 7929, page 318

 

[interessiert]

I guess good to know:

Version 1.2.2 works properly for NOT ENCRYPTED HDs.

Those whose HD is encrypted (FileVault) can spare time and should wait for a later release of COLLIN's Patcher Tool

 

[antony34]

No issues whatsoever except for the known graphics glitches on the menus using the light mode. But can be kind of fixed with the script here. I have one weird glitch in itunes though that some of my own transcoded movies don't play (for no apparent reason). However, they work when playing with quicktime. iSight camera, bluetooth and wifi with continuity patch works (I have an upgraded airport card) as well as all my apps. I have an iMac 11,1 i7 (also late 2009) though.

Thanks for your information!! Let me try to upgrare my iMac 10,1
[doublepost=1538221847][/doublepost]

yes. Details on post 7929, page 318

Thank you!! Let me check it now!

 

[webg3]

I think is better compiling all in Apple script, you can check the dark mode status

tell application "System Events"
tell appearance preferences
set dark mode to not dark mode
set scuro to get dark mode
if scuro then
do shell script "
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Spotlight;
killall Finder;
defaults write com.apple.universalaccess reduceTransparency -bool false;
killall Dock;
killall Finder;
killall NotificationCenter;
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Spotlight;
defaults write com.apple.universalaccess reduceTransparency -bool false;
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO;"
else
do shell script "
defaults write com.apple.universalaccess reduceTransparency -bool false;
killall Finder;
killall Dock;
killall NotificationCenter;
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;
defaults write com.apple.universalaccess reduceTransparency -bool true;
killall Finder;
killall Spotlight;"



end if

end tell

end tell

thank you for that.
[doublepost=1538222738][/doublepost]

Launch Terminal (located in /Applications/Utilities) and enter the following command:
sudo defaults write -g NSRequiresAquaSystemAppearance -bool Yes

Then logout or restart. Switch to Light mode. Only the "weird darkish mode" will be changed by black mode.

-> This is an excerpt from :
https://www.tekrevue.com/tip/only-dark-menu-bar-dock-mojave/
Mainly, whoever wants a Light Mode can have it working 99%, only the dock and top bar will be blank, but not “weird darkish grey”.
I currently prefer this mode to fully white or black and is better than the weird one.

I think this was sorted with the macOS Mojave Patcher 1.2.2, but in any case the above can be preferable to some users.

Not solved non-metal GPUs.

As already mentioned, we want to fix the light mode without affecting the dark mode, this is giving a bit of work, and I do not like the white Dock, so I implemented some scripts, just read a few pages ago, not the best solution, has worked well.

some guys are working on a better solution than mine, but it's not being easy.
[doublepost=1538222996][/doublepost]

Use whichever one is on your chip.
[doublepost=1538219364][/doublepost]
What are you trying to do?

Done, just see the attachments

By combining the Control + Command + M keys (runs my script and enters the dark mode on or off);

Just watch the video and choose the keys in System Preferences> Keyboard

Woooowwww finally this works
Amazing!!!!
Do a test!

 

[0403979]

Patch for Wi-Fi on Patched macOS Mojave Installers:
Those who wish to use Wi-Fi on their patched macOS Mojave installers can use the following steps to enable this functionality.

Warning:
The functionality and safety of this patch is not guaranteed. You may use this at your own risk.

How to Patch:

• Download a patched prelinkedkernel from here.
• Delete /System/Library/PrelinkedKernels/prelinkedkernel from your patched installer.
• Copy the new prelinkedkernel to /System/Library/PrelinkedKernels on your patched installer.
• Lock /System/Library/PrelinkedKernels/prelinkedkernel on your patched installer.

Files to Download:
If your device needs the Legacy Wi-FI Patch, then download one from the With WiFI Patch folder.
If your device doesn't needs the Legacy Wi-FI Patch, then download one from the Without WiFI Patch folder.

 

[Loyd-01a]

Patch for Wi-Fi and APFS Encryption on Patched macOS Mojave Installers:
For those who wish to use Wi-Fi or unlock encrypted APFS drives on their patched macOS Mojave installers can use the following steps to enable this functionality.

Warning:
The functionality and safety of this patch is not guaranteed. You may use this at your own risk.

How to Patch:

• Download a patched prelinkedkernel from here.
• Delete /System/Library/PrelinkedKernels/prelinkedkernel from your patched installer.
• Copy the new prelinkedkernel to /System/Library/PrelinkedKernels on your patched installer.
• Lock /System/Library/PrelinkedKernels/prelinkedkernel on your patched installer.

This guide is linked on the original post.

I saw in original post' credits that you are cited as the guy that Fixed Wi-Fi and APFS encryption on installers !

Are you sure that it is you who did the work ?

 

[dosdude1]

I saw in original post' credits that you are cited as the guy that Fixed Wi-Fi and APFS encryption on installers !

Are you sure that it is you who did the work ?

He just rebuilt prelinkedkernel from a full install. I've been building mine from the BaseSystem, which apparently has these issues.

 

[webg3]

Guys, I'm sorry for the excessive posts, I know that you must already be tired of so many posts ref to the same subject.

I have learned a lot in the last few hours, and I want to share with everyone, I know there are people here who know a lot about programming and systems, I'm just starting to do the hacks, and I would not use that term, but that's what we're all doing us, with our unsupported macs.

This is a cleaner look at start items: I automated the script (now it runs at startup without you noticing)

That's what I was trying to do from the beginning.

Sorry if I did a lot of spam with so many posts.