macOS 10.14 Mojave on Unsupported Macs Thread

[jackluke]

Hi guys, only a question, if I enable sip in recovery mode, this is disabled once checked on normal mode... this is for the function called sip disable patch, there is a way for enabling on normal mode? Thanks a lot at all

You can enable/disable SIP from any macOS Recovery HD from El Capitan to the current macOS, or from any macOS installer (that is equivalent to a Recovery) El Capitan or higher, opening Utilities/Terminal and giving these command:
csrutil status (check if SIP in your Mac internal hdd is enabled or not)
csrutil disable (to disable SIP)
csrutil enable; reboot (this is the one you are asking for)

Not sure but maybe also a NVRAM/PRAM reset could re-enable SIP.

Also there are some patched kext/lib/plist command to force on the fly disabling during boot but I knew only through a Recovery (minimum El Capitan since when SIP was introduced).
I don't exclude that this last kind of SIP patching, will force SIP ever disabled, so any Recovery Terminal command could result vain.

My opinion, after patching process is done, for a daily use is better to re-enable SIP cause the worst dangerous malware often inject into these folders:

• /System
• /usr
• /bin
• /sbin

There is no way to enable/disable SIP in normal boot mode neither in single user mode that is a good deep level of sudo bash.

 

[netsrot39]

Does anybody of you guys also notice that graphic glitch (black bar) ? I have this usually after I wake up the computer from sleep and if I remember correctly it even disappears after some time (i don't know what triggers it and what makes it disappear)

 

[Loyd-01a]

It's because you have installed a third party CAM app, be careful that some could contain malware or incompatible libraries with Mojave. I'd suggest you to uninstall it.

Try open FaceTime, then on the Facetime/Finder bar click on "Video" and see there if can select iSight again as your default webcam.
[doublepost=1531901324][/doublepost]

Well, I guess you will need a supported Mac to fix it from single user mode or you should have backed up your previous Mojave working prelinkedkernel file for your machine. At the moment I don't know another way.

Here are the steps I followed to manually patch Mojave beta 4 (18A336e) again from a supported Mac:

1) Replace any IOUSB*** kext (they are 5 in total) taken from High Sierra (not only IOUSBHostFamily.kext only this to me caused instantly KP)
2) Replace any GeforceTesla***, NVDANV50HalTesla.kext, NVDAResmanTesla.kext taken from High Sierra except GeForceTesla.kext you have to take the one from ASentientBot post.
3) Replace in /System/Library/UserEventPlugins/ the entire com.apple.telemetry.plugin taken from High Sierra

And I add and confirm that with every IOUSB*** taken from High Sierra, and every patches applied to a Mojave disk (if external USB hdd), this will continue to boot even on a supported Mac too.
Cause seems that on them the KP depend only from IOUSB*** Family kext, so swapping all of them is an acceptable general solution.

