macOS 10.14 Mojave on Unsupported Macs Thread

[thewebgal]

Any thoughts on bypassing High Sierra and going directly from Sierra to Mojave?

 

[Jonathan50]

You need to use the patcher to create an installer USB drive, boot from that, and install onto your SSD. It works exactly like High Sierra Patcher did.

Thank you @dosdude1 for your hard work. Can I try your patcher on the Mac Pro 3,1 with non-EFI GT710 Kepler and 8800GT Tesla video cards? Does it affect or edit the machine's firmware in any way?

 

[dosdude1]

Thank you @dosdude1 for your hard work. Can I try your patcher on the Mac Pro 3,1 with non-EFI GT710 Kepler and 8800GT Tesla video cards? Does it affect or edit the machine's firmware in any way?

It won't run on the MacPro3,1 at this time. But no, it does not alter system firmware.

 

[jackluke]

Apple iMac "Core i5" 2.7 27-Inch (Mid-2011) iMac 12,2

Installed Mojave b2 using USB Dosdude1's patcher
Rebooted to USB Patcher, Ran patches iMac 12,2

Rebooted:
Boots to Gray Apple Logo, light gray screen, progress bar gets about 2/3's of the way through and the machine reboots. It then reboots a second time with a double chime. It's like a full chime with a half chime right afterwards.

Will try again later with verbose output.

This is from memory (last night).

I am guessing its an issue with the AMD Video Card. I have not tried anything outside the patcher. Tried to run it like it is for a good test.

I would like to thank dosdude1 again for his hard work and dedication (and anyone else associated with this project). I will be sending a donation to dosdude1 after my next eBay sale. I used to write donation ware about ten years ago and will be paying it forward. Your HS patches are solid.

After a Mojave install the first “mach reboot” is normal routine because it rebuilds the prelinkedkernel file and kextcache id.

I found a way to cheat the macos system to prevent the prelinkedkernel rebuilding since I needed only a prelinkedkernel custom recovery for a test on a machine, and it’s weird but just to rename in S/L/Kernels the kernel file in kernel2 or something else, in this way macos boot will be forced to use the prelinkedkernel you copy on S/L/Prelinkedkernels with no rebuilding of kextcache ID, to me was useful for some experiments.

 

[Jonathan50]

It won't run on the MacPro3,1 at this time. But no, it does not alter system firmware.

Alright then, how about on a friend's 2011 MacMini with i5 processor and HD3000 graphics only? That is, if I can convince her it's, ahem, harmless...

 

[dosdude1]

Alright then, how about on a friend's 2011 MacMini with i5 processor and HD3000 graphics only? That is, if I can convince her it's, ahem, harmless...

Yeah, it should work just fine on there.

 

[mat77_mac]

I'm currently working on C2D machines myself (got about 20 of them). So far I haven't made much progress.
[doublepost=1529967342][/doublepost]Just finished the preliminary release of macOS Mojave Patcher. Keep in mind it is in an early state at this point, and may have some issues. Using the tool, you can download a copy of Mojave from Apple, and create an installer that will boot and install on an unsupported machine. The patched installer will NOT automatically convert SSDs to APFS. The post-install tool does contain some of the preliminary patches that have been tested thus far, but will still have issues at this point more than likely. ONLY machines with Intel Core i series processors are supported at this time. Download available here.

I have iMac mid 2011 only questione work all sistem or i have problem with video card???

 

[dosdude1]

I have iMac mid 2011 only questione work all sistem or i have problem with video card???

If you have an AMD video card, it will not work properly (most if not all 2011 iMacs do).

 

[bosozoku]

If you have an AMD video card, it will not work properly (most if not all 2011 iMacs do).

Thank you for your hard work!
Could you please add a complete tutorial how-to install mojave with your patcher? Much thanks!
I have 13" 2011 mbp i7 with second blank ssd apfs formatted installed in optibay, want to run Mojave from that drive!

 

[dosdude1]

Thank you for your hard work!
Could you please add a complete tutorial how-to install mojave with your patcher? Much thanks!
I have 13" 2011 mbp i7 with second blank ssd apfs formatted installed in optibay, want to run Mojave from that drive!

Just follow the process of using High Sierra Patcher, but of course using Mojave with Mojave Patcher. The High Sierra Patcher guide can be found here.

 

[mikejrslac]

If you have an AMD video card, it will not work properly (most if not all 2011 iMacs do).

Could you comment on what video issues to expect with a 2011 iMac ? thanks

 

[PrincipeAzzurro]

Hi guys and hello dosdude1,

