macOS 10.14 Mojave on Unsupported Macs Thread

[Project Alice]

Good morning everyone,

I am wondering how many MacBook 5,2 Early 2009 users are here? Besides me, there is at least one.

Let's join forces to conquer MacBook 5,2 specific probs, e.g. iSight or Wifi or ...

Looking forward to hearing from you.

Heinz

I have one, but I use it as my main laptop so it stays on High Sierra until mojave is released or until most the bugs are worked out.

I know that dosdude1 also has at least one of these, so I'm sure he's just as interested as we are to have it working perfectly. Mine currently has zero flaws running HS, I did however change the wifi card out about a year ago because the one it had didn't work in 10.12+

 

[coolio2004]

On Mojave beta 4 I don't have any App Store crashes neither on different unsupported Macs, and the front page with "video demo app" running in background doesn't give any issues, so could be the patching or the Video Card typology better/less supported in OpenGL rendering vs Metal adaptive contents.
It seems that Legacy IntelHD and Nvidia Video Cards react better than legacy AMD/ATI , just a supposition.

I can agree. Appstore crashes on my iMac 11.2 with HD 4670. Same image on my MacMini 5.2 with HD 6630M no crash - but no acceleration.

 

[h123]

I have one, but I use it as my main laptop so it stays on High Sierra until mojave is released or until most the bugs are worked out.

I know that dosdude1 also has at least one of these, so I'm sure he's just as interested as we are to have it working perfectly. Mine currently has zero flaws running HS, I did however change the wifi card out about a year ago because the one it had didn't work in 10.12+

Hi Project Alice,

my MB 5,2 works fine with High Sierra, too. Fortunatly, WiFi Card worked right away.

Regards
Heinz

 

[0403979]

Good morning everyone,

I was wondering how many MacBook 5,2 Early 2009 users are here? Besides me, there is at least one.

Let's join forces to conquer MacBook 5,2 specific probs, e.g. iSight or Wifi or ...

Looking forward to hearing from you.

Heinz

My mother has one but she's using Snow Leopard. I don't think I can get her to update to Mojave.

 

[jackluke]

This is not a fix for the double boot. This is a fix that @jackluke and I found to fix a grey screen + kernel panic on Penryn architecture systems. Totally unrelated problem.

I believe the double boot is a result of a corrupt/modified EFI partition. I had some troubles of my own (corrupted SSD, had to wipe and am reinstalling now) so I can't do any testing immediately but I should be running DP4 by midnight and can continue testing.
[doublepost=1532310850][/doublepost]
Same here. @jackluke, are you certain that this IOAccelerator replacement actually does anything? I tested it awhile back on my MB7,1 and nothing changed at all. I have full acceleration either way, and graphical glitches either way.
[doublepost=1532311163][/doublepost]Also, @jackluke, just a question I've been meaning to ask you for a while -- how long did it take you to find which file in UserEventPlugins was the culprit? Did you do something clever like a binary search or just a one-by-one replacement? Because that would suck.

EDIT: Just realized I mentioned you 3 times. I'm sorry, jackluke.

No worries regard mentioning. Glad you're back on forum.

Ah then double boot chime is due to the EFI partition. Good to know. Anyway I don't have that issue.

To me if I don’t replace IOAccelerator I get some weird behaviors in Finder in managing folders especially if they are in View mode list.

The main C2D KP fixing credit is yours, founding culprit was been a child's play, it took me less than an hour, it has been fast method since I was booting from an external SSD.


I discovered it in this way:

Replacing the entire UserEventPlugins folder to me landed to a black screen right after stage2 apple logo.
Replacing only the first 20 plugins instead worked.

So I understood that less then 26 could be culprits of a general C2D KP.
Moreover in High Sierra there are two more plugins not needed in Mojave.

Then I restricted the field using a non-clever method, and lastly one by one it has worked.

That’s not all, to show that telemetry.plugin is not needed at all, I have used Mojave beta 2 for about a week deleting completely that plugin, I have encountered no issues.