I repeat replacing especially the IOUSB*** kexts you we need a supported Mac because you have to recreate the kextcache with HighSierra IOUSB*** embedded in, I insist saying a supported Mac because in past I have tried to rebuild a prelinkedkernel from another Mac pointing to the exact /Volumes/Mojave/S/L/* but it didn't work, the only safe way I know is booting directly from single user mode of the Mojave disk you intend to patch.
Because to do this is mandatory a working internal keyboard through a valid IOUSB***.

I advice using dosdude1's Mojave Patcher both to create an installer and for patching, since manually it's becoming tricky, while his tool make things a lot easier!


edit:

I take this opportunity to remember that even if the new CoreBrightness file is 718 KB, my old Mojave beta 2 patched 648 KB still enable night shift on beta 4.
And even replacing IOAccelerator from Mojave beta 1 still works, personally I need to replace this last one since without it on my specific case when browsing through Finder's folders sometime it autocloses or jump to a back Finder path without any user interaction, it's annoying and it seems this doesn't occur replacing IOAccelerator.

Thank you

If not, when using the dosdude1 patch, what are exactly patches that you select in the post intall step for macbook7,1?

 

[jackluke]

Thank you

If not, when using the dosdude1 patch, what are exactly patches that you select in the post intall step for macbook7,1?

I've done manually, but I guess you should use a previous Mojave Patcher version, since on the new one I saw only IOUSBHostFamily.kext between the packages, maybe lets wait a confirmation by dosdude1 that on Macbook7,1 starting from Mojave beta 4 all the five IOUSB*** kexts from High Sierra are required to avoid a quick reboot KP. I think so.

 

[16v]

O.K. got it to work...
Used latest POST INSTALLER, but isight Cam still dont work on MBP 5.4

 

[Loyd-01a]

I've done manually, but I guess you should use a previous Mojave Patcher version, since on the new one I saw only IOUSBHostFamily.kext between the packages, maybe lets wait a confirmation by dosdude1 that on Macbook7,1 starting from Mojave beta 4 all the five IOUSB*** kexts from High Sierra are required to avoid a quick reboot KP. I think so.

OK Thank for your answer !
I'll wait for news from dosdude1 concerning Macbook7,1 and the beta 4 of Mojave.

 

[Getheur]

Hello. Please, who can write OS update? I can't do it. When I update from beta "h" to beta "e" it will crash system. I start update from setting, after that I apply patcher, which I create with "h" version. So, I need guide for successful update. Thanks!

 

[ASentientBot]

It's because you have installed a third party CAM app, be careful that some could contain malware or incompatible libraries with Mojave. I'd suggest you to uninstall it.

Try open FaceTime, then on the Facetime/Finder bar click on "Video" and see there if can select iSight again as your default webcam.
[doublepost=1531901324][/doublepost]

Well, I guess you will need a supported Mac to fix it from single user mode or you should have backed up your previous Mojave working prelinkedkernel file for your machine. At the moment I don't know another way.

Here are the steps I followed to manually patch Mojave beta 4 (18A336e) again from a supported Mac:

1) Replace any IOUSB*** kext (they are 5 in total) taken from High Sierra (not only IOUSBHostFamily.kext only this to me caused instantly KP)
2) Replace any GeforceTesla***, NVDANV50HalTesla.kext, NVDAResmanTesla.kext taken from High Sierra except GeForceTesla.kext you have to take the one from ASentientBot post.
3) Replace in /System/Library/UserEventPlugins/ the entire com.apple.telemetry.plugin taken from High Sierra

And I add and confirm that with every IOUSB*** taken from High Sierra, and every patches applied to a Mojave disk (if external USB hdd), this will continue to boot even on a supported Mac too.
Cause seems that on them the KP depend only from IOUSB*** Family kext, so swapping all of them is an acceptable general solution.

I repeat replacing especially the IOUSB*** kexts you we need a supported Mac because you have to recreate the kextcache with HighSierra IOUSB*** embedded in, I insist saying a supported Mac because in past I have tried to rebuild a prelinkedkernel from another Mac pointing to the exact /Volumes/Mojave/S/L/* but it didn't work, the only safe way I know is booting directly from single user mode of the Mojave disk you intend to patch.
Because to do this is mandatory a working internal keyboard through a valid IOUSB***.

I advice using dosdude1's Mojave Patcher both to create an installer and for patching, since manually it's becoming tricky, while his tool make things a lot easier!


edit:

I take this opportunity to remember that even if the new CoreBrightness file is 718 KB, my old Mojave beta 2 patched 648 KB still enable night shift on beta 4.
And even replacing IOAccelerator from Mojave beta 1 still works, personally I need to replace this last one since without it on my specific case when browsing through Finder's folders sometime it autocloses or jump to a back Finder path without any user interaction, it's annoying and it seems this doesn't occur replacing IOAccelerator.

Awesome tutorial. I haven't installed beta 4 yet just because there don't seem to be many new features, and I don't really want to erase and reinstall my OS right now since I'm working on a few things (yes, yes, Mojave as primary OS on MacBook7,1 == a bad idea). So, unlike beta 3, you have to replace all IOUSB*.kext files?

I don't have a supported Mac. I had a lot of trouble figuring out how to rebuild the prelinkedkernel, and in the end I put a bash script like:
mount -uw /
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -invalidate /
into /var/root/.profile so that it gets auto-run when I startup single-user mode. I haven't seen this solution (actually, a general purpose way to run scripts without a keyboard kext loaded) so I figured I'd mention it.

But most times, the prelinkedkernel should auto-rebuild at boot if your permissions are correct and /S*/L*/E* has been modified.

 

[swamprock]

You can enable/disable SIP from any macOS Recovery HD from El Capitan to the current macOS, or from any macOS installer (that is equivalent to a Recovery) El Capitan or higher, opening Utilities/Terminal and giving these command:
csrutil status (check if SIP in your Mac internal hdd is enabled or not)
csrutil disable (to disable SIP)
csrutil enable; reboot (this is the one you are asking for)

Not sure but maybe also a NVRAM/PRAM reset could re-enable SIP.

Also there are some patched kext/lib/plist command to force on the fly disabling during boot but I knew only through a Recovery (minimum El Capitan since when SIP was introduced).
I don't exclude that this last kind of SIP patching, will force SIP ever disabled, so any Recovery Terminal command could result vain.

