Currently installing Sierra on a hard drive in an enclosure via my rMBP. Once it installs, I'll take the drive out of the enclosure, stick it into my MacBook5,2 and see what happens.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.12 Sierra Unsupported Macs Thread
- Thread starter redheeler
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Hey guys I am about to give up after a 20 hours of trying to start the installation without seeing the annoying message "Sorry but your upgraded mac - that is way more powerful than the 2016 MB is not compatible with this version of macOS" Or get stuck at file copying because of the Read only filesystem of my installation. I think we should wait until the recovery image comes out because obviously this beta image is not bootable. But I think that we really shall at least annoy Apple because they are dropping support of computers who are useful and valuable to us... Thanks to their "strategy" I'm not anymore able to develop apps because of the Xcode updates... So wish you luck guys and I believe that you will succeed and hope there will be a good guide so everyone can upgrade.
I guess we should learn how to rebuild the prelinked kernel with .kext's we need for USB.
The probable reason why it does that is the new feature which appeared in El Capitan, where it blocks custom kernel extensions. You could turn it on or off there from recovery, though (at least in betas). Maybe there is such an option somewhere in the installer, but it seems unlikely.
The probable reason why it does that is the new feature which appeared in El Capitan, where it blocks custom kernel extensions. You could turn it on or off there from recovery, though (at least in betas). Maybe there is such an option somewhere in the installer, but it seems unlikely.
I got it booted and running on my MacBook 5,2. No USB or input working yet, but I set up AutoLogin and set System Profiler to open at login to show it running. http://dosdude1.com/pics/sierra/bootedmb5,2.JPG
Got Sierra downloaded and installed on a hard drive. I put the hard drive in my MacBook5,2 and edited PlatformSupport.plist with the board-id and model identifier via El Capitan. When attempting to boot into Sierra in verbose mode, I get stuck with the MacBook spewing lines that have to do with processes crossing the high memory watermark, then the processes get terminated. Hmmm...
Last edited:
The only other place to allow custom kernel extensions is within the Boot.efi. There you can change the SIP settings to be disabled by default. After that you are free to set kext-dev-mode=1 when rebuilding the installer.
Try these kexts in my previous post.
I got it booted and running on my MacBook 5,2. No USB or input working yet, but I set up AutoLogin and set System Profiler to open at login to show it running.
Here's the new error verbose was spitting out:
MacBook-Pro.local com.apple.xpc.launchd[1] (com.apple.icloud.findmydeviced) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
MacBook-Pro.local com.apple.xpc.launchd[1] (com.apple.icloud.findmydeviced.459) <Error>: Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /var/empty: 16A201w: xpcproxy + 11972 [1404][DEVICE ID HERE]: 0x2
(note, where DEVICE ID HERE is, there was a UDID of sorts of my machine. Removed for security reasons).
EDIT: Seems the hackintosh community is having a similar issue when trying to install 10.12: https://m.reddit.com/r/hackintosh/comments/4o0tjx/creating_a_macos_sierra_hackintosh/
MacBook-Pro.local com.apple.xpc.launchd[1] (com.apple.icloud.findmydeviced) <Notice>: Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
MacBook-Pro.local com.apple.xpc.launchd[1] (com.apple.icloud.findmydeviced.459) <Error>: Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /var/empty: 16A201w: xpcproxy + 11972 [1404][DEVICE ID HERE]: 0x2
(note, where DEVICE ID HERE is, there was a UDID of sorts of my machine. Removed for security reasons).
EDIT: Seems the hackintosh community is having a similar issue when trying to install 10.12: https://m.reddit.com/r/hackintosh/comments/4o0tjx/creating_a_macos_sierra_hackintosh/
Sorry for the "noobness" here, but how do I get it to load the kexts? I've already tried copying them to /S/L/E, but it seems to just ignore them and uses prelinkedkernel. It also fails to rebuild prelinkedkernel on boot.
You successfully booted it up, right? try this after you add the kexts.
Code:
cd /Volumes/[Your HD Name]
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches
True answer is because they want to...they want you to buy newer Mac.
[doublepost=1465928032][/doublepost]
Is there any reason why you want to stay in 2009 Mac? Curious.
You need to use kext wizard on your supported Mac. Not only does it put kexts where needed, but it makes your device rootless
[doublepost=1465928130][/doublepost]
I used to use kext wizard. Or kext utility. Can he do that on a supported Mac? The kexts would transfer to an unsupported
I know that's wrong. Check when kext utility starts up. It says first thing "Kext_Dev_Mode and Rootless=0." Without you doing a single thing. If only temporarily, it does disable them.
Kext Wizard is unable to bypass SIP and can't modify /System/Library/Extensions.
Well I'll Disable SIP then in single user mode. Now that there's a working installed version, that shouldn't be too hard. AND I'll still use kext wizard to install those kexts.
Maybe it is an option to write a Recovery startup script which disables SIP (don't know if that's possible).
If I can do it on my supported Mac, it should work. What command do I need to run to disable SIP? Another method I was thinking about trying was using Clover to boot, if all else fails, I'll try that.
Those Macs haven't been able to run OS X well since 10.8... Is it worth porting Sierra to those at this point? I think we should try to get it running on El Capitan compatible Macs, and once it runs reliably on those, take care of the older ones.
From what I could gather online, you need to enter recovery, go to terminal and type csrutil disable. I remember a way in single user mode, I just don't remember how.