Late 2009 uses DDR3, my Early 2009 uses DDR2 VRAM. That could be it.I thought the 9400M was the reason my Late 2009 mini got dropped, but the Late 2009 Macbook has the exact same card...
Maybe it'll be easy to unofficially run sierra on those...
Late 2009 uses DDR3, my Early 2009 uses DDR2 VRAM. That could be it.
But I'm currently working on modifying the installer to run on any Mac that can run 10.11. I can't get it though. But the method to run 10.9 Mavericks on the 2008 white MacBooks should work for all other 10.12 dropped Macs. Only thing with that method, you need access to a mac that natively supports 10.12.
What do you mean exactly? There's something with serial numbers?Late 2009 uses DDR3, my Early 2009 uses DDR2 VRAM. That could be it.
But I'm currently working on modifying the installer to run on any Mac that can run 10.11. I can't get it though. But the method to run 10.9 Mavericks on the 2008 white MacBooks should work for all other 10.12 dropped Macs. Only thing with that method, you need access to a mac that natively supports 10.12.
Hi everyone!
I've got a MacBook 5,1. After Sierra being available on the web, I downloaded it and started exploring the installer. Anybody knows what'd happen if I just include the board ID everywhere it's necessary, create an install media and launch the setup from the USB?
Visual Studio is like the XCode for Windows. Pike's open sourced his Bootloader so users can compile their own copies. There is a page tailer just for rootless. Some of it is in xml but I myself can't create an 64 bit version that could set rootless to not equal CsrActiveConfig... complicated stuff.
I think @Hennesie2000 's idea is the way to go for right now.
I'm not partially knowledgeable about editing the bootloader and install packages. I would appreciate a little guidance if you don't mind.
EDIT: Thinking about it, I installed a fully untouched copy onto an SSD, and yes I did mess with the Boot.efis but switched them back. Still having the same problem.
[doublepost=1465877885][/doublepost]Ok hopefully this helps a little bit. I restarted into Verbose mode and the last thing(s) the machine spit out was this:
View attachment 635764
Can you give me an example of how El Capitan or another version was crippled supporting the older hardware? Please, show me that you know what you're talking about.
Usually, if certain features don't work on older hardware, like AirDrop or Handoff, they are simply disabled on that hardware.
I'd be fine with Mountain Lion if not for the loss of security updates. I've considered rolling my early 2009 Mini back to Mavericks but it's going to lose security updates soon as well.
A little experimenting on my part. I installed Sierra on my MBP 2012 and then removed the drive and tried booting from the drive on a Macbook 2008 and Mac Pro 2008. Both just show the no entry sign at startup.
I did try to install Sierra with the board ID placed in all necessary files, it gives me the USB error. Anybody knows what it's caused by?
[doublepost=1465911425][/doublepost]
1) You didn't include your Mac's board ID into some files which mention to the computer what models are allowed to boot Sierra.
2) Even if you did 1, it would've given the forbidden sign at 2/3 of the boot process.
It's caused because Something about the board isn't supported with USB anymore. Go ahead. Boot from a hard drive partition. You'll boot up 100% get the GUI and everything and have zero use with a mouse and keyboard
The keyboard and trackpad on my MacBook are not connected by USB, so I'll give it a try.
Hello everyone, I am new to this forum but let's not get off the main topic here. So after going trough all pages here on the topic and trying to modify the gorgeous new Sierra Installer to run on my Macbook 5,1(Aluminium late 2008 Unibody),
I get stuck to the Locked(Read-only) partition OS X Install ESD(mainly the folder Packages), where I need to replace the OSInstall.mpkg and the InstallableMachines.plist. Tried: "sudo chflags -R nouchg", "sudo chmod a+rx", "sudo chflags 0" and then Reload Finder but I was not able to unlock it... And would be easier to just be created a guide like the one on page 5 by Hennesie2000 from the people who succeeded in installing the Sierra to their unsupported MacBooks. And I really like this idea of just letting Apple know that they have made a big mistake(obviously not an economical but environmental), it could change something considering the fact that they made a big mistake in messing up with the iOS 10 supported devices(iPod touch 5, I was so excited and baaaam after 3 hours: Oh sorry it's not supported!) but thats a talk for another topic.
Are you talking about macmini4,1? how do you do that I can't find a toolBig question is gonna be whether a 4,1 upgraded to 5,1 is going to be counted as a 2010/2012 by the installer.