Feel free to investigate with a clever method in binary patching but it seems there aren't any logs or clues to understand why telemetry.plugin crashes on Mojave unsupported Penryn C2D Macs.

And replacing telemetry.plugin from High Sierra seems a very good solution, as we have seen in other replacing steady method like AppleHDA, IOUSB*** look ever a useful solution in general.

I guess neither Apple engineers could explain exactly why telemetry.plugin crashed, so that's the true reason they dropped supporting C2D (I am joking with this sentence).
[doublepost=1532337437][/doublepost]

Turns out the double boot-chime is still here in a fresh install of DP4. Not sure what's going on but it doesn't appear to cause any problems. Wasn't happening until I selected the SSD in Startup Disk, for what it's worth. Definitely related to the EFI partition or the OS though, your boot ROMs are safe.

Also, just for fun: Go checkout the Privacy settings in System Preferences and scroll to the bottom. Anybody else getting attacked by a giant gear?

Giant Automation Gear appears also on a supported MBP with Mojave beta 4.

 

[0403979]

No worries regard mentioning. Glad you're back on forum.

Ah then double boot chime is due to the EFI partition. Good to know.

To me if I don’t replace IOAccelerator I get some weird behaviors in Finder in managing folders especially if they are in View mode list.

The main C2D KP fixing credit is yours, founding culprit was been a child's play, it took me less than an hour, it has been fast method since I was booting from an external SSD.


I discovered it in this way:

Replacing the entire UserEventPlugins folder to me landed to a black screen right after stage2 apple logo.
Replacing only the first 20 plugins instead worked.

So I understood that less then 26 could be culprits of a general C2D KP.
Moreover in High Sierra there are two more plugins not needed in Mojave.

Then I restricted the field using a non-clever method, and lastly one by one it has worked.

That’s not all, to show that telemetry.plugin is not needed at all, I have used Mojave beta 2 for about a week deleting completely that plugin, I have encountered no issues.

Feel free to investigate with a clever method in binary patching but it seems there aren't any logs or clues to understand why telemetry.plugin crashes on Mojave unsupported Penryn C2D Macs.

And replacing telemetry.plugin from High Sierra seems a very good solution, as we have seen in other replacing steady method like AppleHDA, IOUSB*** look ever a useful solution in general.

I guess neither Apple engineers could explain exactly why telemetry.plugin crashed, so that's the real reason they dropped supporting C2D (I am joking with this sentence).
[doublepost=1532337437][/doublepost]

Giant Automation Gear appears also on a supported MBP with Mojave beta 4.

They probably used the plugin to crash C2Ds on purpose.

 

[jackluke]

I found EFI firmware files in the InstallESD image for Mojave. This would probably work for all other versions although I have not tested it. Perhaps these files are useful to someone?View attachment 772267

The files.scap are only the Boot ROM version upgrade this will be installed into the hidden EFI partition and maybe into /usr/standalone/i386/ but it seems no more here.

While the files.fd are the real EFI EEPROM firmware upgrade.

But none of these contain the two most important Macs Serial numbers to identify your real machine; one printed on the logic board and the other (both) embedded inside the EFI ROM code (or on the aluminium bottom cover).

The machine serial number typically has eleven characters, while the logic board serial number someone more, depending from the model.
But they are different on the same Mac, both embedded into the EFI EEPROM CHIP from factory.

edit:

I'm becoming expert since I bricked MBA2,1 EFI CHIP

 

[0403979]

The files.scap are the Boot ROM version upgrade this will be installed into the hidden EFI partition and maybe into /usr/standalone/i386/ but it seems no more here.

While the files.fd are the real EFI EEPROM firmware upgrade.

But none of these contain the two most important Macs Serial numbers to identify your real machine; one printed on the logic board and the other (both) embedded inside the EFI ROM code (or on the aluminium bottom cover).

The machine serial number typically has eleven characters, while the logic board serial number someone more, depending from the model.
But they are different on the same Mac, both embedded into the EFI EEPROM CHIP from factory.

edit:

