macOS 10.14 Mojave on Unsupported Macs Thread

[Vyzantion]

No, it's now part of the standard Clover package.

BTW, for the record, I've never had a problem APFS, but I now use SSDs exclusively.

That would be great news, since I use Mojave on APFS.
By the way, would the new build of Multibeast contain a compatible Clover with Mojave legacy? In order to create the installation pen drive, I needed to use the Clover from Multibeast, then update it to the latest official version, to able to boot the installer on the legacy system. Anyways, nice to see in here a familiar face.

 

[pkouame]

Tonymacx86 builds of Clover for High Sierra, unlike official ones, include the copied apfs.efi . Or they copy it automatically.
[doublepost=1534282397][/doublepost]By the way, I have discovered this link on a post on Insanelymac, a script to make Mojave installed on Hackintoshes and unsupported Macs to download updates, especially on HFS+. I have allready updated, I can not test it for myself. If you, some of you can test it. https://github.com/Gengik84/MacOS_Updater

Good news.
Yes - that's a good link - based on PikerAlpha's genius no less...

 

[Vyzantion]

Good news.
Yes - that's a good link - based on PikerAlpha's genius no less...

Just a script to paste into Terminal and updates were suppose to go.

 

[saudor]

APFS, for Hackintoshes, has an issue. Support from Clover it is still in infancy. We need to copy apfs.efi manually into Clover in order to make it boot. Of course, a good way to make this would be for the Clover developers to add build-in support for APFS, how they did with HFS+, years ago, but that will take time. I have installed High Sierra on APFS instead of HFS+ a little while ago, as a preparation for Mojave. It went well for a time then, suddenly, at one boot, FakeSMC failed to configure the DSMOS and boot failed. DSMOS is a kext, placed in macOS and iOS, short for Do Not Steal Mac OS, meant to block the boot of the OS on unsupported hardware (in case of macOS, Hackintoshes and unsupported Macs). FakeSMC, configuring the SMC, on boot, configures this kext and allows the boot. On verbose boot, DSMOS first says „Waiting for DSMOS”, then a few lines, some unrelated to it, appear, then „DSMOS has arrived”. After the first message, if FakeSMC fails, the boot is stoped. Sometimes, after the second message the boot stops. DSMOS after the kernel finished booting and before the GUI of the OS. If APFS affects FakeSMC and DSMOS, this shows there are clear, structural differences between HFS+ and APFS in how macOS works and how it relates to hardware.

there’s another patch that actually pulls the apfs from the boot volume. I use that one and it works fine without copying it to the EFI partition

 

[Luckygreek]

Oh I swear by it on my new machines. Its merits are not in question, just didn't feel like tempting too much change on the old clunkers. But agreed, APFS works better.
[doublepost=1534281660][/doublepost]

That's where I got stuck, old clunkers (G5's), decided it was time to retire as Snow Leopard was end of the road without some serious hacks & I'd been down that road before. Served me well for a number of years, but retirement was best course of action, at least for me.

 

[TimothyR734]

here is some info it is a 7 component install that includes the update, macOS brain, secure boot, full bundle update, embedded firmware update, firmware update, recovery HD update. If you have a Touch Bar you will need the bridge os brain and bridge os customer info from thread Developer Beta 5..Is it out yet

 

[videotape74]

I have a mid-2009 MBP (5,4). Where can I find the APFS patcher needed to use the APFS file system on my internal SSD?

 

[thegurgz]

Tonymacx86 builds of Clover for High Sierra, unlike official ones, include the copied apfs.efi . Or they copy it automatically.
[doublepost=1534282397][/doublepost]By the way, I have discovered this link on a post on Insanelymac, a script to make Mojave installed on Hackintoshes and unsupported Macs to download updates, especially on HFS+. I have allready updated, I can not test it for myself. If you, some of you can test it. https://github.com/Gengik84/MacOS_Updater

Will definitely test this tonight!

 

[TimothyR734]

I have a mid-2009 MBP (5,4). Where can I find the APFS patcher needed to use the APFS file system on my internal SSD?

for now dosdude1 has removed it until the new version is completed as for some who have used it it blinked their Macs

 

[videotape74]

for now dosdude1 has removed it until the new version is completed as for some who have used it it blinked their Macs

oh ok, thank you for letting me know.

 

[nekton1]

Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4

The Boot ROM version does not change before and after the patch. As others have said, the patch is pulled at the moment until dosdude1 fixes a rom misidentification bug in some Macs. The old version worked just fine on my MP3,1.

Oh I swear by it on my new machines. Its merits are not in question, just didn't feel like tempting too much change on the old clunkers. But agreed, APFS works better.
[doublepost=1534281660][/doublepost]
Ouch! I thought APFS was a little more mature on hacks. Thanks for the info.
[doublepost=1534281746][/doublepost]
Cool. what is the current version of your boot rom?

 

[BookEmDanno]

