macOS 10.14 Mojave on Unsupported Macs Thread

[Vyzantion]

Dosdude1, you„re the man. O was able to install, thanks to your patch, Mojave on my old legacy Hackintosh. It has Nvidia GeForce 6200 and Mojave works on it. This is a remarcable achievement. Dark mode does not work properly and other things that did not ran on High Sierra do not work either, but the desktop is present. I need to use an older Clover build from Tonymacx86, tweaked for High Sierra. then update to the latest official version of Clover, in order to boot the pen drive and install. If you want, I suggest you create a version of your tool for Hackintoshes, including Clover and FakeSMC into it. Or you could share some of your expertise with Hackintosh boards like Insanelymac or Tonymacx86, in order to help us save money on new hardware, and I am sure you will get many users being grateful. Good job! Keep it going!

 

[0403979]

Dosdude1, you„re the man. O was able to install, thanks to your patch, Mojave on my old legacy Hackintosh. It has Nvidia GeForce 6200 and Mojave works on it. This is a remarcable achievement. Dark mode does not work properly and other things that did not ran on High Sierra do not work either, but the desktop is present. I need to use an older Clover build from Tonymacx86, tweaked for High Sierra. then update to the latest official version of Clover, in order to boot the pen drive and install. If you want, I suggest you create a version of your tool for Hackintoshes, including Clover and FakeSMC into it. Or you could share some of your expertise with Hackintosh boards like Insanelymac or Tonymacx86, in order to help us save money on new hardware, and I am sure you will get many users being grateful. Good job! Keep it going!

Unfortunately the patcher was not and most likely will not be developed for Hackintoshes, it was developed for Macintoshes. You are free to use the patcher at your own risk on any device you chose but the functionality of said patcher cannot be guaranteed on unsupported devices and should be used with caution even on supported devices. Neither me, nor dosdude1, nor anyone else is responsible for potential damage to your suppported or unsupported device when using the patcher.

 

[Vyzantion]

Unfortunately the patcher was not and most likely will not be developed for Hackintoshes, it was developed for Macintoshes. You are free to use the patcher at your own risk on any device you chose but the functionality of said patcher cannot be guaranteed on unsupported devices and should be used with caution even on supported devices. Neither me, nor dosdude1, nor anyone else is responsible for potential damage to your suppported or unsupported device when using the patcher.

Of course we all used it at our own risk. All software is so. But yet I was amazed that it actually worked. I have stoped following this thread for about a month ago, but I discover things have gone really well. I shall probably have to read the whole thread to see how it works. Mojave on Nvidia GeForce 6200, a 2005 GPU is really something.
Is there a way to make downloading the installer app via App Store on Mojave on later builds? I am asking this mostly for legal reasons. I want to comply to local EU law and be safe.

 

[weckart]

Is there a way to make downloading the installer app via App Store on Mojave on later builds? I am asking this mostly for legal reasons. I want to comply to local EU law and be safe.

You really think Apple is going to allow a hack on its App Store that circumvents its EULA?

Although this Beta is pretty "stable" at the moment... with minor bugs... (well known)

Dunno about that. I just woke my MBP 2015 from sleep with Safari the only. app running. Got a beachball and a random reboot. I think there is plenty more work needed for primetime.

 

[Vyzantion]

You really think Apple is going to allow a hack on its App Store that circumvents its EULA?

Of course not. On a Hackintosh, we edit the system definitions, so that macOS sees the Hackintosh as a certain type of Mac (iMac 10.1, for example). This can be done with some dedicated tools, also with the contribution of the boot loader (Clover). App Store allows Mojave to be downloaded only on a supported Mac (like iMac 13.1). Dosdude1„s patch works in a different way, I see, it adds the unsupported Mac to the list of accepted Macs. But when I tested if I could download the installer via the App Store on the installed Mojave, I could not. Changing system definitions will, most likely, ruin the patch or it is at least dangerous to make. This is why I am asking if the patch can be extended in a way to allow downloading the Mojave installer via the App Store, not the downloading tool. For legal reasons. If the app is downloaded from the App Store using an Apple ID, it is considered legal in here (although is barely legal, I admit).

 

[pkouame]

Of course not. On a Hackintosh, we edit the system definitions, so that macOS sees the Hackintosh as a certain type of Mac (iMac 10.1, for example). This can be done with some dedicated tools, also with the contribution of the boot loader (Clover). App Store allows Mojave to be downloaded only on a supported Mac (like iMac 13.1). Dosdude1„s patch works in a different way, I see, it adds the unsupported Mac to the list of accepted Macs. But when I tested if I could download the installer via the App Store on the installed Mojave, I could not. Changing system definitions will, most likely, ruin the patch or it is at least dangerous to make. This is why I am asking if the patch can be extended in a way to allow downloading the Mojave installer via the App Store, not the downloading tool. For legal reasons. If the app is downloaded from the App Store using an Apple ID, it is considered legal in here (although is barely legal, I admit).

