Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I’ve installed on a freshly formatted external usb hdd as hfs+ and ran the patcher on that drive and upon boot get the boot message “This version of Mac OS X is not supported on this platform!”
Have you checked that the file
/System/Library/CoreServices/PlatformSupport.plist
on the volume you're trying to boot from has your Board-Id and model listed.
 
  • Like
Reactions: TimothyR734
Have you checked that the file
/System/Library/CoreServices/PlatformSupport.plist
on the volume you're trying to boot from has your Board-Id and model listed.
I haven’t. Should I type something like the following in terminal using the Mojave installer USB?

Sudo nano /System/Library/CoreServices/PlatformSupport.plist
 
  • Like
Reactions: TimothyR734
I haven’t. Should I type something like the following in terminal using the Mojave installer USB?

Sudo nano /System/Library/CoreServices/PlatformSupport.plist
Well, first of all do you know your board-id and model? Make sure you know those first.

I've never used nano, because I'm a Unix-type person, but you can use whichever editor you're comfortable using.
 
  • Like
Reactions: TimothyR734
.
[doublepost=1535922672][/doublepost]I’ve no idea how to check and can only assume I can do that in terminal some how. I don’t currently know any of the required numbers. Need further research now.
 
  • Like
Reactions: TimothyR734
.
[doublepost=1535922672][/doublepost]I’ve no idea how to check and can only assume I can do that in terminal some how. I don’t currently know any of the required numbers. Need further research now.
If you About This Mac and System Report, under Hardware Overview you'll find Model Identifier. Mine for example is MacBookPro5,1 (its a late 2008 MacBookPro)

board-id is slightly harder. In Terminal, paste this command
ioreg -lp IOService | grep board-id
and hit Return

In the PlatformSupport.plist there's a section for supported models and a section for board-ids. Your Model Indentifier has to be in the models list and the board-id in the other list. If they're not already there, use your favourite editor to add them - use existing entries as templates. Either that or you can edit existing entries - it doesn't matter which ones. All that matters is that your values are in there somewhere.
 
I think there are two potential issues here. One is the stability of the APFS conversion routines in Disk Utility. As has been shown here, it is suboptimal in that the Recovery partition isn't moved into the main container as an APFS volume. The second is potential issues in the upgrade install. When upgrading to a from HFS High Sierra, I would recommend cloning your existing drive to an external, totally repartition and reformat the internal as APFS and then do a full install with migration from the external backup. That work swimmingly here on a MacPro 3,1 from another patched HS volume.
...but in my example the APFS recovery partition (disk2s3) seems to be in the same container as the APFS volume (disk2s2) on which Mojave is installed...however, I do not really understand what is the “synthesized” disk3 !!!
Thanks,
PJN
 
  • Like
Reactions: TimothyR734
...but in my example the APFS recovery partition (disk2s3) seems to be in the same container as the APFS volume (disk2s2) on which Mojave is installed...however, I do not really understand what is the “synthesized” disk3 !!!
Thanks,
PJN

The “synthesized” disk3 is the virtual disk contained in the container on physical disk2.
 
  • Like
Reactions: TimothyR734
.
[doublepost=1535922672][/doublepost]I’ve no idea how to check and can only assume I can do that in terminal some how. I don’t currently know any of the required numbers. Need further research now.

You don't need to edit that file, ever. Just set -no_compat_check as a boot arg and you'll be good.

- Disable SIP
- nvram boot-args="-no_compat_check"

Alternately, add it to com.apple.Boot.plist as a Kernel Flag.
 
Again: MacBook 5,2 Early 2009 iSight working

OK, here we go ( I am feeling victorious ;-) )

This led to a working iSight two times in succession.

1. Install Mojave DP 9 or later
2. Install El Capitan IOUSB*.kexts as described in TimothyR734s post incl. reboot
3. Check in System overview whether it says "integrated iSight Camera" or the like
4. Invoke PhotoBooth, watch splash screen message saying "no cam found" or the like
5. Install IOUSB*.kexts from TimothyR734s post incl. reboot
6. Check in System overview whether it STILL says "integrated iSight Camera" or the like
7. Invoke PhotoBooth, watch splash screen message -> no message is a good sign