Indeed! That's the way system update should work - downloading just the updates instead of the full installer. Congrats. Do you mind sharing your install.log?
[doublepost=1534204993][/doublepost]
Nice.

Sorry, I just saw this post. Do you still need to see the install log? If so, I'll grep the log for entries specific to the date and time my "in-place" update occurred ~ need to do this since the log includes all dates since DP 1 install. Or, if you are looking on something specifc, I will grep that as well.

Unfortunately, my MBAir is @ home, so I will need to do this later.

 

[David403]

From another forum (as posted by Badruzeus)

Major changes for this beta on real cMP (MacPro5,1)s, Update has new firmware 138.0.0.0 bootrom. This update does not require for you to have a Apple-EFI GPU in order for it to upgrade the firmware, of course no boot screen but at least its allowing non-AppleGPUs to be used for upgrading firmware. Also a HUGE update that allows non-Apple GPUs to have full 5.0GT/s PCI-E link speed.

No firmware update for me.

I did the update from system preferences

My BootROM has not changed: it is still MP51.0087.B00. Updated to this when updating from 10.13.5 to 10.13.6

I have one of the non-AppleGPUs recommended by Apple, a Radeon RX 580 with no Boot screen, as expected. I use the 'QuickBoot App' once in the OS. I had tried 'Boot Runner' but with each update of Mojave beta it can't find Mojave from any OS. Of course selecting the startup disc fro System Preferences still works.

 

[pkouame]

Sorry, I just saw this post. Do you still need to see the install log? If so, I'll grep the log for entries specific to the date and time my "in-place" update occurred ~ need to do this since the log includes all dates since DP 1 install. Or, if you are looking on something specifc, I will grep that as well.

Unfortunately, my MBAir is @ home, so I will need to do this later.

No problem. It seems like system update works pretty well under APFS, at this point a very strong indication. Don't worry about the log, but thanks.
[doublepost=1534290567][/doublepost]

Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4

The Boot ROM version does not change before and after the patch. As others have said, the patch is pulled at the moment until dosdude1 fixes a rom misidentification bug in some Macs. The old version worked just fine on my MP3,1.

Thanks. I'll wait for the new version.
[doublepost=1534290712][/doublepost]

there’s another patch that actually pulls the apfs from the boot volume. I use that one and it works fine without copying it to the EFI partition

and @Vyzantion are there hackintosh laptops running core i9s?

 

[nekton1]

Changing the subject, but it has become apparent that Apple over the last year has deprecated booting from APFS RAID, making it difficult in HS and now impossible in Mojave. When I asked an expert why Apple would do this, his (edited for privacy) answer is provided below. What I take from this is a time is coming when what we do here will not be possible any more.

_________________________
It is all about "security".
...they want to lock down the system to prevent any possible root attacks. So the boot process is completely controlled with a locked down set of drivers to load at startup.
They could enable RAID in this scenario, but (it) would take more effort. We even proposed a model that would work, but were shot down. The "Security" team wants a simple process... .
.
.
.
We no longer have root access to the boot device for any reason. Not even to verify a disk, detect disk errors, etc. It is all isolated from even admin access.
___________________________

 

[TimothyR734]

Changing the subject, but it has become apparent that Apple over the last year has deprecated booting from APFS RAID, making it difficult in HS and now impossible in Mojave. When I asked an expert why Apple would do this, his (edited for privacy) answer is provided below. What I take from this is a time is coming when what we do here will not be possible any more.

_________________________
It is all about "security".
...they want to lock down the system to prevent any possible root attacks. So the boot process is completely controlled with a locked down set of drivers to load at startup.
They could enable RAID in this scenario, but (it) would take more effort. We even proposed a model that would work, but were shot down. The "Security" team wants a simple process... .
.
.
.
We no longer have root access to the boot device for any reason. Not even to verify a disk, detect disk errors, etc. It is all isolated from even admin access.
___________________________

that does not sound good but where there is a will there is a way

 

[nekton1]

If you can find a way to get Mojave to install on a boot APFS APPLE RAID or softRAID RAID, let us know. Two ex-Apple disk geniuses I know have said it is impossible now.

that does not sound good but where there is a will there is a way

 

[saudor]

that does not sound good but where there is a will there is a way

Yeah there's gonna be exploits. iOS is supposed to be "locked down" too and there's been jailbreaks for pretty much every version.

 

[Badruzeus]