Some of us are already downloading new beta images via system update (mas) within Mojave betas. Currently a few ways to do so:
- manually enroll for the seed -> kicks off a system update
- download a new beta access utility every time -> kicks off a system update
- use a third party seed catalog switcher/enroller -> kicks off a system update

The Mojave patcher already includes a software update fix that enables this. As the "legality" or "bare-legality" of it all - I don't know...Not a lawyer...

 

[Vyzantion]

Some of us are already downloading new beta images via system update (mas) within Mojave betas. Currently a few ways to do so:
- manually enroll for the seed -> kicks off a system update
- download a new beta access utility every time -> kicks off a system update
- use a third party seed catalog switcher/enroller -> kicks off a system update

The Mojave patcher already includes a software update fix that enables this. As the "legality" or "bare-legality" of it all - I don't know...Not a lawyer...

Are you using a Hackintosh or a Mac? Did you installed the Beta Acces utility? On High Sierra beta this function was build in, in Mojave beta I suppose is the same.

 

[arqueox]

To those who have used dosdude1's Mojave Patcher on their Mac with any IntelHD3000 stock VRAM 384/512 MB
and want to try the VRAM increasing without using my previous Terminal commands:

I attached all the possible already binary patched combinations of VRAM choices 1024/1536/2048 MB into a zipped folder, it also include an entire backup of the IntelHD3000, so just simply replace only the 2 kexts in their related VRAM folder installing into your Mojave /S/L/E/, use your preferred method to install, after done rebuild kextcache, reboot. That's all.

Awesome. Thnx for your effort

 

[pkouame]

Are you using a Hackintosh or a Mac? Did you installed the Beta Acces utility? On High Sierra beta this function was build in, in Mojave beta I suppose is the same.

