Sidebar Sidebar
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

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.
I don't have a supported Mac to install macOS Sierra on, but I have the installer, and all the patches downloaded.

I want to install it to a disk named Sierra, could i put the InstallESD on a USB, and replace InstallableMachines.plist and PlatformSupport.plist, install it, and then do the rest of the work from Mavericks? (kexts, replacing the plists again)
 
NOTNlCE said:
Shouldn't make a difference. If anything, being able to boot from the flash drive is MORE of an indication that the USB injector works.
Click to expand...

I have tried EVERYTHING yet parrotgeek1's LegacyUSBInjector.kext still will not load/work for me. That single incompatibility is the only thing preventing every El Capitan compatible Mac I own from running the 10.12 "Sierra" Beta at this moment.
 
it0uchpods said:
I don't have a supported Mac to install macOS Sierra on, but I have the installer, and all the patches downloaded.

I want to install it to a disk named Sierra, could i put the InstallESD on a USB, and replace InstallableMachines.plist and PlatformSupport.plist, install it, and then do the rest of the work from Mavericks? (kexts, replacing the plists again)
Click to expand...
Your Mac may not be able to run Sierra until we find a way to reverse the SIP check within the Bootloader considering the fact that even El Capitan had this annoying security feature that could only be disabled from the recovery partition.
 
On a Macbook Mid 2009 and the trackpad/keyboard doesn't work with Sierra. I don't own a real Newer Macbook Model other than my Hackintosh El Capitan desktop gaming rig and my Macbook Mid 2009.

Which kexts do I want from El Capitan that I can use in Sierra? I will probably need wireless, trackpad, and keyboard. Not too sure that I was getting wireless either. That is why I said I might need the wireless kext.
 
Last edited:
WadeWiIson said:
On a Macbook Mid 2009 and the trackpad/keyboard doesn't work with Sierra. I don't own a real Newer Macbook Model other than my Hackintosh El Capitan desktop gaming rig and my Macbook Mid 2009.

Which kexts do I want from El Capitan that I can use in Sierra? I will probably need wireless, trackpad, and keyboard. Not too sure that I was getting wireless either. That is why I said I might need the wireless kext.
Click to expand...

Your MacBook is also one of the same exact models that I am having difficulty with. I have only intermittently achieved functionality by installing this modified IOUSBHostFamily.kext though its fairly pointless as after a boot or two, the MacBook loses functionality once again and reinstalling the kext will be necessary.
 

Attachments

  • IOUSBHostFamily.kext.zip
    759.8 KB · Views: 447
Hello @ all, have a Macbook Pro 4.1 15" with 512MB GDDR but my supported Mac Pro 5.1 have a damage graphics card, must wait before I can say more in this forum (have kernel panics and so on). Make new account, cauz the old one is removed, why? o_O
 
Last edited:
WadeWiIson said:
I'm quite confused on this. I thought the compatibility with Macbook Mid 2009 was perfect from what the guide says on here. Or is it because not all Macbook Mid 2009's are the same? Meaning I could have a different trackpad, keyboard, and wireless features in it?

https://forums.macrumors.com/attachments/screen_shot_2016_06_15_at_1_48_41_pm-png.636161/
Click to expand...

Unfortunately thus far my experiences have been different then the link indicates. In achieving boot with the modified IOUSBHostFamily.kext on several occasions, once the track pad/keyboard/USB is functional, I found every single portion of Sierra with the same MacBook working flawlessly. Nothing else is needed.
 
Last edited:
it0uchpods said:
Can you explain a little more @TMRJIJ?
Click to expand...
SIP is a giant system-wide sandbox, that controls access to what Apple considers critical files and folders. One of the reasons for this is that most of kernel side SIP implementation exists into the Sandbox.kext, the same TrustedBSD kernel extensions that implements OS X/macOS sandbox mechanism.
It was implemented in OS X El Capitan and while the original Beta Chipset Kexts that I had (before @dosdude1 modified it for macOS Sierra) may work for your model, unsigned kexts in general won't function because this feature blocking them can only be disabled from the recovery partition. This creates a sense of irony that the only way to use the keyboard and mouse and continue the installation is to use the kexts, however we have to disable SIP first,... but we can't if the keyboard and mouse are not working.
The only workaround I see is to create a new Bootloader that skips the NVRAM check for the csrutil=1 or 0 but my knowledge is limited in that area. I have contacted Pike R. Alpha, the developer who make the 32bit EFI Bootloaders for Mac Pros and some MacBook Pro, and hopefully he may give me some insight on how to do this.

