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.
Don't blame Apple - Its not their fault you just bought a 7 year old machine .... be real.
I have an older mac Pro - I read the thread, and maybe once Mojave is beyond early beta versions,
I'll try it on mine - but not just yet!
that's not the point. this macbook is faster than a Windows laptop with a 7200U in it, a cpu released in 2017. there's no reason it couldn't run 10.14.
 
Well, wait and see if the C2D issue(s) can be found and fixed. Currently completely unclear, but folks are at it!
I personally still have hope running Mojave on all our old gear.


Let's hope that Badruzeus will come with a suggestion from the wonderfull world of Hac*intosh like he did for Intel HD Graphics 3000 !!
 
  • Like
Reactions: volodi
that's not the point. this macbook is faster than a Windows laptop with a 7200U in it, a cpu released in 2017. there's no reason it couldn't run 10.14.
Thats not my point - Speed is not the only determining factor.
Apple is not responsible for a 2011 machine running their latest, greatest software when it is in early release Beta form. Wait for the OS code to be a bit more mature, a bit less bleedin' edge before you condemn them.
Have a great weekend!
 
  • Like
Reactions: olad
How do you guys even get the Mojave file on your Mac? I know you can download the file from the Appstore on a supported Mac, but is there another way?
 
First of all Hello All.
Thanks for the tremendous work you do here.
I have a 27" iMac (late 2009) running High Sierra 10.13.6 Beta (17G54a). Until yesterday I was an happy beta tester. Happy until I understood that all is done for my mac lol. I downloaded the Mac OS Mojave patcher, the OS beta, made bootable usb external and began the installation. After a few hours, computer restarted and I got a prohibitory icon. So I restored from fresh Time machine backup I made just before installing. Is there any hope here for my mac to run Mojave?
It remembers me the time when Apple suddenly discarded SCSI and a lot of my users had to trash their Umax Powerlook scanners, not speaking of scientific instruments continuing to work on obsolete systems....
Anyway, a big thanks to all of you here.

For the prohibitory icon you got on computer restart, I suggest you include this argument on your nvram boot arguments:

"nvram boot-args = -no_compat_check" . See if it get you further on your boot process. It did for mine on unsupported macbook air mid 2011.
 
  • Like
Reactions: ASentientBot
Where? It only gives me the option to browse for a file. And in the resources folder I also can't find the file.
Hint:
You might try to have a look at all the wonderful dropdown menu entries in the menu bar... ;-)
[doublepost=1530367224][/doublepost]
For the prohibitory icon you got on computer restart, I suggest you include this argument on your nvram boot arguments:

"nvram boot-args = -no_compat_check" . See if it get you further on your boot process. It did for mine on unsupported macbook air mid 2011.
Generally a good advice, but won't help at the moment for Core2Duo machines like the 2009 iMac.
 
Thanks to @dosdude1's patcher app, I was able to install Mojave Public Beta without big problems!! ThanksView attachment 768397
The 2011 iMacs are still very powerful by today's standards. Definitely hoping that full acceleration can be achieved on the AMD GPU, but that's really the only issue to overcome. :)
that's not the point. this macbook is faster than a Windows laptop with a 7200U in it, a cpu released in 2017. there's no reason it couldn't run 10.14.
The CPUs in quad-core 2011 iMacs and MacBook Pros outperform plenty of the supported Macs' CPUs, including the brand new $1,200 MacBook.

It's absurd that Apple no longer supports them in Mojave, but I suppose the threat of such good value-for-money used Macs must be neutralized. ;)
 
It's absurd that Apple no longer supports them in Mojave, but I suppose the threat of such good value-for-money used Macs must be neutralized. ;)
Staying without Mojave isnt't that bad, consequences are worse. Most developers will wipe open GL/CL code from apps, making it metal-only – that's a matter of time. I hope we'll have at least 2 years without limitations.
 
Hi Guys, Thanks for the patch. I now installed it on my MBP early 2011. A quick question, will we be able to update to latest beta updates when they get released with no problems? If we can, do we need to apply the patch again?

Thanks in advance.
 
I do this like this?
Captura de Tela 2018-06-30 às 14.25.21.png


