macOS 10.14 Mojave on Unsupported Macs Thread

[thewebgal]

Excellent!! Mojave beta installed just fine tonight - no fancy stuff - Just ran the app for the install!
Of course, I had already swapped in the Seagate SSDD, a new Wifi card and the NVidia GTX680 card!

Thanks to ALL you folks for ALL your help getting here! (esp DosDude!)

 

[schwab]

The steps appear ok, retry last time re-replacing the QT1.app Info.plist from Contents into the long Airportbrcm4360 Contents

If still doesn't work, not sure but you could try to replace the entire IO80211Family.kext from HS into Mojave S/L/E

Still no bluetooth with the other info.plist...I attached the Terminal output.

Quickertek may be able to help send me the correct kext file orinfo.plist file ... their tech is going to view this thread hopefully. Thanks again....at least my WiFi orks using this mcard2

 

[pkouame]

Out of interest, can you make that but inverted? So apps dark, sidebars and stuff light?

A possibility.
But my primary focus is to enable a vibrant mode where it was intended to be. Currently vibrantDark is the only mode that works, so I call it instead of vibrantLight. Tweaking the amount of vibrancy on top of that will be the icing on the cake.

 

[ASentientBot]

Just made a (not thoroughly tested) applet to change the dark mode flag in a given application bundle.

I'll stop cross-posting things from that thread now, but I thought maybe some people would find this useful.

 

[TimothyR734]

Just made a (not thoroughly tested) applet to change the dark mode flag in a given application bundle.

I'll stop cross-posting things from that thread now, but I thought maybe some people would find this useful.

Thank You

 

[MoHaya]

Hi guys I have a quick favor to ask, if any one who has a 13 inch aluminum MacBook 5,1 2008, or a 13 inch 2009 MacBook Pro 5,5. Can they please tell me if their Track pads are detected or not, and which version of Mojave beta their using. Because both of the track pads on my machines are not detected. Thanks

 

[TimothyR734]

Hi guys I have a quick favor to ask, if any one who has a 13 inch aluminum MacBook 5,1 2008, or a 13 inch 2009 MacBook Pro 5,5. Can they please tell me if their Track pads are detected or not, and which version of Mojave beta their using. Because both of the track pads on my machines are not detected. Thanks

I have a mid 2009 White MacBook as stated in the OP the Tracpads are not fully functional

 

[jackluke]

Still no bluetooth with the other info.plist...I attached the Terminal output.

Quickertek may be able to help send me the correct kext file orinfo.plist file ... their tech is going to view this thread hopefully. Thanks again....at least my WiFi orks using this mcard2

Try this modified Info.plist based on the Mojave one with your two dev/ven IDs inside.
Just follow all the previous steps and mostly rebuild the kextcache.
Replace this file I've attached within your Mojave path:
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/

 

[schwab]

Try this modified Info.plist based on the Mojave one with your two dev/ven IDs inside.
Just follow all the previous steps and mostly rebuild the kextcache.
Replace this file I've attached within your Mojave path:
/System/Library/Extensions/IO80211Family.kext/Contents/PlugIns/AirPortBrcm4360.kext/Contents/

Thank you, however, Bluetooth is still not available and I have attached my Terminal output having followed your instructions.

 

[jackluke]

Thank you, however, Bluetooth is still not available and I have attached my Terminal output having followed your instructions.

The Terminal output appears correct, the patched Info.plist has been withdrawn from Mojave beta 9 build 18A377a , probably is related to this, which Mojave beta version are you using ?

Anyway there is another possibility, copy from your High Sierra S/L/E the IO802Family.kext to the Mojave S/L/E (take a backup first of your IO802Family.kext from Mojave), then after replaced the kext, launch the rebuild kextcache from Mojave Terminal.

 

[Badruzeus]

Thank you, however, Bluetooth is still not available and I have attached my Terminal output having followed your instructions.

1. Boot to RecoveryHD
2. Disable SIP: `csrutil disable`
3. Boot to Desktop
4. Rollback vanilla IO80211Family.kext on SLE, then..
5. Terminal:

cd /System/Library/Extensions
sudo mv AirPortBrcmNIC-MFG.kext AirPortBrcmNIC-MFG.kext.bak

6. Repair, rebuild prelinkedkernel && kernelcache:

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

7. Go to SysPref > Network: Remove All Interfaces, then..
8. Terminal:

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

9. Reboot, re-enable SIP.

If for unknown reason this method doesn't work, repeat Point (1-6), but with:

cd /System/Library/Extensions
sudo mv AirPortBrcmNIC-MFG.kext.bak AirPortBrcmNIC-MFG.kext

 

[schwab]

The Terminal output appears correct, the patched Info.plist has been withdrawn from Mojave beta 9 build 18A377a , probably is related to this, which Mojave beta version are you using ?

Anyway there is another possibility, copy from your High Sierra S/L/E the IO802Family.kext to the Mojave S/L/E (take a backup first of your IO802Family.kext from Mojave), then after replaced the kext, launch the rebuild kextcache from Mojave Terminal.

I am using macOS Mojave Version 10.14 Beta (18A353d)

I do not know what you mean by copying High Sierra S/L/E

 

[jackluke]

I am using macOS Mojave Version 10.14 Beta (18A353d)

I do not know what you mean by copying High Sierra S/L/E