I'm becoming expert since I bricked MBA2,1 EFI CHIP

So these aren’t useful then?

Edit: The "joke" was removed.

 

[jackluke]

So these aren’t useful then (mr expert)?

I don't understand your sense of humor.

edit:

No controversy on my side, you are still too young.

 

[tsialex]

So these aren’t useful then (mr expert)?

No. It's the unpersonalised BootROMs that Apple puts to update Macs with every new release.

 

[jackluke]

No. It's the unpersonalised BootROMs that Apple puts with every release.

Thank you.

 

[saudor]

I wonder if there’s any news on continuity activation tool...

It works perfect on my 2010 with upgraded WiFi card

 

[jiojio12]

Hi, I dont know if this is a dumb question. But I installed mojave on my 2011 imac with a clean install on an external hard drive. So my question is does the patch installer affect my native 10.13 installed on my internal in anyway, or are all changes confined to the external running 10.14?

 

[tsialex]

Thank you.

I'm not expert and people who really know please correct me but you need three infos to personalize a .fd BootROM file:

1) The System Serial Number = SSN
2) The Order Number/SKU
3) The Logic Board Serial Number = LBSN

When Apple replaces your logic board, the new one has the OrderNumber/SKU and LBSN from factory, the Blank Board Serializer are then used to insert your SSN on the new board. Without this three infos present on the BootROM, you can't access iCloud/iMessage/Facetime.

Usually the LBSN is printed on a label on your logic board, so you just need the SSN and OrderNumber/SKU to reconstruct the full personalised BootROM.

 

[jackluke]

I'm not expert and people how really know please correct me but you need three infos to personalize a .fd BootROM file:

1) The System Serial Number = SSN
2) The Order Number/SKU
3) The Logic Board Serial Number = LBSN

When Apple replaces your logic board, the new one has the OrderNumber/SKU and LBSN from factory, the Blank Board Serializer are then used to insert your SSN on the new board. Without this three infos present on the BootROM, you can't access iCloud/iMessage/Facetime.

Usually the LBSN is printed on a label on your logic board, so you just need the SSN and OrderNumber/SKU to reconstruct the full personalised BootROM.

Absolutely agree with you, and I am sure you are an expert in this field (more than me).

I appreciated the word "unpersonalised", best word to summarize the everything.

But before, I wanted simply to be ironic on the fact I recently bricked an EFI EEPROM CHIP, warning the others to don't try it without having the proper skills/tools for fixing.

 

[fabiojuniorr]

It works perfect on my 2010 with upgraded WiFi card

I have a USB dongle, but I’m not sure if I should try it, last time I’ve tried on Sierra, I had to restore it and lost all my data

 

[tsialex]

Absolutely agree with you, and I am sure you are an expert in this field (more than me).

I appreciated the word "unpersonalised", best word to summarize the everything.

But before, I wanted simply to be ironic on the fact I recently bricked an EFI EEPROM CHIP, warning the others to don't try it without having the proper skills/tools for fixing.

I'm preparing a guide to edit the .fd file and personalize it, it's easy but the details are crucial - a lot of people with Mac Pros are having trouble with it. I'll post a link here later on.

 

[0403979]

Hi, I dont know if this is a dumb question. But I installed mojave on my 2011 imac with a clean install on an external hard drive. So my question is does the patch installer affect my native 10.13 installed on my internal in anyway, or are all changes confined to the external running 10.14?

No question is dumb unless you already know the answer, in which case you would not be asking the question. As far as I know all changes are applied to the external Mojave installation and do not affect any of your other operating systems.

 

[Brale]

Hi guys,
I tried to install Mojave on my MacBook Air 3,2 (Late 2010) but After i opened the macOS Post Install tool i saw that MBA 3,2 is not on the list. There is 3,1 or 4,1 but no 3,2 so I selected 4,1. Is there any specific reason or is there a some fix to make it work or I'm just out of luck with my MBA?
Tnx

Update 1: I replaced com.apple.telemetry.plugin with HS version and I was able to boot to Welcome screen but now my keyboard and trackpad not working. Stuck on Welcome screen.