Also, I think I saw on the OS X Hackers Facebook page, correct? :)
 
Unfortunately, I don't own the model in question or I would give it a shot for you. I can only verify that my Early 2009 iMac is working, and I have outlined the process that I personally went through. Does my iMac even need the USB injection? From what I can tell, it uses an NVIDIA chipset which is otherwise supported.
 
NOTNlCE said:
Unfortunately, I don't own the model in question or I would give it a shot for you. I can only verify that my Early 2009 iMac is working, and I have outlined the process that I personally went through. Does my iMac even need the USB injection? From what I can tell, it uses an NVIDIA chipset which is otherwise supported.
Click to expand...

I guess that this is for me ;). It's nice to see that your iMac is compatible. Next week I will try to install it on my 08, i will tell you later how it went.
 
TMRJIJ said:
SIP is a giant system-wide sandbox, that controls access to what Apple considers critical files and folders. One of the reasons for this is that most of kernel side SIP implementation exists into the Sandbox.kext, the same TrustedBSD kernel extensions that implements OS X/macOS sandbox mechanism.
It was implemented in OS X El Capitan and while the original Beta Chipset Kexts that I had (before @dosdude1 modified it for macOS Sierra) may work for your model, unsigned kexts in general won't function because this feature blocking them can only be disabled from the recovery partition. This creates a sense of irony that the only way to use the keyboard and mouse and continue the installation is to use the kexts, however we have to disable SIP first,... but we can't if the keyboard and mouse are not working.
The only workaround I see is to create a new Bootloader that skips the NVRAM check for the csrutil=1 or 0 but my knowledge is limited in that area. I have contacted Pike R. Alpha, the developer who make the 32bit EFI Bootloaders for Mac Pros and some MacBook Pro, and hopefully he may give me some insight on how to do this.

Also, I think I saw on the OS X Hackers Facebook page, correct? :)
Click to expand...

So the step of booting up in an El Capitan Recovery HD, executing the command: "csrutil disable; reboot" (without the quotes) and disabling SIP from there is not working/not actually disabling it on the Sierra Volume ?

If so, that might explain after attempting to do so, the Volume I tried to disable SIP on only gives the "no smoking" symbol now when trying to boot it.
 
gpatpandp said:
So the step of booting up in an El Capitan Recovery HD, executing the command: "csrutil disable; reboot" (without the quotes) and disabling SIP from there is not working/not actually disabling it on the Sierra Volume ?

If so, that might explain after attempting to do so, the Volume I tried to disable SIP on only gives the "no smoking" symbol now when trying to boot it.
Click to expand...
Yes, the actual setting for SIP is in the NVRAM, not anywhere on the volume itself. You basically just disabled SIP on the supported Mac, not the Mac you are intending on booting Sierra on.
 
@TMRJIJ, no way to install Sierra without supported mac, even with pre-installed dmg? I have Macbook 5,2 and want to try Sierra, can I install it right from ElCap?
 
TMRJIJ said:
Yes, the actual setting for SIP is in the NVRAM, not anywhere on the volume itself. You basically just disabled SIP on the supported Mac, not the Mac you are intending on booting Sierra on.
Click to expand...

Even despite pointing the directory (i.e. cd /Volumes/my Sierra Drive that I intended on disabling SIP) appropriately in the recovery drive terminal ?
[doublepost=1466109320][/doublepost]
Herfindale said:
@TMRJIJ, no way to install Sierra without supported mac, even with pre-installed dmg? I have Macbook 5,2 and want to try Sierra, can I install it right from ElCap?
Click to expand...

No supported Mac needed once you correctly build a 10.12 Beta installer. The issue that you will face is no trackpad/keyboard/USB functionality once the installer boots.
 
gpatpandp said:
Even despite pointing the directory (i.e. cd /Volumes/my Sierra Drive that I intended on disabling SIP) appropriately in the recovery drive terminal ?
[doublepost=1466109320][/doublepost]

