macOS 10.12 Sierra Unsupported Macs Thread

[Czo]

Thanks! Yes please do reply with the full instructions on how to fix this. I would like to upgrade back to Sierra but only if I can be sure how to fix this problem if / when it happens again.

You need to boot to Sierra's recovery, and run the following commands. Maybe, you need to modify the commands if your startup disk is not named to "Macintosh HD":

First disable SIP (this also can be run from El Capitan's recovery):

csrutil disable

If everything is ok, you see this:

Successfully disabled System Integrity Protection. Please restart the machine for the changes to take effect.

The next commands only print something if error occured.

Now, you need to remove the non working prelinkedkernel with this:

rm "/Volumes/Macintosh HD/System/Library/PrelinkedKernels/prelinkedkernel"

The system recreates prelinkedkernel, if some of the extensions are changed, so need to "change something":

touch "/Volumes/Macintosh HD/System/Library/Extensions"

Now, if everything went fine, you need to wait 2-3 minutes and try a reboot.
[doublepost=1486674651][/doublepost]

iv seen that. I got the offset and the dump but when I tried to edit the iMac section it causes display preferences to crash system preferences when I click on it
https://www.tonymacx86.com/threads/...rebrightness-macos-10-12.213764/#post-1435420
[doublepost=1486660939][/doublepost]
It must have been the way you worded it that caught me off guard. I apologize for taking it the wrong way

Did you codesign the modified binary? If you don't the display prefpane will crash.

 

[nandor690]

Did you codesign the modified binary? If you don't the display prefpane will crash.

How do I do that?

 

[fischersd]

I think you may not be familiar with the process. You do not need "specific reasons" to have a kext sign request. It simply needs to be a driver used by the system or be something that needs to run for many users.

Regardless of the steps you need to take to get the access, distributing kexts with your dev signing authority for purposes of circumventing Apple's policies will have a pretty predictable result.

 

[Sedulous]

Regardless of the steps you need to take to get the access, distributing kexts with your dev signing authority for purposes of circumventing Apple's policies will have a pretty predictable result.

Culpability by proxy makes no sense. It is like Apple pulling Microsoft's license because someone used Word to write a nasty latter to Cook. A developer creates a piece of software. Someone else uses that software. What they use it for is not the developer's problem.

 

[kdc1]

Hi, dosdude1 thank you for your patched Sierra, could you help me with Continuity Activation Tool for unsupported Mac? I have a mbp 5,1 (late '08) and when I try to install CAT to enable continuity features my Mac hang at Apple Logo boot bar.


ht**s://github.com/dokterdok/Continuity-Activation-Tool

 

[Czo]

How do I do that?

sudo codesign -f -s - /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/Current/CoreBrightness

Maybe this only successful if you have a valid dev account.

 

[nandor690]

You need to boot to Sierra's recovery, and run the following commands. Maybe, you need to modify the commands if your startup disk is not named to "Macintosh HD":

First disable SIP (this also can be run from El Capitan's recovery):

csrutil disable

If everything is ok, you see this:

Successfully disabled System Integrity Protection. Please restart the machine for the changes to take effect.

The next commands only print something if error occured.

Now, you need to remove the non working prelinkedkernel with this:

rm "/Volumes/Macintosh HD/System/Library/PrelinkedKernels/prelinkedkernel"

The system recreates prelinkedkernel, if some of the extensions are changed, so need to "change something":

touch "/Volumes/Macintosh HD/System/Library/Extensions"

Now, if everything went fine, you need to wait 2-3 minutes and try a reboot.
[doublepost=1486674651][/doublepost]

Did you codesign the modified binary? If you don't the display prefpane will crash.

sudo codesign -f -s - /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/Current/CoreBrightness

Maybe this only successful if you have a valid dev account.

ill try it with my free account and see if it works for 7 days lol

 

[fischersd]

Culpability by proxy makes no sense. It is like Apple pulling Microsoft's license because someone used Word to write a nasty latter to Cook. A developer creates a piece of software. Someone else uses that software. What they use it for is not the developer's problem.

Right...because that's a comparable scenario. Responsible dev's and companies wouldn't jeopardize their livelihood this way.

Apple doesn't need to prove that you had intent. You would need to prove why you did what you did in terms of altering the code and some plausible mechanism for how these signed items ended up in the hands of a community working to keep unsupported systems running Apple's OS.

This debate is pointless. We're not going to agree. You want to get some kexts signed, get yourself a dev license for that purpose.
[doublepost=1486736286][/doublepost]

Hi, dosdude1 thank you for your patched Sierra, could you help me with Continuity Activation Tool for unsupported Mac? I have a mbp 5,1 (late '08) and when I try to install CAT to enable continuity features my Mac hang at Apple Logo boot bar.


ht**s://github.com/dokterdok/Continuity-Activation-Tool

Soo, you don't get an answer over on the CAT thread, so you decide to bring that topic to another thread?

 

[nandor690]

ill try it with my free account and see if it works for 7 days lol

That was exactly the problem. How cool is that. just change the hex number to 07 and it works! I missed that line that said Update: you need to re-sign the patched frameworks binary.
thanks again!!! Time to work on iSight now

 

[kdc1]

Soo, what's the problem? I asked here to the official releaser of Sierra unsupported Mac patcher, to see if he is able to fix this issue.

Right...because that's a comparable scenario. Responsible dev's and companies wouldn't jeopardize their livelihood this way.

Apple doesn't need to prove that you had intent. You would need to prove why you did what you did in terms of altering the code and some plausible mechanism for how these signed items ended up in the hands of a community working to keep unsupported systems running Apple's OS.

This debate is pointless. We're not going to agree. You want to get some kexts signed, get yourself a dev license for that purpose.
[doublepost=1486736286][/doublepost]
Soo, you don't get an answer over on the CAT thread, so you decide to bring that topic to another thread?

 

[fischersd]

Soo, what's the problem? I asked here to the official releaser of Sierra unsupported Mac patcher, to see if he is able to fix this issue.

Most forums, you're supposed to keep topics within the threads that have been created for them (I'm sure it's in the rules).

The CAT tool has absolutely nothing to do with dosdude1 or this thread. Why are you making the problems with that tool his problem?

 

[andreo]

Hi
I keep trying install Sierra on my non-Pro Macbook4,1 with 2,4GHz C2D and 4GB of Ram.
I'd prepared USB with DosDude1's tool. When I booting from my USB thumb I have 'Circle Slash'.
Also I burnt my usb thumb image on DVD and installer was running, but external and internal mouse and keyboard won't work.
Did you have any solution?

 

[fischersd]

Hi
I keep trying install Sierra on my non-Pro Macbook4,1 with 2,4GHz C2D and 4GB of Ram.
I'd prepared USB with DosDude1's tool. When I booting from my USB thumb I have 'Circle Slash'.
Also I burnt my usb thumb image on DVD and installer was running, but external and internal mouse and keyboard won't work.
Did you have any solution?

Sounds like you haven't disabled SIP. Boot in recovery mode, go to a terminal prompt and type csrutil disable

Then reboot from the USB installer you created with dosdude1's tool, install Sierra and remember to run the post install when you reboot (again, booting from the USB when you reboot).

 

[zrw2011]

what r u guys refering to my macbook has been fine

 

[toyosup88]

So i'm having a problem updating to 10.12.3 through the app store. I originally created a separate partition to install sierra to make sure it worked. i worked great and updated fine through app store. So i deleted that partition and installed 10.12.2 over El Capitan and now it says no updates available. Is there a way to fix this without doing a clean install?

 

[dosdude1]

So i'm having a problem updating to 10.12.3 through the app store. I originally created a separate partition to install sierra to make sure it worked. i worked great and updated fine through app store. So i deleted that partition and installed 10.12.2 over El Capitan and now it says no updates available. Is there a way to fix this without doing a clean install?

Did you apply the software update patch? If so, try running "sudo softwareupdate -l" in Terminal.

 

[TMRJIJ]

Hi, dosdude1 thank you for your patched Sierra, could you help me with Continuity Activation Tool for unsupported Mac? I have a mbp 5,1 (late '08) and when I try to install CAT to enable continuity features my Mac hang at Apple Logo boot bar.


ht**s://github.com/dokterdok/Continuity-Activation-Tool

We don't work with the Continuity Activation Tool in this thread. The development of that has its own thread. I do wish you luck since there have been kernel panic issues for even the newer Continuity Unsupported' macs.

 

[virk]

Hi
I keep trying install Sierra on my non-Pro Macbook4,1 with 2,4GHz C2D and 4GB of Ram.
I'd prepared USB with DosDude1's tool. When I booting from my USB thumb I have 'Circle Slash'.
Also I burnt my usb thumb image on DVD and installer was running, but external and internal mouse and keyboard won't work.
Did you have any solution?

I cannot see why your Macbook (late or early 2008?) should be supported at all.

 

[TMRJIJ]

Hi
I keep trying install Sierra on my non-Pro Macbook4,1 with 2,4GHz C2D and 4GB of Ram.
I'd prepared USB with DosDude1's tool. When I booting from my USB thumb I have 'Circle Slash'.
Also I burnt my usb thumb image on DVD and installer was running, but external and internal mouse and keyboard won't work.
Did you have any solution?

DosDude1's tool doesn't support your model. While you can make the necessary modifications to the scripts, you would need to find a way to disable SIP first (unless you manage to get El Capitan from the previous thread).
You can do it, but It's really not worth the trouble. In addition to lack of OpenGL support from Mavericks and onwards, you would have to deal with a wonky trackpad, keyboard, and USB issues.

 

[BuffyzDead]

You can simply use the WiFI card from a white Unibody MacBook, model A1342. The card is fully compatible with that machine and Sierra, but is slightly smaller that the original card, so you may have to get creative with the mounting.

Ok. I found and successfully installed a supported wifi card. The same card as was used in my first Mac Mini project; BCM943224PCIEBT

My issue:
At reboot: the card would not come up. The menu bar would say No Wifi Hardware installed. Of course I assumed one of the antenna wires came off OR I did not accurately plug the ribbon cable onto the wifi/Bluetooth board. BUT Bluetooth was working/enabled. Head scratching ensued and I thought to re open the Mac mini to make sure all connections were 100% sound.

Well, after several reboots, just verifying that everything was working fine, the wifi TURNED ON. Not only did it acknowlegde the hardware was installed but it auto connected to my wifi network. Then I thought, well the drivers downloaded/installed to support the card. I thought I was all set
BUT I saw it was only connecting to my 5Ghz network and would Not connect to my 2.4Ghz network!?!

I then recalled that this is also the exact same situation in my first late 2009 Mac Mini (3,1) project.
Only connects to 5Ghz network, not 2.4Ghz network. I was fine with that one, since that first Mini also connects via Ethernet. Leave good and workin alone.

But this second Mac mini will be set up to only connect via wifi 100%.

Now today, the wifi won't turn on at all. System Report says the hardware is there but, even after reboots, wifi will not turn on. Both trying to turn on in system preferences and in menu bar.

What can I try, please? ....what might be the cause? To both get the wifi card to turn on always, and to connect to 2.4Ghz network?

Sorry for the long post. I just wanted to communicate the complete situation.
Thank you again for all your work!!!

 

[nandor690]

Ok. I found and successfully installed a supported wifi card. The same card as was used in my first Mac Mini project; BCM943224PCIEBT

My issue:
At reboot: the card would not come up. The menu bar would say No Wifi Hardware installed. Of course I assumed one of the antenna wires came off OR I did not accurately plug the ribbon cable onto the wifi/Bluetooth board. BUT Bluetooth was working/enabled. Head scratching ensued and I thought to re open the Mac mini to make sure all connections were 100% sound.

Well, after several reboots, just verifying that everything was working fine, the wifi TURNED ON. Not only did it acknowlegde the hardware was installed but it auto connected to my wifi network. Then I thought, well the drivers downloaded/installed to support the card. I thought I was all set
BUT I saw it was only connecting to my 5Ghz network and would Not connect to my 2.4Ghz network!?!

I then recalled that this is also the exact same situation in my first late 2009 Mac Mini (3,1) project.
Only connects to 5Ghz network, not 2.4Ghz network. I was fine with that one, since that first Mini also connects via Ethernet. Leave good and workin alone.

But this second Mac mini will be set up to only connect via wifi 100%.

Now today, the wifi won't turn on at all. System Report says the hardware is there but, even after reboots, wifi will not turn on. Both trying to turn on in system preferences and in menu bar.

What can I try, please? ....what might be the cause? To both get the wifi card to turn on always, and to connect to 2.4Ghz network?

Sorry for the long post. I just wanted to communicate the complete situation.
Thank you again for all your work!!!

You could try going to /Library/Preferences/SystemConfiguration and deleting the Network and Airport plist and then reboot and set up wifi again. This has worked on some hackintoshes that I have upgraded

 

[Branskins]

The patcher keeps crashing on me giving me an error that it can't copy the files. When I select the option to continue as root the patcher crashes telling me that NSFileManager fileSystemRepresentationWithPath: is being passed a nil or empty path.

Any ideas?

 

[karthy]

I have a macbook pro 4,1 laptop, inbuilt speakers were working before the upgrade. The sound icon at the top right corner is greyed out when I alt click it, under output devices it doesn't detect internal speakers. how can I fix this

 

[fischersd]

The patcher keeps crashing on me giving me an error that it can't copy the files. When I select the option to continue as root the patcher crashes telling me that NSFileManager fileSystemRepresentationWithPath: is being passed a nil or empty path.

Any ideas?

I'd re-download the Sierra installer from Apple again (for some reason, a number of downloads are flawed). Might not hurt to try a different USB flash drive as well.
[doublepost=1486900953][/doublepost]

I have a macbook pro 4,1 laptop, inbuilt speakers were working before the upgrade. The sound icon at the top right corner is greyed out when I alt click it, under output devices it doesn't detect internal speakers. how can I fix this

It's not the 10.12.3 software update (I have the same MBP). It could be a race condition or just dust in your headphone jack.
Grab a pair of your Apple EarPods, go into System Preferences, Sound, Output on your mac - plug the EarPods into the headphone jack. Do headphones now show up? (make sure they work as well) If so, now unplug them and internal speakers should be back.

I know some people have fixed the sensor by shooting some compressed air in there - definitely don't recommend that - you're blowing dust into your MBP - you could cause a short somewhere inside and cause serious problems.

 

[slimmy18222]

Nice, the one I put in the late 2008 MacBook Air (same card as found in the 2009 Mac mini) works great in Sierra. Antenna connectors are subtly different though, so it takes a bit of effort to make good contact.

It's already an older card that works back to Snow Leopard, and tested back to Snow Leopard on my 2008 MacBook Air. El Capitan supports it just fine.

Done.

How does it's working? I have seen that AirPort from A1342 doesn't have temperature sensor on it,as shows on Hardware Apple test. Anyway please give a feedback in how this solutions is working on your Macbook Air and if it's worth the effort using Sierra on it