macOS 10.14 Mojave on Unsupported Macs Thread

[pantherstoner]

I've read that Radeon 5000/6000 can't run Mojave. Mine is AMD Radeon 7650M. Is there any chance that it can run Mojave?
Edit: 7650 is part of the AMD6000Controller.kext and it doesn't have metal support.
Spec of 7650M: https://www.techpowerup.com/gpu-specs/radeon-hd-7650m.c1210

 

[RK78]

Running 10.14.6 (newly installed) on iMac 10,1 from HFS+ volume. Unable to boot into recovery mode. At CMD-R or Restart using boot picker (option boot), always get no entry symbol. Both diskutil list and boot picker show 10.14.6 recovery partition.

Any help greatly appreciated.

 

[avz]

@dosdude1, @jackluke, any suggestions?

pkgutil --expand-full "drop your .pkg file here without quotation marks" ~/Expanded

Then just browse through the Payloads folders and you should see your Extensions, Frameworks, PrivateFrameworks etc.
[automerge]1571951788[/automerge]

do I need the usb stick I installed the patched Mojave from, every time I want to turn on my MacBook Pro early 2008? or have I done something wrong? because without the stick inserted my Mac boots into the os installer page(with disk utility and ...) and not Mojave

and btw is there any fix or workaround for MacBook Pro 4.1 trackpad issue?

thank you very much in advance for you help

It sounds like you have an APFS booting issue. Since your machine has an Intel chipset it should be relatively safe for you to apply the APFS ROM patch.

 

[Frantisekj]

The new iMovie update requires metal that are unsupported Macs are not capable of so yes wise choice to stay at the previous version unless a work around is found

thanks a lot for this info. i just have not updated it yet. ufff

 

[seyyed]

It sounds like you have an APFS booting issue. Since your machine has an Intel chipset it should be relatively safe for you to apply the APFS ROM patch.

thx very much for your help I will try it ASAP . is there any fix for the MacBook Pro 4.1 (early 2008) trackpad issue too?

 

[ezegalli]