Post your results here, please.

3. Sep. 2018 - Annotation:
- iSight picture is very dark
- fast movement in front of cam hangs Photo Booth
 
  • Like
Reactions: TimothyR734
Merci,

I understand.

And what, exactly, is supposed to be in the "synthetized" disk ?

My apologies for this weird question,

PJN

Exactly what I said, the container with all of the APFS partitions. It might be easier for you to think of this in terms of how virtual disks work with VMs like VirtualBox. Instead of using actual disk partitions on the users system disk, VirtualBox uses a virtual disk file which contains those partitions. The 'synthetized' disk could be considered to be analogous to the virtual disk file and the container being the partition map that holds those partitions. Note this is just a rough analogy but it gets to the crux of the idea.
 
Exactly what I said, the container with all of the APFS partitions. It might be easier for you to think of this in terms of how virtual disks work with VMs like VirtualBox. Instead of using actual disk partitions on the users system disk, VirtualBox uses a virtual disk file which contains those partitions. The 'synthetized' disk could be considered to be analogous to the virtual disk file and the container being the partition map that holds those partitions. Note this is just a rough analogy but it gets to the crux of the idea.

OK, Thanks,

I got it...

PJN
 
  • Like
Reactions: TimothyR734
My wifi card has an x on it and says wifi hardware not installed?? It's an atheros wifi card and is not on the unsupported list... I already tried the legacy wifi patcher twice but no result.. have tried the pram and the smc reset..no change...I have contacted dosdude1 via email and he told me to apply the legacy wifi patch but select force rebuild cache...I did that and still nothing..I'm at a lost...everything else works...even bluetooth...the wifi works in windows 7 that I'm dual booting with...so I'm not sure what is going on there.
 
  • Like
Reactions: TimothyR734
My wifi card has an x on it and says wifi hardware not installed?? It's an atheros wifi card and is not on the unsupported list... I already tried the legacy wifi patcher twice but no result.. have tried the pram and the smc reset..no change...I have contacted dosdude1 via email and he told me to apply the legacy wifi patch but select force rebuild cache...I did that and still nothing..I'm at a lost...everything else works...even bluetooth...the wifi works in windows 7 that I'm dual booting with...so I'm not sure what is going on there.
What MacBook pro model are you on? During Apple Hardware Test mine doesn't register any hardware problem too. But it stopped working with an x (hardware not installed for wifi). I'm on MacBook Pro 2010 7,1 it used to work before 10.14.
 
  • Like
Reactions: TimothyR734
What MacBook pro model are you on? During Apple Hardware Test mine doesn't register any hardware problem too. But it stopped working with an x (hardware not installed for wifi). I'm on MacBook Pro 2010 7,1 it used to work before 10.14.
Macbook Pro 2008 4,1
 
Macbook Pro 2008 4,1

The YouTube video that dosdude1 did last month


shows Mojave running on a MacBook Pro 4,1 and notes that, like other models, you will have to open up the unit and replace your wifi card with a supported card. I would suggest that you make sure the replacement card supports simultaneous dual-band so that AirDrop works and that it doesn't require the legacy wifi patch if possible. The AirPort Extreme (0x14E4, 0x8E) Broadcom BCM43xx 1.0 (5.106.98.102.30) that I purchased off of Amazon last year for my MacPro 3,1 achieves both.
 
Last edited:
If you About This Mac and System Report, under Hardware Overview you'll find Model Identifier. Mine for example is MacBookPro5,1 (its a late 2008 MacBookPro)

board-id is slightly harder. In Terminal, paste this command
ioreg -lp IOService | grep board-id
and hit Return

In the PlatformSupport.plist there's a section for supported models and a section for board-ids. Your Model Indentifier has to be in the models list and the board-id in the other list. If they're not already there, use your favourite editor to add them - use existing entries as templates. Either that or you can edit existing entries - it doesn't matter which ones. All that matters is that your values are in there somewhere.
I can confirm that my mac board ID is contained in the SupportedBoardId list and my model number is also contained within the SupportedModelProperties list. Still won’t successfully boot with these values present.
 
  • Like
Reactions: TimothyR734
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.