An "unsupported" mac. Did you try installing the latest beta utility on your hack? No idea about hacks but it would have to "spoof" not only a model id but a machine id and some cpu features to pass installation checks etc. The software update fix (distributed via dude's patcher) serves that function for us.

 

[ctaylora1231]

Does anyone have Continuity Camera working on the latest beta? Not sure if it’s a beta issue or an unsupported system issue. I already used the Continuity Activation Tool to active handoff features on my 2011 Mac Mini

 

[arqueox]

You really think Apple is going to allow a hack on its App Store that circumvents its EULA?

Dunno about that. I just woke my MBP 2015 from sleep with Safari the only. app running. Got a beachball and a random reboot. I think there is plenty more work needed for primetime.

Mine is working great. All the apps are running well, including Adobe illustrator and Photoshop...
No random reboots. Camera working great, you name it.but if you only have one app running, probably there is a problem with your installation... This last beta is pretty "stable" for a beta.

 

[Vyzantion]

An "unsupported" mac. Did you try installing the latest beta utility on your hack? No idea about hacks but it would have to "spoof" not only a model id but a machine id and some cpu features to pass installation checks etc. The software update fix (distributed via dude's patcher) serves that function for us.

On Hacks, we can not do in place updates on beta builds (only after RTM). We need to manually download the new beta build from App Store. On the High Sierra, I could change system definition via Multibeast, the dedicated multi purpose tool pack from Tonymacx86, that ran on top of the Clover boot loader. Dosdude1„s patch works differently, it seems, then this.If I change system definitions via Multibeast, on reboot the patches shall crash and Mojave would need to be reinstalled from scratch, I guess, since they work by adding the old Mac type as legit. Clover picks an appropriate system definition from components, although later on Multibeast can change it. if that choice made by Clover meets the guess of Dosdude1„s patcher, things go well. If not, the OS shall crash. I need a reboot to get changed system definitions to work and this is why I can not use it on this composite method of Hackintoshing I have just discovered (partialy Clover+FakeSMC, partially Dosdude1). This is why I think acces to download full builds via the App Store are required.

 

[0403979]

On Hacks, we can not do in place updates on beta builds (only after RTM). We need to manually download the new beta build from App Store. On the High Sierra, I could change system definition via Multibeast, the dedicated multi purpose tool pack from Tonymacx86, that ran on top of the Clover boot loader. Dosdude1„s patch works differently, it seems, then this.If I change system definitions via Multibeast, on reboot the patches shall crash and Mojave would need to be reinstalled from scratch, I guess, since they work by adding the old Mac type as legit. Clover picks an appropriate system definition from components, although later on Multibeast can change it. if that choice made by Clover meets the guess of Dosdude1„s patcher, things go well. If not, the OS shall crash. I need a reboot to get changed system definitions to work and this is why I can not use it on this composite method of Hackintoshing I have just discovered (partialy Clover+FakeSMC, partially Dosdude1). This is why I think acces to download full builds via the App Store are required.

You can no longer download any macOS installer from the App Store on a device running macOS Mojave.

 

[ASentientBot]

Of course we all used it at our own risk. All software is so. But yet I was amazed that it actually worked. I have stoped following this thread for about a month ago, but I discover things have gone really well. I shall probably have to read the whole thread to see how it works. Mojave on Nvidia GeForce 6200, a 2005 GPU is really something.
Is there a way to make downloading the installer app via App Store on Mojave on later builds? I am asking this mostly for legal reasons. I want to comply to local EU law and be safe.

I don't know why people aren't being helpful. If we help Hackintosh users, then we will get help from them as well and both communities will benefit. There's no need for this slight hostility towards Hackintosh that a lot of people on this forum seem to have.

The Mojave App Store doesn't have an option to download macOS installers. You can use the option Tools --> Download macOS Mojave in @dosdude1's patcher. Alternately, you can use a script like this one or follow my instructions to manually find the download links from the software catalog.

Hope that helps!

 

[0403979]

I don't know why people aren't being helpful. If we help Hackintosh users, then we will get help from them as well and both communities will benefit.

The Mojave App Store doesn't have an option to download macOS installers. You can use the option Tools --> Download macOS Mojave in @dosdude1's patcher. Alternately, you can use a script like this one or follow my instructions to manually find the download links from the software catalog.

Hope that helps!

I was trying but you tried better...

 

[ASentientBot]

I was trying but you tried better...

Sorry, I guess I interpreted your posts in the wrong light. Previously when people ask questions about Hackintosh, forum members have been kind of dismissive. I shouldn't've assumed you were doing the same.

 

[0403979]

Sorry, I guess I interpreted your posts in the wrong light. Previously when people ask questions about Hackintosh, forum members have been kind of dismissive. I shouldn't've assumed you were doing the same.

I actually have done the same and I regret it. Do you know of any scripts to download the install from macOS itself? I found one but it’s currently working and it saves the app in a disc image which is not really what I want.

 

[nekton1]

Dream on.
There are far far too many bugs still to fix before that.
Printing is just one example.
There will likely be another beta on Monday but final is still 4 to 6 weeks away.

Maybe the GM will be out Monday

[doublepost=1534108751][/doublepost]There is a good reason for creating a bootable USB. If it'll boot from a USB installer and basic functions like disk utility, terminal etc., work we can be fairly sure that basic setup with Mac firmware, RAM, hardware, etc., is OK.
I'd place a bet that the OWC Mercury SSDs have the drive firmware problem you posted a link to.
Webgal, check whether your SSDs are listed at OWC as affected by the bug. If they are, the SSD drive bug fix is here:
https://eshop.macsales.com/tech_center/OWC/SSD/Mac_USB_disc_bootable


Once booted from a USB installer, if

I ask because you reported "Bad disc!" If so, your HDD may need to be repaired. You can try running diskutil repair on that drive from Sierra (since you are booted back into Sierra with SSD). A bad hard drive will (of course) prevent an install.

Bad hardware notwithstanding, there is no reason you shouldn't be able to install HS on your system straight from Apple.

Why did you create a bootable HS stick? After the HS download, you should have just invoked the install HS app on your hard disk. Or maybe you did...I can't tell.

Did you scan the links I sent about your OWC SSD and 5,1 bootroms? Here's another OWC page about firmware updates for their Mercury SSDs : https://eshop.macsales.com/tech_center/OWC/SSD. You should really check that your third-party SSD is compatible with your system before proceeding. Else you're back to KPs again, especially if you APFS the thing.

Last thing, if you haven't already, try running a full diagnostic on your machine

Not much more to recommend remotely. Again, you'll have to get HS up and running before considering Mojave.

[doublepost=1534109243][/doublepost]thewebgal
Go to the OWC site and see if your OWC SSDs are among those listed as having the firmware bug preventing OS installation.
If they are download the USB firmware updater and update the firmware in the SSDs.

no, no such text. All I got was a circle with a bar through it.

 

[pkouame]

On Hacks, we can not do in place updates on beta builds (only after RTM). We need to manually download the new beta build from App Store. On the High Sierra, I could change system definition via Multibeast, the dedicated multi purpose tool pack from Tonymacx86, that ran on top of the Clover boot loader. Dosdude1„s patch works differently, it seems, then this.If I change system definitions via Multibeast, on reboot the patches shall crash and Mojave would need to be reinstalled from scratch, I guess, since they work by adding the old Mac type as legit. Clover picks an appropriate system definition from components, although later on Multibeast can change it. if that choice made by Clover meets the guess of Dosdude1„s patcher, things go well. If not, the OS shall crash. I need a reboot to get changed system definitions to work and this is why I can not use it on this composite method of Hackintoshing I have just discovered (partialy Clover+FakeSMC, partially Dosdude1). This is why I think acces to download full builds via the App Store are required.

Interesting. By the way, I think hack <-> unmac exchanges are valuable for both our communities. In fact a lot of what we're doing here was inspired by those famous hack forums/boards. I also have a selfish reason: hacks are becoming a real option for me as Apple stumbles badly with their new machines and I don't believe in their mac pro promises any more..

But I'm confused, so some more questions:
- Have you tried a normal system update (from preferences - that's where it's moved to in Mojave)? If so, what happens?
- What is your hack identified as now? I mean model, machine id, etc.? Can you also print out the output from the following:

- sysctl -a | grep machdep.cpu
- system_profiler SPHardwareDataType
- ioreg -l | awk -F\" '/board-id/ { print $4 }'
​

[doublepost=1534119124][/doublepost]

Dream on.
There are far far too many bugs still to fix before that.
Printing is just one example.
There will likely be another beta on Monday but final is still 4 to 6 weeks away.

[doublepost=1534108751][/doublepost]There is a good reason for creating a bootable USB. If it'll boot from a USB installer and basic functions like disk utility, terminal etc., work we can be fairly sure that basic setup with Mac firmware, RAM, hardware, etc., is OK.
I'd place a bet that the OWC Mercury SSDs have the drive firmware problem you posted a link to.
Webgal, check whether your SSDs are listed at OWC as affected by the bug. If they are, the SSD drive bug fix is here:
https://eshop.macsales.com/tech_center/OWC/SSD/Mac_USB_disc_bootable


Once booted from a USB installer, if

[doublepost=1534109243][/doublepost]thewebgal
Go to the OWC site and see if your OWC SSDs are among those listed as having the firmware bug preventing OS installation.
If they are download the USB firmware updater and update the firmware in the SSDs.

I think so to. Simply because I got bitten by OWC SSD driver issues...so speaking from painful experience.

 

[thewebgal]

I have known for 2 years that my machine SHOULD be able to run High Sierra - yet it has crashed and burned repeatedly when I tried. I tried a direct install, I tried thumb drive copies - NOTHING worked without Kernel panics or worse. But with tips from OTHERS, I finally managed to get a Firmware update yesterday that had been one barrier.

Today I booted to Terminal and turned SIP back on csrutil enable. Rebooted and confirmed it was now ON.
Booted into Sierra and created a bootable High Sierra thumb drive using the Apple commands via Terminal.
Powered down and pulled the OWC SSD, and installed a Seagate 1TB SSD in its place.
Booted from the thumb drive, formatted the Seagate SSD as APFS.
Booted from the thumbdrive and proceeded with a bare install.
Afterwards, I ran Migration Assistant and loaded all my settings and software.
Turns out I had another conflict with a Silican Image eSATA card (also from OWC a few years back).
It runs an external case of 4 drives (PROBOX), so I pulled the card, plugged the case into a USB port (slower)
rebooted again, and all seems to be ok now.
I pulled my old Sierra Time machine drive and stick in a blank 4TB drive and started a few timeMachine run ...

I'll let this go for a few weeks at least before I try anything with Mojave!

I ask because you reported "Bad disc!" If so, your HDD may need to be repaired. You can try running diskutil repair on that drive from Sierra (since you are booted back into Sierra with SSD). A bad hard drive will (of course) prevent an install.

Bad hardware notwithstanding, there is no reason you shouldn't be able to install HS on your system straight from Apple.

Why did you create a bootable HS stick? After the HS download, you should have just invoked the install HS app on your hard disk. Or maybe you did...I can't tell.

Did you scan the links I sent about your OWC SSD and 5,1 bootroms? Here's another OWC page about firmware updates for their Mercury SSDs : https://eshop.macsales.com/tech_center/OWC/SSD. You should really check that your third-party SSD is compatible with your system before proceeding. Else you're back to KPs again, especially if you APFS the thing.

Last thing, if you haven't already, try running a full diagnostic on your machine

Not much more to recommend remotely. Again, you'll have to get HS up and running before considering Mojave.

 

[nekton1]

Congratulations.

Next, I'd check/update the OWC firmware bug. But at least you are now on High Sierra. Frankly, unless you are desperate to see Mojave, I'd wait until the final release b/c it is hot mess right now with many issues, not least of which is buggy printing.
Either wait if the MP5,1 is your only machine, or get the firmware bug in the OWC SSD fixed and install Mojave on that for play time.
PS. If you do a clean install of Mojave on another SSD (bug-fixed OWC SSD) and then pull the user profile from a High Sierra install on another SSD using Migration Assistant, I have seen the migrated profile on Mojave have weird subtle bugs, so be warned that Mojave MA might not be ready for prime time.

I have known for 2 years that my machine SHOULD be able to run High Sierra - yet it has crashed and burned repeatedly when I tried. I tried a direct install, I tried thumb drive copies - NOTHING worked without Kernel panics or worse. But with tips from OTHERS, I finally managed to get a Firmware update yesterday that had been one barrier.

Today I booted to Terminal and turned SIP back on csrutil enable. Rebooted and confirmed it was now ON.
Booted into Sierra and created a bootable High Sierra thumb drive using the Apple commands via Terminal.
Powered down and pulled the OWC SSD, and installed a Seagate 1TB SSD in its place.
Booted from the thumb drive, formatted the Seagate SSD as APFS.
Booted from the thumbdrive and proceeded with a bare install.
Afterwards, I ran Migration Assistant and loaded all my settings and software.
Turns out I had another conflict with a Silican Image eSATA card (also from OWC a few years back).
It runs an external case of 4 drives (PROBOX), so I pulled the card, plugged the case into a USB port (slower)
rebooted again, and all seems to be ok now.
I pulled my old Sierra Time machine drive and stick in a blank 4TB drive and started a few timeMachine run ...

I'll let this go for a few weeks at least before I try anything with Mojave!

 

[pkouame]

I have known for 2 years that my machine SHOULD be able to run High Sierra - yet it has crashed and burned repeatedly when I tried. I tried a direct install, I tried thumb drive copies - NOTHING worked without Kernel panics or worse. But with tips from OTHERS, I finally managed to get a Firmware update yesterday that had been one barrier.

Today I booted to Terminal and turned SIP back on csrutil enable. Rebooted and confirmed it was now ON.
Booted into Sierra and created a bootable High Sierra thumb drive using the Apple commands via Terminal.
Powered down and pulled the OWC SSD, and installed a Seagate 1TB SSD in its place.
Booted from the thumb drive, formatted the Seagate SSD as APFS.
Booted from the thumbdrive and proceeded with a bare install.
Afterwards, I ran Migration Assistant and loaded all my settings and software.
Turns out I had another conflict with a Silican Image eSATA card (also from OWC a few years back).
It runs an external case of 4 drives (PROBOX), so I pulled the card, plugged the case into a USB port (slower)
rebooted again, and all seems to be ok now.
I pulled my old Sierra Time machine drive and stick in a blank 4TB drive and started a few timeMachine run ...

I'll let this go for a few weeks at least before I try anything with Mojave!

So you pulled out your OWC SSD and installed HS on a supported SSD. You're on your way to Mojave. Perfect.
[doublepost=1534123857][/doublepost]

I don't know why people aren't being helpful. If we help Hackintosh users, then we will get help from them as well and both communities will benefit. There's no need for this slight hostility towards Hackintosh that a lot of people on this forum seem to have.

The Mojave App Store doesn't have an option to download macOS installers. You can use the option Tools --> Download macOS Mojave in @dosdude1's patcher. Alternately, you can use a script like this one or follow my instructions to manually find the download links from the software catalog.

Hope that helps!

@ASentientBot love those instructions. Have served me well. And I recognize foxlet's old code...brings me back.
[doublepost=1534123887][/doublepost]

I actually have done the same and I regret it. Do you know of any scripts to download the install from macOS itself? I found one but it’s currently working and it saves the app in a disc image which is not really what I want.

Julian - what are you trying to do?

 

[TimothyR734]

the newest version of the SWU Switcher 1.0.4

 

[thegurgz]

Don’t know if this relates to the forum, but what does Safari Technology Preview have that Safari doesn’t? Noticed it was a discussion in this forum earlier, tried it, but didn’t find anything worthwhile.

 

[pkouame]

Don’t know if this relates to the forum, but what does Safari Technology Preview have that Safari doesn’t? Noticed it was a discussion in this forum earlier, tried it, but didn’t find anything worthwhile.

I find it most useful for web app full stack development. Best place for insights is
here https://webkit.org/blog/8384/release-notes-for-safari-technology-preview-62/