macOS 10.14 Mojave on Unsupported Macs Thread

[HDMC]

Thanks very much for the reply !

There is 2 methods to resolve this.
1) You can replace the 5 IOUSB* kext in S/L/E with the one in High Sierra (post 8472 from webg3 gave me the idea to try that)

How did you do that ? I can´t do anything with S/L/E ! Where I can find these kexts and where to replace them ?

2) Use the legacy iSight patch in dosdude1 post install tool (post 8692 from SpinThis!)

I already tried this with no solution

Both methods worked for me for Brio and C920 Logitech webcam on my Mac Pro 3.1.

I tried the Logitech C615 and Microsoft HD 3000, both the same ...

 

[TimothyR734]

Thanks very much for the reply !


How did you do that ? I can´t do anything with S/L/E ! Where I can find these kexts and where to replace them ?


I already tried this with no solution


I tried the Logitech C615 and Microsoft HD 3000, both the same ...

The link to the 5 kexts is on page 351 I used kext utility that is also included in the link

 

[webg3]

 

[joelw135]

Has anyone had any luck updating Mac Mini 3,1 using the Mojave update utility to Beta 3? if yes any special things needed?

 

[imm0rtalz16_2006]

Did you apply the legacy video card patch?

Yes

 

[ASentientBot]

To those who struggle launching 32-bit apps... it is not a side-effect of running Mojave on an unsupported system. They run with zero issues on my MacBook7,1 with a Penryn CPU and that's as unsupported as it gets.

Please try launching the app's main executable (SomeApp.app/Contents/MacOS/SomeApp) in Terminal and reporting the output. You may be missing a library, or one architecture of a library. Some system frameworks contain a "fat" binary with versions for both 64-bit and 32-bit programs. If just the 32-bit version is missing or corrupted, this would explain your problem. (I noticed that most executables in recovery mode/installer drive (BaseSystem) are "thin" 64-bit versions. If you've restored any copies from there, that may be the problem. I tried this before when I screwed up SkyLight and this will cause your symptom of only 64-bit apps working.)

The "not optimized" dialog when launching a 32-bit app is a normal warning in Mojave, as support for 32-bit apps will be removed in 10.15. However, it isn't a problem.

Hope that helps clear things up a little. It's getting frustrating seeing so many complex theories about a (probably) simple issue.

And remember, if all else fails, nuke and reinstall!

 

[oscarodas]

Did this work from software update? I am not sure if I should try it on a 2010 Mac Mini 3,1.

Yes, as soon as I saw the available update I agreed to download and install.But before you do it, if you read the posts that people have been able to update, most are iMacs 2011.

 

[jackluke]

To those who struggle launching 32-bit apps... it is not a side-effect of running Mojave on an unsupported system. They run with zero issues on my MacBook7,1 with a Penryn CPU and that's as unsupported as it gets.

Please try launching the app's main executable (SomeApp.app/Contents/MacOS/SomeApp) in Terminal and reporting the output. You may be missing a library, or one architecture of a library. Some system frameworks contain a "fat" binary with versions for both 64-bit and 32-bit programs. If just the 32-bit version is missing or corrupted, this would explain your problem. (I noticed that most executables in recovery mode/installer drive (BaseSystem) are "thin" 64-bit versions. If you've restored any copies from there, that may be the problem. I tried this before when I screwed up SkyLight and this will cause your symptom of only 64-bit apps working.)

The "not optimized" dialog when launching a 32-bit app is a normal warning in Mojave, as support for 32-bit apps will be removed in 10.15. However, it isn't a problem.

Hope that helps clear things up a little. It's getting frustrating seeing so many complex theories about a (probably) simple issue.

And remember, if all else fails, nuke and reinstall!

Agree, but why if @lukiy booting in safe mode 32 bit apps work ?
I mean booting from safe mode isn't a similar concept as booting from BaseSystem.dmg ?

I thought he posted his terminal output with "permissions issues" on the hidden "private" folder.

 

[yeiyei0891]

What is your machine?

Remembering that both Light Mode and Dark Mode depend on the reduction of transparency, I recommend applying before for disengagement, because here the two modes normally work.

MacBook 6,1. When I switch to dark mode I apply the Dark Script and all looks ok in finder and dock but some apps (VLC) has the menu (or sidebar) with grey background (like finder without script). When I switch to Light Mode I apply the LightScript and VLC it's ok (same with Finder which hasn't transparency). The problem is that the DarkScript gives transparency to sidebar and dock in Finder but too gives transparency to other menus and sidebar in some apps and grey background. The LightScript remove the transparency to Finder but too remove that transparency in VLC and looks ok.

 

