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.
Will test with my MacBook5,2 as soon as the Sierra download completes.

Already beat you to it. Nada. Still either booting 2/3 of the way with a prohibited sign, or like my MacBook 4,1 with el cap, if you restore the installer to a hard drive partition, you'll boot to the installer, but there'll be no way to use a mouse or keyboard making it impossible to go any further.

There is something in the system. I'm not sure what. But it is hindering us to move forward. I can't seem to figure it out. The processors should match, I have the 9400 m which should work, what's failing? Should I start unhooking things like wifi and speakers? Maybe there's an unsupported kext that trips the installer.
 
Already beat you to it. Nada. Still either booting 2/3 of the way with a prohibited sign, or like my MacBook 4,1 with el cap, if you restore the installer to a hard drive partition, you'll boot to the installer, but there'll be no way to use a mouse or keyboard making it impossible to go any further.

There is something in the system. I'm not sure what. But it is hindering us to move forward. I can't seem to figure it out. The processors should match, I have the 9400 m which should work, what's failing? Should I start unhooking things like wifi and speakers? Maybe there's an unsupported kext that trips the installer.

From what Verbose mode spit out at me it looks like it might be something on the USB bus. Isn't that how the iSight and WiFi card connect to the Mac?

EDIT: IR Sensor, Camera, Bluetooth, Keyboard, and Trackpad are all on USB.
 
From what Verbose mode spit out at me it looks like it might be something on the USB bus. Isn't that how the iSight and WiFi card connect to the Mac?

EDIT: IR Sensor, Camera, Bluetooth, Keyboard, and Trackpad are all on USB.


Ok then how can we add a kext and force it to load? I know they tried this last year with El Cap but there was more wrong last year. We need to force USBInjectAll.kext to load. It's a hackintosh kext that loads any and every driver. Not to mention if we used an El Capitan version, we are more likely to have a working system. Someone needs to run over to tonymacx86 and ask if we even can force load kexts in an installer.
 
Ok then how can we add a kext and force it to load? I know they tried this last year with El Cap but there was more wrong last year. We need to force USBInjectAll.kext to load. It's a hackintosh kext that loads any and every driver. Not to mention if we used an El Capitan version, we are more likely to have a working system. Someone needs to run over to tonymacx86 and ask if we even can force load kexts in an installer.

Well, here's the weird thing. Verbose is complaining about power to USB. It doesn't see it, but it assumes it's there and continues. I posted a pic a few posts back.
 
Well, here's the weird thing. Verbose is complaining about power to USB. It doesn't see it, but it assumes it's there and continues. I posted a pic a few posts back.

That's what happens when USB isn't supported. Same thing happened with my Vivobook hackintosh when I switched from Yosemite to El Cap. Ran the Inject all kext using kext wizard and it worked fine.
 
Ok then how can we add a kext and force it to load? I know they tried this last year with El Cap but there was more wrong last year. We need to force USBInjectAll.kext to load. It's a hackintosh kext that loads any and every driver. Not to mention if we used an El Capitan version, we are more likely to have a working system. Someone needs to run over to tonymacx86 and ask if we even can force load kexts in an installer.

I don't think that will fix anything. USBInjectAll.kext was created to solve issues with port limits on machines with USB 3.0 in El Capitan because of the change in the OS X usb drivers.
 
That's what happens when USB isn't supported. Same thing happened with my Vivobook hackintosh when I switched from Yosemite to El Cap. Ran the Inject all kext using kext wizard and it worked fine.

Interesting. So these machines must use a different USB controller then the supported Macs. Now if I knew were the USB kexts were held...
 
I don't think that will fix anything. USBInjectAll.kext was created to solve issues with port limits on machines with USB 3.0.

It was as far as we got last year besides replacing wifi with a PCI USB card. Bad idea BTW.
[doublepost=1465881841][/doublepost]
Interesting. So these machines must use a different USB controller then the supported Macs. Now if I knew were the USB kexts were held...

Probably System/Library/Extensions
[doublepost=1465881887][/doublepost]
It was as far as we got last year besides replacing wifi with a PCI USB card. Bad idea BTW.
[doublepost=1465881841][/doublepost]

Probably System/Library/Extensions

Wait. I get what you're doing. You're gonna replace the Sierra USB kexts with El Cap ones.
 
It was as far as we got last year besides replacing wifi with a PCI USB card. Bad idea BTW.
[doublepost=1465881841][/doublepost]

Probably System/Library/Extensions
[doublepost=1465881887][/doublepost]

Wait. I get what you're doing. You're gonna replace the Sierra USB kexts with El Cap ones.

Bingo. Working on it now.
 
It was as far as we got last year besides replacing wifi with a PCI USB card. Bad idea BTW.
[doublepost=1465881841][/doublepost]

Probably System/Library/Extensions
[doublepost=1465881887][/doublepost]

Wait. I get what you're doing. You're gonna replace the Sierra USB kexts with El Cap ones.

I did work on new USB Kexts that would come with OS X Extractor 1.33 but we still need a working 64 bit Boot.efi with SIP disabled by default.
 