Hello Everyone, I´m having problems to install Mojave on my MacBook Pro 8,1 Late 2011 (13" Core i5, Intel Graphics) following @dosdude1 guide http://dosdude1.com/mojave/

I was running High Sierra using AFPS on a SSD and successfully download Mojave image + created the bootable USB using the Pacther

When booting, i did all the steps but after a minute, i get stuck on ""No packages were eligible for install"

After reading the FAQs, i checked the date using the terminal and date is ok
I do also format, again, my drive using AFPS (GUID) and already tried with Mac OS Journal... but i do always get the same message after 1 minute of installing time


If someone knows how to fix this, i will be really appreciated, thanks in advaced

 

[Larsvonhier]

Latest Sec. Update 2019-001 beta also fully operational/patchable and with working CCFL patch (on MBP4,1):

 

[tzmmtz]

Previously I was using Sierra Patcher on Mac Pro 3,1 but now migrated that machine to a 2019 MacBook Pro. Upon restart I get the SIP warning that it is enabled. Which perhaps makes sense since I used Apple migration tool. I thought if I downloaded the Mojave installer from Apple and ran it the message would go away. But it doesn’t.

Here is the screenshot.

Any thoughts how I can make this laptop behave like a non-patched Mojave since this 2109 model doesn’t need the patcher and therefore SIP can be enabled.

Thanks,
Todd

 

[LuisN]

Previously I was using Sierra Patcher on Mac Pro 3,1 but now migrated that machine to a 2019 MacBook Pro. Upon restart I get the SIP warning that it is enabled. Which perhaps makes sense since I used Apple migration tool. I thought if I downloaded the Mojave installer from Apple and ran it the message would go away. But it doesn’t.

Here is the screenshot.

Any thoughts how I can make this laptop behave like a non-patched Mojave since this 2109 model doesn’t need the patcher and therefore SIP can be enabled.

Thanks,
Todd

Delete the kext from /Library/Extensions. I think it's called "SIPManager.kext"

 

[tzmmtz]

I didn't find SIPManager.kext but I did find com.dd1.SIPLD in /Library/LaunchAgents. After deleting that the message went away on restart. If there is anything else I should remove from this previous Sierra Patched volume please let me know.

 

[avz]

thx very much for your help I will try it ASAP . is there any fix for the MacBook Pro 4.1 (early 2008) trackpad issue too?

Not that I am aware of. Your trackpad is old and seen as a mouse by the system. I have a late 2008 unibody MB with a multitouch gestures. There is a world of difference between early 2008 and late 2008. Innovation seems to be at its peak at this point.

 

[Larsvonhier]

Not that I am aware of. Your trackpad is old and seen as a mouse by the system. I have a late 2008 unibody MB with a multitouch gestures. There is a world of difference between early 2008 and late 2008. Innovation seems to be at its peak at this point.

Don't confuse MacBook 4,1 with MacBook Pro 4,1. The Pro has a fully supported multi-touch trackpad whereas the MB4,1 and MB5,2 lack suitable kexts to enable most features. If the top case of a MacBook Pro 4,1 has been replaced with one from a MBPro3,1 though, you might end up with the same lack of features...

 

[LuisN]

I didn't find SIPManager.kext but I did find com.dd1.SIPLD in /Library/LaunchAgents. After deleting that the message went away on restart. If there is anything else I should remove from this previous Sierra Patched volume please let me know.

Sorry, I didn't notice your old installation was Sierra. I guess Sierra has some different patches than Mojave

 

[avz]

Sorry, I didn't notice your old installation was Sierra. I guess Sierra has some different patches than Mojave

I believe that with regard to SIP patch there is no difference between Mojave and Sierra. It just not enough to delete just the kext(which he obviously already done).

 

[Flacko]

I didn't find SIPManager.kext but I did find com.dd1.SIPLD in /Library/LaunchAgents. After deleting that the message went away on restart. If there is anything else I should remove from this previous Sierra Patched volume please let me know.

As you have found, migration is far from foolproof and does tend to copy unwanted remains of apps to the new Mac. I always do a manual restore when starting afresh with new system especially on a supported device. This does take time though! I just had a look on my cMP3.1 running a patched Mojave (not Sierra) and these are some of the patcher files etc:

Library/LaunchAgents/com.dd1.SIPLD.plist. Library/LaunchAgents/dosdude1.patchUpdater.plist
Library/Extensions/LegacyUSBInjector.kext. Library/Extensions/LegacyUSBVideoSupport.kext
Library/Extensions/SIPManager.kext

You may find using EtreCheckPro useful as it will give you a list of all the unsigned kexts and files in your new system and paths so you can remove them. A free demo, but limited version, is available in the Apple App Store.

 

[joevt]

I have an old Mojave 10.14.3 installer that I downloaded months ago (I can't download a newer one? - I'll use the 10.14.4 updater and the 10.4.5 combo updater on another partition). I used macOS Mojave Patcher 1.3.3 to create a USB installer. I started the installer and got an error "No packages were eligible for install". The patcher documentation says I should change the date using Terminal.app. I checked the date in the installer using Terminal.app and it appears to be correct (Oct 26, 2019). Then I remembered reading something about Apple certificates expiring Oct 24 so I tried setting the date to Oct 23. Now the installer appears to work. Is this a real problem or would it have worked if I set the date to Oct 26 (even though it was already set to Oct 26)? I'll try again on another partition.

 

[Flacko]

I have an old Mojave 10.14.3 installer that I downloaded months ago (I can't download a newer one? - I'll use the 10.14.4 updater and the 10.4.5 combo updater on another partition). I used macOS Mojave Patcher 1.3.3 to create a USB installer. I started the installer and got an error "No packages were eligible for install". The patcher documentation says I should change the date using Terminal.app. I checked the date in the installer using Terminal.app and it appears to be correct (Oct 26, 2019). Then I remembered reading something about Apple certificates expiring Oct 24 so I tried setting the date to Oct 23. Now the installer appears to work. Is this a real problem or would it have worked if I set the date to Oct 26 (even though it was already set to Oct 26)? I'll try again on another partition.

Here is a good article that explains the problem:

Beware Apple security certificates after 24 October: they may have expired

Don’t rely on being able to use any Apple installer package unless it has been downloaded recently: its certificate is about to expire.

eclecticlight.co

Basically if you have an installer that you downloaded before 24 October 2019 it is likely that it will not work as some of the Certificates have expired. Downloading after 24th October should be ok as Apple have been updating the certificates. Probably means all those backed up old installers are now useless!
Edit: Or like you found you could change the time on the computer to before 24 October 2019.

 

[RK78]

BUMPING AS I'VE HAD ZERO REPLIES AFTER SEVERAL DAYS:

Running 10.14.6 (newly installed) on iMac 10,1 from HFS+ volume. Unable to boot into recovery mode. At CMD-R or Restart using boot picker (option boot), always get no entry symbol. Both diskutil list and boot picker show 10.14.6 recovery partition.

Any help greatly appreciated.

And some further questions, if I may :

-Is there some reason why booting to recovery mode might be disallowed? Have also tried from an APFS volume, and similarly get the no entry symbol. No reason to think the recovery partitions are damaged.

-Just discovered that Mojave via the patcher apparently needs to run with SIP disabled ("SIP Disabler Patch") Wondering why? Would think that if some SIP protected files need to be modified, that at least SIP would be restored afterwards. Do not want to run with SIP constantly disabled. In that regard, ran sudo csrutil clear, which showed "successfully enabled SIP + now restart." After restarting, saw from csrutil status that SIP was still disabled. If SIP can't be enabled, this would be a real deal breaker. Would think that if this is so, that the documentation would clearly state this.

(Have written directly to dosdude several days ago, to address offered for further suppport, also with zero response -- very disheartening)

 

[TimothyR734]

BUMPING AS I'VE HAD ZERO REPLIES AFTER SEVERAL DAYS:



And some further questions :

-Is there some reason why booting to recovery mode might be disallowed? Have also tried from an APFS volume, and similarly get the no entry symbol. No reason to think the recovery partitions are damaged.

-Just discovered that Mojave via the patcher apparently needs to run with SIP disabled ("SIP Disabler Patch") Wondering why? Would think that if some SIP protected files need to be modified, that at least SIP would be restored afterwards. Do not want to run with SIP constantly disabled. In that regard, ran sudo csrutil clear, which showed "successfully enabled SIP + now restart." After restarting, saw from csrutil status that SIP was still disabled. If SIP can't be enabled, this would be a real deal breaker.

(Have written directly to dosdude several days ago, to address offered for further suppport, also with zero response -- very disheartening)

[automerge]1572111016[/automerge]
Try running this in the terminal as far as SIP it needs to be disables if you are you macOS Mojave on an unsupported Mac as certain apps and settings could become broken and unusable with SIP for example if graphics acceleration stopped working with SIP enabled it would make you Mac unusable I have running my iMac mid 2009 with SIP disabled since High Sierra no issues

 

[RK78]

Thanks, but can you please explain exactly what this script does? Besides dealing with booting to the recovery partition, does it also allow SIP to be enabled, or directly re-enable SIP?

 

[TimothyR734]

it should bring back the recovery partition

 

[Infografix]

BUMPING AS I'VE HAD ZERO REPLIES AFTER SEVERAL DAYS:



And some further questions, if I may :

-Is there some reason why booting to recovery mode might be disallowed? Have also tried from an APFS volume, and similarly get the no entry symbol. No reason to think the recovery partitions are damaged.

-Just discovered that Mojave via the patcher apparently needs to run with SIP disabled ("SIP Disabler Patch") Wondering why? Would think that if some SIP protected files need to be modified, that at least SIP would be restored afterwards. Do not want to run with SIP constantly disabled. In that regard, ran sudo csrutil clear, which showed "successfully enabled SIP + now restart." After restarting, saw from csrutil status that SIP was still disabled. If SIP can't be enabled, this would be a real deal breaker. Would think that if this is so, that the documentation would clearly state this.

(Have written directly to dosdude several days ago, to address offered for further suppport, also with zero response -- very disheartening)

Please understand that DosDude and others who work on this stuff do so as a volunteer effort (read: not paid) in addition to real jobs and etc that make their actual living. While it can be frustrating to wait for days for someone to offer a useful response to the question, this is not a live tech support service, it is a user forum.

As for your issue with the recovery partition:

When you ran post install on your Mojave installation, did you select the option for the recovery partition patch? It is not selected by default. If you do that, and run the setup you should be able to start up from recovery mode, I believe.

Also, yes, SIP has to be continually disabled, for Patch Updater to run, as well as MacOS will "correct" itself otherwise from some of the modifications done to the OS. If this is a dealbreaker, no one is making you use the patch, you can still run High Sierra without modifications on your system and it's a currently supported OS by Apple. This project is invaluable for us who have abandoned systems that don't even get OS support that far, and as for me, I'm willing to ditch SIP to have it. I had secure Mac computing for the entire existence of MacOS X without SIP before it was even a thing; I just compute safely, and don't futz in my system without knowing what I'm doing.

 

[TimothyR734]

Here is a good article that explains the problem:

Beware Apple security certificates after 24 October: they may have expired

Don’t rely on being able to use any Apple installer package unless it has been downloaded recently: its certificate is about to expire.

eclecticlight.co

Basically if you have an installer that you downloaded before 24 October 2019 it is likely that it will not work as some of the Certificates have expired. Downloading after 24th October should be ok as Apple have been updating the certificates. Probably means all those backed up old installers are now useless!
Edit: Or like you found you could change the time on the computer to before 24 October 2019.

Also if you keep a copy of the Apple Beta software profile download a new copy as it is mostly like expired to and if you have downloaded a Apple Dev beta Profile from Beta profiles they are expired

 

[RK78]

Also if you keep a copy of the Apple Beta software profile download a new copy as it is mostly like expired to and if you have downloaded a Apple Dev beta Profile from Beta profiles they are expired

Please understand that DosDude and others who work on this stuff do so as a volunteer effort (read: not paid) in addition to real jobs and etc that make their actual living. While it can be frustrating to wait for days for someone to offer a useful response to the question, this is not a live tech support service, it is a user forum.

As for your issue with the recovery partition:

When you ran post install on your Mojave installation, did you select the option for the recovery partition patch? It is not selected by default. If you do that, and run the setup you should be able to start up from recovery mode, I believe.

Also, yes, SIP has to be continually disabled, for Patch Updater to run, as well as MacOS will "correct" itself otherwise from some of the modifications done to the OS. If this is a dealbreaker, no one is making you use the patch, you can still run High Sierra without modifications on your system and it's a currently supported OS by Apple. This project is invaluable for us who have abandoned systems that don't even get OS support that far, and as for me, I'm willing to ditch SIP to have it. I had secure Mac computing for the entire existence of MacOS X without SIP before it was even a thing; I just compute safely, and don't futz in my system without knowing what I'm doing.

Understood that dosdude might not have time to reply immediately, but thought that after 4 days I might at least have heard something back.

Now that I know that, for all intents and purposes, SIP can not be enabled, I will have to consider whether I want to continue running Mojave when HSierra is EOL next year -- only reason I started down this path. It does involve some additional expense for several very necessary programs that won't otherwise run in 10.14.

And thanks for the information about SIP needing to remain disabled, unless I missed it, which is quite possible, would think that somewhere in the documentation this should be clearly stated. Had I known, I probably wouldn't have gotten involved in the first place. At least that's clear now.

And I totally get that running with SIP disabled might for some be preferable to running a completely unsupported OS. Difficult to evaluate the tradeoff involved.

 

[TimothyR734]

Understood that dosdude might not have time to reply immediately, but thought that after 4 days I might at least have heard something back.

Now that I know that, for all intents and purposes, SIP can not be enabled, I will have to consider whether I want to continue running Mojave when HSierra is EOL next year -- only reason I started down this path. It does involve some additional expense for several very necessary programs that won't otherwise run in 10.14.

And thanks for the information about SIP needing to remain disabled, unless I missed it, which is quite possible, would think that somewhere in the documentation this should be clearly stated. Had I known, I probably wouldn't have gotten involved in the first place. At least that's clear now.

And I totally get that running with SIP disabled might for some be preferable to running a completely unsupported OS. Difficult to evaluate the tradeoff involved.

yes it is a trade off as with High Sierra on our unsupported Macs it is the last OS where light mode is not broken for macOS Mojave we had the the hybrid patches to at least have a white menu bar no transparency and macOS Mojave is the last OS to support 32 bit Apps macOS Catalina no support for 32 bit apps what so ever we had to recreate patches to fix light mode photos app is only partially working iCloud has issues syncing at times Maps is partially working as most of tases require metal which our old Macs don't support But I have never ever had issues with SIP disabled and with macOS Catalina you get nagging authorize warning when installing apps outside the App Store