Update 2: I fixed keyboard/trackpad issue by replacing IOUSBHostFamily.kext.

I'm able to boot to Mojave but still wondering why MBA 3,2 is not on the macOS Install Patch list?

 

[jackluke]

Hi guys,
I tried to install Mojave on my MacBook Air 3,2 (Late 2010) but After i opened the macOS Post Install tool i saw that MBA 3,2 is not on the list. There is 3,1 or 4,1 but no 3,2 so I selected 4,1. Is there any specific reason or is there a some fix to make it work or I'm just out of luck with my MBA?
Tnx

Update: I replaced com.apple.telemetry.plugin with HS version and I was able to boot to Welcome screen but now my keyboard and trackpad not working. Stuck on Welcome screen.

You are almost there, to fix keyboard/trackpad relaunch Mojave Patcher "Post Install" selecting as your Volume your Mojave disk, and as patch options "USBOHCI Support patch", maybe select "USB support injector" too, then force rebuild kernel cache.

Select also for your MBA 3,2 "Legacy Video card patch" and "Legacy Audio patch"

The steps are perfectly explained http://dosdude1.com/mojave/

 

[Loyd-01a]

just copied those 5 files from backup 10.13.5 IOUSB*.kexts and use kextbeast 2.01 to install and my FaceTime video is now working with Mojave B4 , full dynamic wallpaper patch is also working , great stuff guys...

Could you please share those 5 files from backup 10.13.5 IOUSB*.kexts ? (I'am on 10.13.5)
Thank you

 

[dosdude1]

Hi guys,
I tried to install Mojave on my MacBook Air 3,2 (Late 2010) but After i opened the macOS Post Install tool i saw that MBA 3,2 is not on the list. There is 3,1 or 4,1 but no 3,2 so I selected 4,1. Is there any specific reason or is there a some fix to make it work or I'm just out of luck with my MBA?
Tnx

Update 1: I replaced com.apple.telemetry.plugin with HS version and I was able to boot to Welcome screen but now my keyboard and trackpad not working. Stuck on Welcome screen.

Update 2: I fixed keyboard/trackpad issue by replacing IOUSBHostFamily.kext.

I'm able to boot to Mojave but still wondering why MBA 3,2 is not on the macOS Install Patch list?

Just a mistake on my part. Just apply patches for the 3,1, it's the same machine pretty much.

 

[flygbuss]

A small observation I made: When I got my MBP 8,1 to run Mojave after I reseated the RAM I decided
to go for APFS instead of HFS+
After that the book chimes now two times like others described it here as well.
Didn't do it when I was having the OS on HFS+ before..

 

[pkouame]

I've got that in the Privacy panel too, this will be a Mojave beta bug rather than an unsupported bug.
Have you tried to add a custom icon to a file or folder, thought I would try and see if they have fixed the ever present bug in High Sierra where it squishes the replacement icon into a square format, now you get the correct aspect ratio but the new icon is blurred. Blimey!

No I never did. Even funnier, it never looked like a gear until I clicked on it.

 

[jackluke]

I have a USB dongle, but I’m not sure if I should try it, last time I’ve tried on Sierra, I had to restore it and lost all my data

Did had a similar issue in past, it's due to the wrong Mediatek/Ralink Driver pkg installer, there are many floating in the web, if you find the right one for your dongle it will work on any MacOS release starting from El Capitan till Mojave.

EDIT:
Forgot to say a very important thing, to use any third party USB wifi dongle, from El Capitan you should have SIP disabled.

[doublepost=1532353863][/doublepost]

Could you please share those 5 files from backup 10.13.5 IOUSB*.kexts ? (I'am on 10.13.5)
Thank you

TimothyR734 has uploaded some pages ago all the 5 Kexts. But I don't understand if you need them for your High Sierra installation or Mojave adaptation.

edit: page 136

Ok, that's not very usual, they are from 10.13.6 , but I bet they work also on a High Sierra 10.13.5 installation.