Bingo. Working on it now.

If it's that simple, I'll probably cry. Seriously. I've worked about 4 hours now in flat package editor.
[doublepost=1465882052][/doublepost]
I did work on new USB Kexts that would come with OS X Extractor 1.33 but we still need a working 64 bit Boot.efi with SIP disabled by default.

Where's Pike? He still makes the best (and only) boot.efi's
[doublepost=1465882154][/doublepost]
If it's that simple, I'll probably cry. Seriously. I've worked about 4 hours now in flat package editor.
[doublepost=1465882052][/doublepost]

Where's Pike? He still makes the best (and only) boot.efi's

Also, probably gonna need those kexts.
[doublepost=1465882202][/doublepost]Random thought;

Couldn't you go into Single User mode, target the installer partition of the hard drive, and then disable SIP?
 
If it's that simple, I'll probably cry. Seriously. I've worked about 4 hours now in flat package editor.
[doublepost=1465882052][/doublepost]

Where's Pike? He still makes the best (and only) boot.efi's
[doublepost=1465882154][/doublepost]

Also, probably gonna need those kexts.

I replaced all the USB kexts and still no luck.
 
If it's that simple, I'll probably cry. Seriously. I've worked about 4 hours now in flat package editor.
[doublepost=1465882052][/doublepost]

Where's Pike? He still makes the best (and only) boot.efi's
[doublepost=1465882154][/doublepost]

Also, probably gonna need those kexts.
[doublepost=1465882202][/doublepost]Random thought;

Couldn't you go into Single User mode, target the installer partition of the hard drive, and then disable SIP?

The SIP setting is only accessible within the Recovery Partition/Installer which would likely be inaccessible because you need the USB kexts. It's pretty ironic. The only other way is to modify the Bootloader to disable rootless (Windows PC with Visual Studio may be required).
 
The SIP setting is only accessible within the Recovery Partition/Installer which would likely be inaccessible because you need the USB kexts. It's pretty ironic. The only other way is to modify the Bootloader to disable rootless (Windows PC with Visual Studio may be required).

You could create a Clover based installer on a USB stick. That should allow you to load any kext you need and you could disable SIP.
 
You could create a Clover based installer on a USB stick. That should allow you to load any kext you need and you could disable SIP.


Yeah and not make it 10 seconds in. Clover doesn't play well at all with real macs. Though you don't have a bad start.
[doublepost=1465882965][/doublepost]
The SIP setting is only accessible within the Recovery Partition/Installer which would likely be inaccessible because you need the USB kexts. It's pretty ironic. The only other way is to modify the Bootloader to disable rootless (Windows PC with Visual Studio may be required).

I have a Windows PC. What's visual studio and what do I need to do? I've got nothing but time on my hands....well...starting tomorrow morning.
 
Yeah and not make it 10 seconds in. Clover doesn't play well at all with real macs. Though you don't have a bad start.
[doublepost=1465882965][/doublepost]

I have a Windows PC. What's visual studio and what do I need to do? I've got nothing but time on my hands....well...starting tomorrow morning.

It works fine if you boot in Legacy Mode. Used to use it on my 2006 MacPro to run 10.9 before Tiamo created the boot.efi.
 
It works fine if you boot in Legacy Mode. Used to use it on my 2006 MacPro to run 10.9 before Tiamo created the boot.efi.

I mean, I'll try it. But even then A, there's no clover or chameleon for Sierra. B, if I'm not mistaken, legacy mode is also a text mode making it almost impossible to turn SIP off and C, I honestly don't remember how to force kexts in it. I was a chameleon kind of guy
 
I mean, I'll try it. But even then A, there's no clover or chameleon for Sierra. B, if I'm not mistaken, legacy mode is also a text mode making it almost impossible to turn SIP off and C, I honestly don't remember how to force kexts in it. I was a chameleon kind of guy

Legacy mode isn't text only. It just allows you to boot the efi file located in the Clover install. From there you will have the full graphics of the boot loader.

You can disable SIP with settings in your Clover config.plist. Set your BooterConfig to 0x28 and set your CsrActiveConfig to 0x67. That will completely disable SIP without needing to go into the RecoveryHD.

But yes there isn't an official Clover for Sierra yet.
 
Yeah and not make it 10 seconds in. Clover doesn't play well at all with real macs. Though you don't have a bad start.
[doublepost=1465882965][/doublepost]

I have a Windows PC. What's visual studio and what do I need to do? I've got nothing but time on my hands....well...starting tomorrow morning.
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.
 
Isn’t it enough to disable SIP with the El Capitan Recovery/Installer? The setting is stored in NVRAM, so it shouldn’t matter.
 
Isn’t it enough to disable SIP with the El Capitan Recovery/Installer? The setting is stored in NVRAM, so it shouldn’t matter.
Maybe for the recently disowned Macs. I have yet to finish installing Sierra on my mid 2010 MacBook Pro to see if my custom Bluetooth kexts brick it. However those 'really old' Macs in my OS X Hackers realm like the MacBook 3,1 and 4,1 couldn't run El Capitan without this workaround.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.