[caincha]

Any news on RAIDing 2 SSDs on APFS?
I’ve got a 17” MacBook Pro 2010 and would really LOVE to see that big screen running a blazingly-fast Mojave on RAID

 

[webg3]

MacBook 6,1. When I switch to dark mode I apply the Dark Script and all looks ok in finder and dock but some apps (VLC) has the menu (or sidebar) with grey background (like finder without script). When I switch to Light Mode I apply the LightScript and VLC it's ok (same with Finder which hasn't transparency). The problem is that the DarkScript gives transparency to sidebar and dock in Finder but too gives transparency to other menus and sidebar in some apps and grey background. The LightScript remove the transparency to Finder but too remove that transparency in VLC and looks ok.

It is correct everything you said, unfortunately there is no way to fix DarkScript, unless you make adjustments manually and remove all the transparency of it, leaving the menus with solid colors, it was made only for use in dark mode, but the applications that are not ready for dark mode will display the menus in black and gray background, some applications are already moving to dark mode, just wait or use LightMode while we do not have the definitive solution, since my scripts are only temporary and a nice way I found to use the system at the moment.

 

[joelw135]

Yes, as soon as I saw the available update I agreed to download and install.But before you do it, if you read the posts that people have been able to update, most are iMacs 2011.

Well I crashed and burned, it went into a continuous loop. I booted from my install and patched. Still a loop. Trying to reinstall over original install hope it works.

UPDATE: Need to do a clean install. Is there a Beta 3 file to download? I guess not. So back to original.

 

[lukiy]

To those who struggle launching 32-bit apps... it is not a side-effect of running Mojave on an unsupported system. They run with zero issues on my MacBook7,1 with a Penryn CPU and that's as unsupported as it gets.

Please try launching the app's main executable (SomeApp.app/Contents/MacOS/SomeApp) in Terminal and reporting the output. You may be missing a library, or one architecture of a library. Some system frameworks contain a "fat" binary with versions for both 64-bit and 32-bit programs. If just the 32-bit version is missing or corrupted, this would explain your problem. (I noticed that most executables in recovery mode/installer drive (BaseSystem) are "thin" 64-bit versions. If you've restored any copies from there, that may be the problem. I tried this before when I screwed up SkyLight and this will cause your symptom of only 64-bit apps working.)

The "not optimized" dialog when launching a 32-bit app is a normal warning in Mojave, as support for 32-bit apps will be removed in 10.15. However, it isn't a problem.

Hope that helps clear things up a little. It's getting frustrating seeing so many complex theories about a (probably) simple issue.

And remember, if all else fails, nuke and reinstall!

The problem is that:
1. ALL 32 bit apps cannot be opened in normal mode.
2. ALL 32 bit apps CAN be open in safe mode.
3. When trying to launch the app's main executable from a command line, there is no output, no errors.
4. No errors in Console app. It is like the 32 app thread goes to sleep doing nothing.
5. People who have Mojave on supported hardware can open the 32 bot apps normally.

These may suggest that there may be something wrong with the unsupported patches.

 

[NoobMacUser]

Hi, this is the latest Beta, I installed it today, it went very smooth, only took about 17 minutes, it downloaded from apple the system re-started twice and then gave me the desktop, I didn't have to install any patches.View attachment 793261

Is your GPU working fine?

 

[cybermol]

Is your GPU working fine?

how about the authorization voor apps like Skype and Parallels?

 

[andrey_russian]