My opinion, after patching process is done, for a daily use is better to re-enable SIP cause the worst dangerous malware often inject into these folders:

• /System
• /usr
• /bin
• /sbin

There is no way to enable/disable SIP in normal boot mode neither in single user mode that is a good deep level of sudo bash.

There's a version of rEFInd that can enable/disable SIP if installed and booted from USB: https://forums.macrumors.com/thread...nsupported-macs.1889851/page-37#post-24695866

Read all of "Problem 2" for instructions. There is an option within rEFInd that lets you enable and disable SIP when necessary.

 

[pkouame]

Used @Czo's solution (SUVMMFaker.dylib) as linked above by @0403979 and finally got it to show up in System Preferences > Software Update to do the update without a supported Mac. Afterward I had to re-modify PlatformSupport.plist with the unsupported Mac's model + board id and it was bootable.

At what stage did you modify your plist. I finally got my system software update to kick-in, let it install and restart, but it's in an infinite loop. Also, did you post-install?

 

[jackluke]

Awesome tutorial. I haven't installed beta 4 yet just because there don't seem to be many new features, and I don't really want to erase and reinstall my OS right now since I'm working on a few things (yes, yes, Mojave as primary OS on MacBook7,1 == a bad idea). So, unlike beta 3, you have to replace all IOUSB*.kext files?

I don't have a supported Mac. I had a lot of trouble figuring out how to rebuild the prelinkedkernel, and in the end I put a bash script like:
mount -uw /
chown -R root:wheel /S*/L*/E*
chmod -R 755 /S*/L*/E*
kextcache -invalidate /
into /var/root/.profile so that it gets auto-run when I startup single-user mode. I haven't seen this solution (actually, a general purpose way to run scripts without a keyboard kext loaded) so I figured I'd mention it.

But most times, the prelinkedkernel should auto-rebuild at boot if your permissions are correct and /S*/L*/E* has been modified.

I am 90% sure that from Mojave beta 4 the Macbook7,1 (and maybe any C2D with legacy USB) will require the five IOUSB*** kexts from High Sierra to avoid a quick KP due to HID USB internal devices unresponsive.

The quick reboot KP I am referring occurs few seconds before the "hid legacy shim 2" in verbose so there is no chance in single user mode to let it slide automatically until a script launch for kextcache auto-rebuild, it crashes very very early than landing to the command line.

Agree on what you written, but the auto-rebuild occurs only if you are booting directly from the MacOS disk you want to refresh the prelinkedkernel, I meant can't be done from another Mac for a different Mac, or at least I don't know how to do it.

Or better it can be done with a workaround, by replacing the Mojave's five IOUSB*** kexts with High Sierra ones, to support booting for the legacy USB machines, and since I've checked that a supported Mac still can boot with replaced telemetry.plugin this is a very good chance to make a common boot Mojave for both supported/unsupported Macs.

edit:
Your script for auto-rebuild a kextcache is interesting.

 

[cpharada1]

[doublepost=1531913266][/doublepost]updated to Public Beta 3 = 18A336e on my iMac mid-2011 (12,2 with AMD Radeon HD 6770M). Graphics much improved with no UI glitches. Has anyone else noted this ?

Yes, my iMac 12,2 with AMD 6970M is much smoother with graphics. No more unreadable menu bar and app windows are much cleaner with or without font smoothing and reduced transparency. Dynamic wallpaper is still buggy and overall performance is laggy but the changes have made me think Mojave will someday be my primary OS.
Thanks so much dosdude1 and all the other wizards working on this!

 

[roysterdoyster]

need help with my MacBookPro4,1 (17-inch, Early-2008): won't boot after install (Mojave Beta 4; Patcher 0.1b12)
My current machine configuration: 10.13.6 (17G65), NVIDIA GeForce 8600M GT 512 MB.
Here's what I did to move from 10.13.6 to 10.14 Beta 4
1 - Created bootable USB stick (16GB)
2 - formatted SSD to APFS
3 - installed Mojave Beta 4
4 - patched with d0sdude1's patcher b12
5 - MBP stuck after startup chime with blank screen, no boot logo
6 - repeated patching several times, no success

so now I'm back on 10.13.6.

Help anyone? Highly appreciated!

 

[dosdude1]