Before attempting replacing from HighSierra take first a backup of your IO802Family.kext inside your Mojave S/L/E to the Desktop

You are still in Mojave beta 6, so there should be some differences with the beta9 Info.plist I've patched taking from IO802Family.kext beta9 Bundle, the fact is that you have no more your original AirPortbrcm4360.kext Info.plist, anyway try copying IO802Family.kext entirely from your working High Sierra S/L/E into your Mojave S/L/E

S/L/E is abbreviation for /System/Library/Extensions/

After you have replaced your HighSierra IO802Family.kext inside your Mojave S/L/E , probably you will lose WiFi too but just launch that "one line" Terminal command to rebuild kextcache, and at least WiFi will work again.

I cannot help you further than this.

 

[schwab]

1. Boot to RecoveryHD
2. Disable SIP: `csrutil disable`
3. Boot to Desktop
4. Rollback vanilla IO80211Family.kext on SLE, then..
5. Terminal:

cd /System/Library/Extensions
sudo mv AirPortBrcmNIC-MFG.kext AirPortBrcmNIC-MFG.kext.bak

6. Repair, rebuild prelinkedkernel && kernelcache:

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / && sudo update_dyld_shared_cache -force

7. Go to SysPref > Network: Remove All Interfaces, then..
8. Terminal:

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

9. Reboot, re-enable SIP.

If for unknown reason this method doesn't work, repeat Point (1-6), but with:

cd /System/Library/Extensions
sudo mv AirPortBrcmNIC-MFG.kext.bak AirPortBrcmNIC-MFG.kext

Thank you for your suggestions.

What does #4 mean?

 

[thegurgz]

Hi guys I have a quick favor to ask, if any one who has a 13 inch aluminum MacBook 5,1 2008, or a 13 inch 2009 MacBook Pro 5,5. Can they please tell me if their Track pads are detected or not, and which version of Mojave beta their using. Because both of the track pads on my machines are not detected. Thanks

I have a MBP 5,5 and the trackpad is detected for me. 10.14 Beta (18A377a) Never had any issues with trackpad detection.

 

[Badruzeus]

What does #4 mean?

I meant "unmodified" version of IO80211Family.kext from prev. backup as @jackluke has also suggested.

 

[AnonMac50]

I can’t test it (since I don’t have those machines), but has anyone tried getting the trackpad and multitouch kexts from El Capitan and putting them on Mojave? That might work.

 

[parrotgeek1]

As I stated before, if you have an APFS patched ROM, you must DESELECT the "APFS Patch" option in the post-install tool to prevent the extra EFI stuff being installed for systems that don't have APFS support in the BootROM. I have no way of checking this with the post-install tool, so you will need to deselect it manually before applying post-install patches.

Isn't there something called like FirmwareFeatures? But it might only be set on a supported apfs mac

 

[lumos]

Hi all,

please, can anyone tell me how can I check if my Mac Pro 3.1 is APFS boot compatible?
Can I test with a standard Hard Disk or I need an SSD?
How can I restore my backupped rom in case I want to go back? If yes how?

Thanks

Please, anyone can give me an answer?

Thanks

 

[TimothyR734]

Please, anyone can give me an answer?

Thanks

The 2008 3,1 will not be able to boot from APFS. without the APFS boot rom patcher

 

[jbarley]

The 2008 3,1 will not be able to boot from APFS. without the APFS boot rom patcher

We now have 2 options that allow a MP3,1 to boot APFS.
Flash the boot rom,
or use the "APFS Patch" option in the post-install tool"
which was made available in the Mojave Patcher version 1.2.0

 

[TimothyR734]

We now have 2 options that allow a MP3,1 to boot APFS.
Flash the boot rom,
or use the "APFS Patch" option in the post-install tool"
which was made available in the Mojave Patcher version 1.2.0

I have a macbook 5,2 and I applied the APFS patch in the post install and my APFS converted hdd with the latest beta of Mojave does not boot it only boot High Sierra HFS as it is the only hdd that is detected my APFS Mojave only appears as EFI

 

[jbarley]

The 2008 3,1 will not be able to boot from APFS. without the APFS boot rom patcher

I have a macbook 5,2 and I applied the APFS patch in the post install and my APFS converted hdd with the latest beta of Mojave does not boot it only boot High Sierra HFS as it is the only hdd that is detected my APFS Mojave only appears as EFI

Help me out here, this issue with your macbook 5,2 has what to do the MacPro 2008 3,1 you referred to in your earlier post.

 

[TimothyR734]

Help me out here, this issue with your macbook 5,2 has what to do the MacPro 2008 3,1 you referred to in your earlier post.

Well mine is a new model MacBook 2009 than a 3,1 2008 now would the thinking be if a 2009 MacBook won't boot APFs that a 2008 won't boot APFS as well so you need you need to use the APFS Boot Rom Patcher

 

[jbarley]

Well mine is a new model MacBook 2009 than a 3,1 2008 now would the thinking be if a 2009 MacBook won't boot APFs that a 2008 won't boot APFS as well so you need you need to use the APFS Boot Rom Patcher

Seems your logic is flawed because my 2008 MacPro 3,1 boots very well after using the APFS patch in the post install tool.
I went this route because my 3,1 fails each time I try the boot rom flash.