I replaced iMac 27 2011 ATI Radeon HD 6770M 512 MB with Nvidia GeForce GTX 680M 2 Gb (from notebook ALIENWARE M18 R2.
No Mac boot menu now.
Is there a solution to the problem?

 

[Sveto]

Yes, mostly because the macOS recoveries do a check through Internet on machine before allow to download the Installer (again) into the disk, maybe this check is patchable too, but then would remain a non-patched Installer with dangerous firmware.pkg inside (and without Post-Install), so both the HFS and APFS Recovery are just for Utilities fun, anyway from a Recovery Terminal can do a lot of things, even a partial manual patching of Mojave.

You can do the same in single user recovery (command+R+S), it does not need patching, no user interface and has the same power as terminal+disk utility in normal recovery. So better to stop messing with making regular recovery work. If one is missing the patched USB and needs to fix a few things on the go, well then the single user recovery can be used.

 

[jackluke]

You can do the same in single user recovery (command+R+S), it does not need patching, no user interface and has the same power as terminal+disk utility in normal recovery. So better to stop messing with making regular recovery work. If one is missing the patched USB and needs to fix a few things on the go, well then the single user recovery can be used.

First of all, right to be clear, I have found a "fix" for the "APFS Recovery" NOT for HFS "Recovery HD" (dosdude1 into his Mojave Patcher has fixed HFS "Recovery HD").

Then I could be partially agree with your argument, but it depends which kind of mac do you have.
1) My APFS Recovery "fix" is oriented to those who want to know more on manual patching;
2) Apart the Terminal, with the APFS GUI Recovery you can use wifi with Safari, GUI DiskUtility and mainly Time Machine;
3) With many unsupported mac if you don't have SIP disabled, a whitelisted platform Mac Model Identifier and especially the right patched "prelinkedkernel/immutablekernel" for your machine using CMD+S+R you won't have the USB input devices (internal keyboard, trackpad, usb mouse, bluetooth keyboard, bluetooth mouse and so on) responsive, so without those from Recovery single user Terminal can't type nothing.

Anyway feel free to give advices to other on fixing their issues using a Recovery single user mode Terminal.

 

[avz]

I replaced iMac 27 2011 ATI Radeon HD 6770M 512 MB with Nvidia GeForce GTX 680M 2 Gb (from notebook ALIENWARE M18 R2.
No Mac boot menu now.
Is there a solution to the problem?

Did you flash it for Mac first?

 

[vix2000]

Any suggestions re: the keyboard problem? Otherwise it’s back to high Sierra unfortunately

 

[andrey_russian]

Did you flash it for Mac first?

Ooops! No.
Does this procedure work with my card?

 

[oscarodas]

Is your GPU working fine?

As you can see I have an AMD 6970M, that means no acceleration, but I don't play games or do graphics intensive apps, apart from that my system works ok, never had an issue with operating system, the only programs that don't work are VLC and Netflix.

 

[avz]

Ooops! No.
Does this procedure work with my card?

From the video description that I posted:
"This method will work with any GTX680 card with a matching port layout as the reference card (shown in the video), and will allow it to show a boot screen on any Mac Pro 3,1 or later."

I haven't performed this procedure myself, so maybe somebody more experienced can help.

 

[andrey_russian]

From the video description that I posted:
"This method will work with any GTX680 card with a matching port layout as the reference card (shown in the video), and will allow it to show a boot screen on any Mac Pro 3,1 or later."

I haven't performed this procedure myself, so maybe somebody more experienced can help.

OK. Thank you.

 

[Sveto]

First of all, right to be clear, I have found a "fix" for the "APFS Recovery" NOT for HFS "Recovery HD" (dosdude1 into his Mojave Patcher has fixed HFS "Recovery HD").

Then I could be partially agree with your argument, but it depends which kind of mac do you have.
1) My APFS Recovery "fix" is oriented to those who want to know more on manual patching;
2) Apart the Terminal, with the APFS GUI Recovery you can use wifi with Safari, GUI DiskUtility and mainly Time Machine;
3) With many unsupported mac if you don't have SIP disabled, a whitelisted platform Mac Model Identifier and especially the right patched "prelinkedkernel/immutablekernel" for your machine using CMD+S+R you won't have the USB input devices (internal keyboard, trackpad, usb mouse, bluetooth keyboard, bluetooth mouse and so on) responsive, so without those from Recovery single user Terminal can't type nothing.

Anyway feel free to give advices to other on fixing their issues using a Recovery single user mode Terminal.

Your input is highly appreciated. I am NOT criticizing it in any shape or form. My points are as follows:
HFS "Recovery HD" was not fixed by dosdude1 in patcher v.1.2.1, I don't know for v1.2.2
To me it seems way too big of an effort trying to fix APFS GUI Recovery if one plans to do serios patching and manipulations to the system in general. The safest is to perform it, while booted in the patched USB installer (which carries the same goodies as the regular Recovery).
For rather small changes (on the go) one can use a Single User Recovery (since the patched USB is not around). Also although I completely agree with your point 3), if one has successfully installed and booted in Mojave, than in 99% Single User Recovery has been already made functional by the USB patched installer.