No supported Mac needed once you correctly build a 10.12 Beta installer. The issue that you will face is no trackpad/keyboard/USB functionality once the installer boots.
Click to expand...
In order to disable SIP, you MUST boot into the Recovery partition on the machine you intend to run unsigned kexts on (so in this case your unsupported Mac). This property is stored in NVRAM, so it can be done using El Capitan's recovery partition if necessary. Just boot Recovery, open Terminal, and run "csrutil disable". Reboot, and you should be able to load unsigned kexts.
 
cammykool said:
Im excited to see if anything comes fr my MP 1,1
Click to expand...

Unfortunately there is no point in doing so as those machines have lacked GPU support since OS X 10.9 Mavericks.
[doublepost=1466110141][/doublepost]
dosdude1 said:
In order to disable SIP, you MUST boot into the Recovery partition on the machine you intend to run unsigned kexts on (so in this case your unsupported Mac). This property is stored in NVRAM, so it can be done using El Capitan's recovery partition if necessary. Just boot Recovery, open Terminal, and run "csrutil disable". Reboot, and you should be able to load unsigned kexts.
Click to expand...

So despite pointing the directory to the Sierra installed Volume, merely entering the csrutil disable; reboot command within the El Capitan Recovery HD terminal effectively disabled the SIP on that particular machine ?

 
gpatpandp said:
Unfortunately there is no point in doing so as those machines have lacked GPU support since OS X 10.9 Mavericks.
Click to expand...
Not after upgrading the graphics card... But, Sierra won't be able to run on those machines anyways, due to the lack of SSE4.1.
 
Just curiosity, I've imagine that I can't not simply install a Sierra beta update from the Mac App Store running on a Mac not supported. So, what we can do after Apple releases new betas? Is there some kind of patch?
 
dosdude1 said:
Not after upgrading the graphics card... But, Sierra won't be able to run on those machines anyways, due to the lack of SSE4.1.
Click to expand...

Disregard my response...I misunderstood/mistakenly read his initial inquiry as a MBP (MacBook Pro) 1.1/1.2. I am all to familiar with the Mac Pro 1.1/1.2. In fact I am thinking about giving Clover a go in my 2,1 though mike boss pointed out a critical existing flaw with Mac Pro's and integer codes in Sierra that might make it prohibitive.
[doublepost=1466112504][/doublepost]
gpatpandp said:
Disregard my response...I misunderstood/mistakenly read his initial inquiry as a MBP (MacBook Pro) 1.1/1.2. I am all to familiar with the Mac Pro 1.1/1.2. In fact I am thinking about giving Clover a go in my 2,1 though mike boss pointed out a critical existing flaw with Mac Pro's and integer codes in Sierra that might make it prohibitive.
Click to expand...

Also just thought I would mention to folks that just because your unsupported Mac operates hacked with the first Beta is no guarantee that will be the case once it is officially released. I am "old school" going back to the Mac Pro Jabbawok Chameleon/Mountain Lion hack as well as the "Hacker Wayne" ML PostFacto days.

Case in point: Back in the day when the first initial OS X 10.8 Developer Preview Beta was released, Apple included the compatibility for 32 Bit machines to boot the operating systems 64 Bit Kernel. In the VERY next Beta release, Apple totally removed all traces of the cabability and a whole slew of machine suddenly lost official support and the rest as they say is history.
 
MacBook_10.12.jpg
So I was able to repair my MacBook 5,2 10.12 Beta boot partition by removing the LegacyUSBInjector.kext from the Library/Extensions folder and reinstalling the modified IOUSBHostFamily.kext and performing permissions and kext cache commands.

As the pic posted indicates, pointing to a specific Volume directory doesn't make any difference nor does it matter whether you perform the SIP disable command in the Sierra or El Capitan Recovery HD.
 
I have found access to my fathers Late 2009 iMac, which is supported.

It has almost the same hardware as the Mac mini Late 2009, but with a different CPU.

Here is my install plan:

Install macOS Sierra onto my 64GB USB, do all the modifications, and check that it boots on the Mac mini.

Then boot into Mavericks, and run use disk utility to clone the USB to a partition on the hard drive. Will this work?

Is anyone planning on making a tutorial, if I get mine working, I have a spare Early 2009 MacBook I could use to make one.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back