APFS, for Hackintoshes, has an issue. Support from Clover it is still in infancy. We need to copy apfs.efi manually into Clover in order to make it boot. Of course, a good way to make this would be for the Clover developers to add build-in support for APFS, how they did with HFS+, years ago, but that will take time. I have installed High Sierra on APFS instead of HFS+ a little while ago, as a preparation for Mojave. It went well for a time then, suddenly, at one boot, FakeSMC failed to configure the DSMOS and boot failed. DSMOS is a kext, placed in macOS and iOS, short for Do Not Steal Mac OS, meant to block the boot of the OS on unsupported hardware (in case of macOS, Hackintoshes and unsupported Macs). FakeSMC, configuring the SMC, on boot, configures this kext and allows the boot. On verbose boot, DSMOS first says „Waiting for DSMOS”, then a few lines, some unrelated to it, appear, then „DSMOS has arrived”. After the first message, if FakeSMC fails, the boot is stoped. Sometimes, after the second message the boot stops. DSMOS after the kernel finished booting and before the GUI of the OS. If APFS affects FakeSMC and DSMOS, this shows there are clear, structural differences between HFS+ and APFS in how macOS works and how it relates to hardware.

Obsolete..!!! Talking about proprietary APFS *.efi driver for using with h*ckintosh, we're at Clover have developed our own OpenSource version named "ApfsDriverLoader": based on reverse-engineered Apple's ApfsJumpStart driver since while ago (this is new repo, now with v2.x after project has been moved, thanks to @savvamitr*fanov). NO, I'm not guessing ppl here to use it, so plz don't even try it on your real macs.

Spoiler

You can #ofc build it your self using Xcode for sure, or entire Clover package with EDK2 or UDK2018 including new ApfsDriverLoader (./ebuild.sh --ext-co), or just use it from Releases page.

FakeSMC is OffTopic here, though I never getting issue with HighSierra upto Mojave using Slice's fork v3.5.x. No more comment from me about h*ckintosh, sorry.. since I've told early that I'll never ask for it's support here. But if your choice is teaching @dosdude1 @parrotgeek1 etc. about how Apple-Intel-Arch operate (?), it's up to you (I've to thank to all of them for MLPostFactor Patcher.app that I use on my MB4,1 with 10.8.5). I'm using my non-real mac here with Fermi graphics is just for comparison after Apple dropped lots of unsupported graphics models under Mojave, but interestingly still including NVDAGF*.kext on SLE, that Apple don't even use it on their real macs (on vanilla system for sure, not 'ked by any ~beast #LoL). Sorry if sounds harsh, though I don't think so.

Also sorry @pkouame, for my prev. report with succeeded any Beta Updates under Mojave, my bad.. I just realized that I use supported platform (MBP10,1), so it doesn't make a sense here. Thanks.

 

[nekton1]

I think on a MP5,1 you might need to do it manually by pressing the Power button at start for 15 seconds until the single tone which indicates it is firmware update mode.

No firmware update for me.

I did the update from system preferences

My BootROM has not changed: it is still MP51.0087.B00. Updated to this when updating from 10.13.5 to 10.13.6

I have one of the non-AppleGPUs recommended by Apple, a Radeon RX 580 with no Boot screen, as expected. I use the 'QuickBoot App' once in the OS. I had tried 'Boot Runner' but with each update of Mojave beta it can't find Mojave from any OS. Of course selecting the startup disc fro System Preferences still works.

 

[thegurgz]

By the way, I have discovered this link on a post on Insanelymac, a script to make Mojave installed on Hackintoshes and unsupported Macs to download updates, especially on HFS+. I have allready updated, I can not test it for myself. If you, some of you can test it. https://github.com/Gengik84/MacOS_Updater

Looks like script downloads: “FirmwareUpdate.pkg”
“FullBundleUpdate.pkg” “EmbeddedOSFirmware.pkg” “macOSupd10.14.pkg”
“macOSUpd10.14Patch.pkg” “macOSUpd10.14.RecoveryHDUpdate.pkg”
“macOSBrain.pkg”
“SecureBoot.pkg”

Installing boot file on target volume now.

 

[pkouame]

If you can find a way to get Mojave to install on a boot APFS APPLE RAID or softRAID RAID, let us know. Two ex-Apple disk geniuses I know have said it is impossible now.

Since you changed the subject . My humble opinion...But HS and Mojave support accessing RAID arrays after boot right? Don't you think that's an adequate workaround? RAID technology from inception has always been about performant redundant and reliable access to big data. So you can keep your stripes protecting your data and boot using Apple's most secure file system. Just sayin...

 

[DaniloGeekDude]

No problem. It seems like system update works pretty well under APFS, at this point a very strong indication. Don't worry about the log, but thanks.

That explains while I cannot update my un-supported MBP5,3 via system preferences. Oh well, update via @dosdude1's mojave patcher is not too bad, it just a lengthy process compared to the system preferences update. But, it works!

Thanks for this info!

 

[Luckygreek]

Anyone else getting this dragging a window in the Finder?

2010 iMac ATI 5750

 

[thegurgz]

End result, going to try to reboot to see if it still goes through. Probably would have been quicker to just download the DB from the patcher and write it to a drive… still waiting end result.
[doublepost=1534306187][/doublepost]
Too many corpses being created error on boot. Forgot how to fix, anyone know?

EDIT: after the error, finished boot, yet no menu bar and finder won’t open. Isn’t too many corpses error supposed to prevent booting?