three years ago my MacBook Pro 17'' 8.3 late 2011 (best machine ever) had its motherboard repaired for discrete graphics card troubles - the infamous AMD Radeon HD 6770M - and worked fine until about a month ago. Since then - basically with the last High Sierra update to 10.13.4 - the kernel panics and white startup screens are back. Ultimately they have induced me to disable the discrete card and run the machine without it (if anybody is interested, this https://apple.stackexchange.com/questions/267581/gpu-problem-boot-hangs-on-grey-screen is how I managed to do it, thanks to the very elegant solution offered by LangLangC on stackexchange). All is fine without the AMD card, my machine has much longer battery autonomy and doesn't heat up anymore as it used to before. But there are also several disadvantages, most of all not being able to use external monitors anymore due to the insufficient capacity of the integrated graphics card via Thunderbolt 1.

Therefore… my wet dream now is that Mojave… might somehow "magically" get rid of that hardware problem altogether and give me back my graphics card. With new kexts perhaps, or even a new architecture altogether, I don't know...

This would be the only reason for me to want to try out Mojave (although I haven't figured out how to get it installed just yet).

What is your take on this? Does what I say make sense? Or should I forget about it and let it go until Apple rolls out new MacBook Pros with a decent (non-butterfly) keyboard (I gave back a 15'' fully blown MPB earlier this year because i hated, hated hated the keyboard)?

Thanks and greets from Berlin - keep up the good work here and elsewhere…

 

[Starplayr]

After a Mojave install the first “mach reboot” is normal routine because it rebuilds the prelinkedkernel file and kextcache id.

I found a way to cheat the macos system to prevent the prelinkedkernel rebuilding since I needed only a prelinkedkernel custom recovery for a test on a machine, and it’s weird but just to rename in S/L/Kernels the kernel file in kernel2 or something else, in this way macos boot will be forced to use the prelinkedkernel you copy on S/L/Prelinkedkernels with no rebuilding of kextcache ID, to me was useful for some experiments.

That is interesting, and I like the logic.

 

[0403979]

Hi guys and hello dosdude1,

three years ago my MacBook Pro 17'' 8.3 late 2011 (best machine ever) had its motherboard repaired for discrete graphics card troubles - the infamous AMD Radeon HD 6770M - and worked fine until about a month ago. Since then - basically with the last High Sierra update to 10.13.4 - the kernel panics and white startup screens are back. Ultimately they have induced me to disable the discrete card and run the machine without it (if anybody is interested, this https://apple.stackexchange.com/questions/267581/gpu-problem-boot-hangs-on-grey-screen is how I managed to do it, thanks to the very elegant solution offered by LangLangC on stackexchange). All is fine without the AMD card, my machine has much longer battery autonomy and doesn't heat up anymore as it used to before. But there are also several disadvantages, most of all not being able to use external monitors anymore due to the insufficient capacity of the integrated graphics card via Thunderbolt 1.

Therefore… my wet dream now is that Mojave… might somehow "magically" get rid of that hardware problem altogether and give me back my graphics card. With new kexts perhaps, or even a new architecture altogether, I don't know...

This would be the only reason for me to want to try out Mojave (although I haven't figured out how to get it installed just yet).

What is your take on this? Does what I say make sense? Or should I forget about it and let it go until Apple rolls out new MacBook Pros with a decent (non-butterfly) keyboard (I gave back a 15'' fully blown MPB earlier this year because i hated, hated hated the keyboard)?

Thanks and greets from Berlin - keep up the good work here and elsewhere…

A software update will never fix a hardware issue. If the issue is truly with the hardware then you need a motherboard replacement.

Apple won’t release a MacBook Pro without a butterfly keyboard. They have made the transition and aren’t going back. If you want a good 15-inch without a butterfly keyboard then pick a 2015 model from Apple’s website (non refurbished): https://www.apple.com/shop/buy-mac/macbook-pro?product=MJLQ2LL/A&step=config#

 

[bosozoku]

Just follow the process of using High Sierra Patcher, but of course using Mojave with Mojave Patcher. The High Sierra Patcher guide can be found here.

Thank you, it's all clear now!
As far as I understand, it will download the latest version of macOS Mojave available?

 

[dosdude1]

Hi guys and hello dosdude1,

three years ago my MacBook Pro 17'' 8.3 late 2011 (best machine ever) had its motherboard repaired for discrete graphics card troubles - the infamous AMD Radeon HD 6770M - and worked fine until about a month ago. Since then - basically with the last High Sierra update to 10.13.4 - the kernel panics and white startup screens are back. Ultimately they have induced me to disable the discrete card and run the machine without it (if anybody is interested, this https://apple.stackexchange.com/questions/267581/gpu-problem-boot-hangs-on-grey-screen is how I managed to do it, thanks to the very elegant solution offered by LangLangC on stackexchange). All is fine without the AMD card, my machine has much longer battery autonomy and doesn't heat up anymore as it used to before. But there are also several disadvantages, most of all not being able to use external monitors anymore due to the insufficient capacity of the integrated graphics card via Thunderbolt 1.

Therefore… my wet dream now is that Mojave… might somehow "magically" get rid of that hardware problem altogether and give me back my graphics card. With new kexts perhaps, or even a new architecture altogether, I don't know...

This would be the only reason for me to want to try out Mojave (although I haven't figured out how to get it installed just yet).

What is your take on this? Does what I say make sense? Or should I forget about it and let it go until Apple rolls out new MacBook Pros with a decent (non-butterfly) keyboard (I gave back a 15'' fully blown MPB earlier this year because i hated, hated hated the keyboard)?

Thanks and greets from Berlin - keep up the good work here and elsewhere…

Those machines have a defective GPU. No software will fix that, other than disabling the dedicated GPU using my method found here.
[doublepost=1530042187][/doublepost]

Thank you, it's all clear now!
As far as I understand, it will download the latest version of macOS Mojave available?

Yes, that's right.

 

[Jonathan50]

At the risk of sounding funny, may I ask why the patcher downloaded 10.13.5 High Sierra in my case?

 

[smokesletsgo]

Those machines have a defective GPU. No software will fix that, other than disabling the dedicated GPU using my method found here.
[doublepost=1530042187][/doublepost]
Yes, that's right.

Can the tool be modified to download Public Beta instead of Developer? Asking because I think PB has the News app, and latest DP2 doesn't for some reason.

 

[dosdude1]

Can the tool be modified to download Public Beta instead of Developer? Asking because I think PB has the News app, and latest DP2 doesn't for some reason.

Yeah, already made that change.
[doublepost=1530044731][/doublepost]

At the risk of sounding funny, may I ask why the patcher downloaded 10.13.5 High Sierra in my case?

Apple changed the CatalogURL with the release of Public Beta for some reason. This has been fixed.

 

[PrincipeAzzurro]

Those machines have a defective GPU. No software will fix that, other than disabling the dedicated GPU using my method found here.

Well - kudos. This is far more elegant than the solution I had found before. Thank you very much indeed mate, if we ever meet a round of the best beer in the place is on me.

 

[DaniloGeekDude]

At the risk of sounding funny, may I ask why the patcher downloaded 10.13.5 High Sierra in my case?

Are you sure you downloaded the Mojave patcher (which includes the patcher and then the option to download the beta 10.14 installer as well?)

http://dosdude1.com/mojave/

P.S. sorry just noticed dosdude1's reply after I posted the above.

So does the link contain the first Public Beta now?

 

[Jonathan50]

Are you sure you downloaded the Mojave patcher (which includes the patcher and then the option to download the beta 10.14 installer as well?)

http://dosdude1.com/mojave/

P.S. sorry just noticed dosdude1's reply after I posted the above.

So does the link contain the first Public Beta now?

Starting over now. This patcher has a slightly different byte count than the previous one, so I may well have the updated one. Will report back.

 

[Neoprada]

Are you sure you downloaded the Mojave patcher (which includes the patcher and then the option to download the beta 10.14 installer as well?)

http://dosdude1.com/mojave/

P.S. sorry just noticed dosdude1's reply after I posted the above.

So does the link contain the first Public Beta now?

I have the same issue, I tried 3 times just to be sure and each gave me High Sierra. After seeing Dosdude1 message I am trying again but my wonder is should I have reinstalled the patcher over or just hope it downloads Mojave this time?

 

[avisavis]

Just follow the process of using High Sierra Patcher, but of course using Mojave with Mojave Patcher. The High Sierra Patcher guide can be found here.

I used the Mojave Patcher and selected already downloaded(not with this tool) Mojave Developer Preview1 and proceeded.
At the end it showed "..../macOS Mojave Patcher.app/Contents/Resources/dp1/OSInstall.mpkg: No such file or directory"

Could you please let me know if I missed anything or did something wrong...

Used this on Macbook pro late 2011 13"

 

[visberry]

Just follow the process of using High Sierra Patcher, but of course using Mojave with Mojave Patcher. The High Sierra Patcher guide can be found here.

what are the requirements and supported models on the patcher?