need help with my MacBookPro4,1 (17-inch, Early-2008): won't boot after install (Mojave Beta 4; Patcher 0.1b12)
My current machine configuration: 10.13.6 (17G65), NVIDIA GeForce 8600M GT 512 MB.
Here's what I did to move from 10.13.6 to 10.14 Beta 4
1 - Created bootable USB stick (16GB)
2 - formatted SSD to APFS
3 - installed Mojave Beta 4
4 - patched with d0sdude1's patcher b12
5 - MBP stuck after startup chime with blank screen, no boot logo
6 - repeated patching several times, no success

so now I'm back on 10.13.6.

Help anyone? Highly appreciated!

Don't use APFS and it will work fine.

 

[0403979]

Don't use APFS and it will work fine.

I was looking around for the error and I just now found it because you pointed it out. The bootloader doesn’t support APFS natively.

 

[redheeler]

At what stage did you modify your plist. I finally got my system software update to kick-in, let it install and restart, but it's in an infinite loop.

The update installed fine, but afterward booted to the This version of Mac OS X is not supported on this platform! message (verbose mode), indicating the plist needed to be re-modified.

Also, did you post-install?

I didn't use the MacOS Mojave Patcher to install Mojave on my 2011 MacBook Pro. I simply added the needed kexts manually after updating to beta 3, and the only one I had trouble with following the update to beta 4 was AppleHDA.kext (no audio through the built-in speakers), which I replaced with a version from High Sierra to resolve the issue.

 

[jackluke]

I didn't use the MacOS Mojave Patcher to install Mojave on my 2011 MacBook Pro. I simply added the needed kexts manually after updating to beta 3, and the only one I had trouble with following the update to beta 4 was AppleHDA.kext (no audio through the built-in speakers), which I replaced with a version from High Sierra to resolve the issue.

A similar issue I had encountered, and I know why, that's because during a major version upgrade, sometimes the "kext folder" keep an older modified date letting thinking that it is the older one, instead if you inspect Name.kext/Contents/MacOS/ the real "kext unix binary" has been updated inside, so replacing just him could work too. Anyway replacing entirely is better.

 

[pkouame]

The update installed fine, but afterward booted to the This version of Mac OS X is not supported on this platform! message (verbose mode), indicating the plist needed to be re-modified.

I didn't use the MacOS Mojave Patcher to install Mojave on my 2011 MacBook Pro. I simply added the needed kexts manually after updating to beta 3, and the only one I had trouble with following the update to beta 4 was AppleHDA.kext (no audio through the built-in speakers), which I replaced with a version from High Sierra to resolve the issue.

Ah. Makes sense now. I assume you changed your catalog to developer seed. Do you know what "customer seed" is?

 

[DeutscheMark]

Hi, I need some help installing the current beta.
I have a MacBook Pro 13" Early 2011 and already installed Developer Beta 3 on an SSD with APFS and it's working fine so far.
But what is the correct way now to update to Developer Beta 4?
Thank you.

 

[vince22]

O.K. got it to work...
Used latest POST INSTALLER, but isight Cam still dont work on MBP 5.4

many thanks to dosdude1 for awesome work, only missing for my 2010 MacBook Pro 7.1 no FaceTime video but everything else running smoothly.

 

[TimothyR734]

b12 Patcher
Failed to Copy to USB
Please make sure drive is formatted correctly

whats wrong?

try to format your usb with disk utility to extended journaled then try again with the patcher utility if it happens again try another usb drive

 

[0403979]

Hi, I need some help installing the current beta.
I have a MacBook Pro 13" Early 2011 and already installed Developer Beta 3 on an SSD with APFS and it's working fine so far.
But what is the correct way now to update to Developer Beta 4?
Thank you.

Update via settings and patch afterwards with your patched usb.

 

[TimothyR734]

Hi, I need some help installing the current beta.
I have a MacBook Pro 13" Early 2011 and already installed Developer Beta 3 on an SSD with APFS and it's working fine so far.
But what is the correct way now to update to Developer Beta 4?
Thank you.

did you check under software update in the system preferences if so you could try the SWUSwitcher utility on page 125

 

[roysterdoyster]

Don't use APFS and it will work fine.

Thank you, @dosdude1 ! Your work is outstanding.

Would i rather
a - install OVER 10.13.6?
b - erase HFS+ Macintosh HD (while sticking to HFS+) first, then install Mojave Beta 4, patch with b12, run Migaration Assistant App from within new system?

MBP4,1 (Early-2008)

 

[0403979]

Thank you, @dosdude1 ! Your work is outstanding.

Would i rather
a - install OVER 10.13.6?
b - erase HFS+ Macintosh HD (while sticking to HFS+) first, then install Mojave Beta 4, patch with b12, run Migaration Assistant App from within new system?

MBP4,1 (Early-2008)

Erasing first is better.