When I'll boot installer usb, they force me to restart because of error, showing me a log error... My macbook is a air mid 2011
 
Last edited:
I do this like this? View attachment 768431

When I'll boot installer usb, they force me to restart because of error, showing me a log error... My macbook is a air mid 2011
Not sure how you edited to this result.
Normally, just boot a working system.
Open terminal, issue command sudo nvram boot-args="-no_compat_check"
And make sure that SIP is disabled for the time being. You might have to boot into a working recovery to disable it there with terminal command csrutil disable
 
  • Like
Reactions: ASentientBot
I do this like this? View attachment 768431

When I'll boot installer usb, they force me to restart because of error, showing me a log error... My macbook is a air mid 2011

nvram boot-args=-no_compat_check is a command to run in Terminal, not a key/value for com.apple.Boot.plist. However, you shouldn't need to set it in NVRAM and in that plist anyways. One or the other should be enough.

Finally, the -no_compat_check only bypasses the (\) icon at startup. It will not fix any other crashes later on. What's the error you're seeing?
 
  • Like
Reactions: Larsvonhier
This log annexed it's appearing to me...
 

Attachments

  • Installer Log 30-Jun-2018.txt
    107 KB · Views: 344
Can you please elaborate the steps u did to install majave on it MBP 2011 machine.I have a MBP early 2011 15" running on Intel HD graphics chip only.
 
Hi Guys, Thanks for the patch. I now installed it on my MBP early 2011. A quick question, will we be able to update to latest beta updates when they get released with no problems? If we can, do we need to apply the patch again?

Thanks in advance.
Can you please elaborate the steps to install Mojave on it MBP early 2011?Is your MBP running on integrate d Intel graphics or discrete AMD Radeon graphics?
 
The CPUs in quad-core 2011 iMacs and MacBook Pros outperform plenty of the supported Macs' CPUs, including the brand new $1,200 MacBook.

It's absurd that Apple no longer supports them in Mojave, but I suppose the threat of such good value-for-money used Macs must be neutralized. ;)
it was the same story with the mac pro 3.1's losing support a few years ago.
 
  • Like
Reactions: Starplayr
Can you please elaborate the steps to install Mojave on it MBP early 2011?Is your MBP running on integrate d Intel graphics or discrete AMD Radeon graphics?

I have the MacBook Pro "Core i5" 2.3 13" Early 2011 version with integrated graphics only. (MacBook8.1)

What I did was:
- Download Mojave with the Patcher.
- Create a USB Installer with the patcher.
- Restart into the USB Installer.
- Make sure the HDD/SSD is formatted to Mac os extended journaled. Due to apfs not working and the patch for it greyed out at the moment. (Hopefully they fix this soon)
- Install Mojave.
- Once installed. Reboot back into the USB Installer and run the Patch for your version of MBP (Yours might be Macbook8.1 or MacBook8.2 version) and rebuild the Cache.
- Then restart the MBP and you should able to carry on with the setup process.

Let me know how it goes. You should be able to install it by follow those steps.

For your information @dosdude1
 
Last edited:
Report: Successful install on 2011 iMac
iMac12,2 2.7 GHz Core i5-2500S, 12 GB RAM, AMD Radeon HD 6770M 512 MB


Install to Firewire 400 disk formatted as APFS worked, but wouldn't boot. I got the no symbol. I didn't try reformatting it as HFS+. So I created a new APFS partition on my internal drive and that worked. (I love how easy this is to do via APFS.)


Initial impression:

System was very, very, very slow during setup and early use. It seemed to progress to just being slow after a while.
Youtube HD videos play correctly in Safari.
The News application is interesting, but content is too dense. It needs more white space.
Chrome seems to work OK.


Problems:

"Automatically adjust brightness" doesn't work.
Lots of video tearing when moving windows, many windows don't redraw until they take damage.
Lastpass application crashes, lastpass Safari extension doesn't work until you restart Safari.
Home application won't launch, says that it's damaged or incomplete (?).


So kudos to dosdude1 for getting this to work at all, but while it's interesting to play with it's really not usable for day to day use.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.