macOS 10.12 Sierra Unsupported Macs Thread

[dosdude1]

Installed Sierra on my Early 2009 iMac a few weeks ago. Ran into the loss of mouse and keyboard issues after 2 days. No fix worked. Had to reinstall El Cap from a backup. After following this thread and seeing the recommendation of disabling SIP, I decide to try again. All has been good for 5 days. Again, thank you dosdude!

Now I see updates are/might be available. Can someone point me in the right direction on the best way to do these? THANKS!

Just use AUSEnabler. Details are located here: http://swdist.furcode.co/aus-enabler

 

[psu7276]

dosdude1,

Thanks for the prompt reply. Things were easy and worked fine. Now a silly question. Does the last patch take care of all future updates or does it need to be run again for each future update?

BTW, for anyone debating the installation of Sierra, it is worth it. I can see an improved speed difference!

 

[Sedulous]

dosdude1,

Thanks for the prompt reply. Things were easy and worked fine. Now a silly question. Does the last patch take care of all future updates or does it need to be run again for each future update?

BTW, for anyone debating the installation of Sierra, it is worth it. I can see an improved speed difference!

The update patch will work for future OS updates. As I understand it, the patch basically tricks the Apple update server.

Yeah, OS 10.12 works great on my unsupported Mac too. Makes me mad that Apple drops support for machines that can capably run the OS. I guess Apple likes fragmentation or doesn't understand that people do not buy new computers every year.

 

[foxlet]

The update patch will work for future OS updates. As I understand it, the patch basically tricks the Apple update server.

Yeah, OS 10.12 works great on my unsupported Mac too. Makes me mad that Apple drops support for machines that can capably run the OS. I guess Apple likes fragmentation or doesn't understand that people do not buy new computers every year.

It's not a "patch" as used traditionally, nor does it use any client-side tricks on Apple's update server. The server-side software replaces the metadata component entirely.

 

[parrotgeek1]

It's not a "patch" as used traditionally, nor does it use any client-side tricks on Apple's update server. The server-side software replaces the metadata component entirely.

cant you make it run its own server which retrieves and edits the xml, then point the update server to 127.0.0.1?
[doublepost=1477467506][/doublepost]

ohhh, @dosdude1 kernelcache can't be a file, when you do the kextcache in the postinstall, you have to output it to prelinkedkernel

bump @dosdude1

Also, given that someone said their imac volume worked when another audio device was plugged in, I made a tiny driver which pretends to be an audio device but does not do anything. Can someone see if that works? Put the zip contents in /Library/Audio/Plug-Ins/HAL

(Yes I know it shows up in system preferences as a "volume control" but if it works I can make it hidden)

 

[Appleuser4life60077]

so far I am very happy with my mid 2009 white MacBook running Sierra, it did the update yesterday morning with no issues and continues to work great. I have a white 2010 unibody MacBook I got in a trade for one of the a1181 MacBooks I restored and selling, since the person who had it managed to step on the display and obviously ruined it. probably shouldn't be in a big hurry to get a screen for it since this a1181 running Sierra is working perfect and gets about 3 hours on a original battery with 500 cycles on it. I just like the design of the unibody better...think it looks prettier...

 

[dosdude1]

cant you make it run its own server which retrieves and edits the xml, then point the update server to 127.0.0.1?
[doublepost=1477467506][/doublepost]

bump @dosdude1

Also, given that someone said their imac volume worked when another audio device was plugged in, I made a tiny driver which pretends to be an audio device but does not do anything. Can someone see if that works? Put the zip contents in /Library/Audio/Plug-Ins/HAL

(Yes I know it shows up in system preferences as a "volume control" but if it works I can make it hidden)

I'll give that a try as soon as I get access to my 24" iMac 8,1 (I currently have a 20" iMac 8,1 with me, however it doesn't have the volume control problem under Sierra). I'll let you know the results once I'm able to properly test it.

 

[foxlet]

cant you make it run its own server which retrieves and edits the xml, then point the update server to 127.0.0.1?
[doublepost=1477467506][/doublepost]

bump @dosdude1

Also, given that someone said their imac volume worked when another audio device was plugged in, I made a tiny driver which pretends to be an audio device but does not do anything. Can someone see if that works? Put the zip contents in /Library/Audio/Plug-Ins/HAL

(Yes I know it shows up in system preferences as a "volume control" but if it works I can make it hidden)

If you mean running the server-side software as a local process bound to localhost, yes, it can do that. That's how the system is debugged internally to test updates, for that matter. It involves more than just editing a single XML file though.

Now, if the question really is if that will be distributed in the same way as an app that can be ran by an user, it's an unfortunate no. I don't have plans to support user-ran versions of AUS at the moment (there's a need to consider variables such as needed dependencies, OS differences, network setup, etc, that makes it difficult to work out a local solution compared to the current one).

 

[FilthyMuppetInnuendo]

Posting again because I apparently screwed something up.

Hi, everyone. Is there a feature to search within only a specific thread? 140 pages are a pain to read through. I’m running into an error during installation on my 2009 Mac Pro, but I can’t export the log (the installer just hard freezes everything before I can do so) and I can’t seem to reset the installer to try again (it would probably work if I wiped the stick and rebuilt it, but I want to avoid that if I can). I just want to search this thread for anyone else having the same or similar error before potentially repeating something common.

Funny thing is, I managed to get Sierra installed and working perfectly on this thing before, but for only one boot session. After which it wigged out and I had to revert things.

Thanks for any help!

 

[schreinerman]

I found for Macbook Air Late 2008 / Mid 2009 a WLAN card that replaces the not usable WLAN.

It is a card of an Apple MacBook Pro 13 A1342 (607-5953-B).

I plugged it successfully to the 30-pin header and recognized 0x14E4, 0x93

It is a little bit smaller than the original one and the antenna connectors seems to be different. Also without cables connected, it connects to my WLAN-router. Anyhow, I try to find a solution to get the antennas connected...

I'll keep you up-to-date...

Update: See some photos attached...

 

[dlfgma]

CloudFlare acceleration is simply not going to be used. Flushing the cache defeats the point of using a cache in the first place. (And there is no maintained API to automate it, either).

furcode site is down..

 

[chazzzzman]

@foxlet I cannot get your update tool to work. I've installed it on two MacPro 2009's running Sierra but it just hangs when I run it.. no window to select catalog.

Is there something wrong with it right now?

Thanks!

Charles

 

[parrotgeek1]

If you mean running the server-side software as a local process bound to localhost, yes, it can do that. That's how the system is debugged internally to test updates, for that matter. It involves more than just editing a single XML file though.

Now, if the question really is if that will be distributed in the same way as an app that can be ran by an user, it's an unfortunate no. I don't have plans to support user-ran versions of AUS at the moment (there's a need to consider variables such as needed dependencies, OS differences, network setup, etc, that makes it difficult to work out a local solution compared to the current one).

Can you at least open source it?

 

[foxlet]

@foxlet I cannot get your update tool to work. I've installed it on two MacPro 2009's running Sierra but it just hangs when I run it.. no window to select catalog.

Is there something wrong with it right now?

Thanks!

Charles

One of the servers apparently went down, the cause is still under investigation.

 

[chazzzzman]

One of the servers apparently went down, the cause is still under investigation.

OK.. thanks!
[doublepost=1477512490][/doublepost]

One of the servers apparently went down, the cause is still under investigation.

Works now!

 

[Pinarek]

[QUOTE = "schreinerman, Beitrag: 23784725, Mitglied: 1054256"] fand ich für Macbook Air Ende 2008 / Mitte 2009 eine WLAN-Karte, die den nicht nutzbaren WLAN ersetzt.

Es ist eine Karte von einem Apple MacBook Pro 13 A1342 (607-5953-B).

Ich steckte es erfolgreich an den 30-Pin-Header und erkannte 0x14E4, 0x93

Es ist ein wenig kleiner als die ursprüngliche und die Antennenanschlüsse scheint unterschiedlich zu sein. Auch ohne Kabel angeschlossen ist, wird eine Verbindung mit meinem WLAN-Router. Wie auch immer, ich versuche, eine Lösung zu finden, die Antennen verbunden zu bekommen ...

Ich werde Sie auf dem Laufenden halten...

Update: Hier sehen Sie einige Fotos beigefügt ... [/ QUOTE]

Hallo Schreinerman, deutscher Kollege hier. Ich habe mir auch eine solche Karte bei Eaby bestellt, müsste demnächst ankommen. ich will die in meinem macmini3,1 Late2009 einbauen.
gibts mit den Antennensteckern Probleme? sind die nicht gleich groß wie bei der alten karte ?

 

[Kevbasscat]

I have a similar iMac to yours, mine just has a different CPU (2.93) and GPU (GT120 I think?). I honestly lost interest in trying to put MacOS on this old mac as it's a semi production machine so I can't afford any downtime. Was hoping to get a new mac once new ones are announced. We'll see what happens later this week.

Does anyone here know everything my early 2009 iMac needs to upgrade to Sierra ?

 

[Ludacrisvp]

@foxlet I cannot get your update tool to work. I've installed it on two MacPro 2009's running Sierra but it just hangs when I run it.. no window to select catalog.

Is there something wrong with it right now?

Thanks!

Charles

It's probably a lot easier if you would do the firmware update to turn your 2009 Mac Pro (macpro4,1) into the 2010 Mac Pro (macpro5,1) which is officially supported under Sierra.

 

[parrotgeek1]

.

 

[psu7276]

Does anyone here know everything my early 2009 iMac needs to upgrade to Sierra ?

I'm not quite sure what you are asking but I also have an Early 2009 iMac. Did the update and had problems because I did not disable SIP. (and I don't even know what SIP is!) After reading more posts I saw that the SIP disable was necessary for this machine. (and perhaps others) After doing this, the install and following operation has been issue free.

Just go back a few pages here and more details are available. Sierra is worth it! I definitely see a speed improvement.

 

[Sedulous]

Is there any way to get Apple to change their decision to withhold Sierra from machines that obviously are capable of running OS 10.12?

 

[foxlet]

Can you at least open source it?

Outside of what is already been open sourced, there are no further plans at the moment.

 

[FilthyMuppetInnuendo]

Is there any way to get Apple to change their decision to withhold Sierra from machines that obviously are capable of running OS 10.12?

Many of the machines in question are in their “Vintage” stage, which, if I remember correctly, means they’re only supported for repair in California. Whether they SHOULD be is a matter of the current state of the economy (longer life-cycles for products should mean longer support thereof), but I don’t recall Apple ever adding to a compatibility list, even in the beta cycles.

Also, I’ll rephrase my question: Is anyone having trouble installing Sierra AND finding your installer freezes before you can export the log? What are the most common errors with getting it to work?

 

[limpiacristales]

Works perfectly unless you have VirualBox installed in which case you need to delete it.

Hello all, first of all i want to express deep admiration and gratitude to dosdude and foxlet for their efforts.

i have the same problem with a not working integrated isight camera, and i don't have Virtualbox (and never had). Instead, i had Vmware, wich i have deleted in the hope of solving the problem, but i still haven't a working integrated cam (wich it was working before the instalation of sierra on my unsuported macbook pro 5.2, 17" late 2009).

As it was necessary, i migrated from Snow Leopard, through El Capitan, to Sierra (following all the steps and patches). I did it in a row, so i don't know if the cam was working during the few minutes El Capitan was instaled, so MAYBE it has any relation with something explained on the following site (written for El Capitan):
http://www.insanelymac.com/forum/topic/306777-guide-usb-fix-el-capitan-1011/

Unfortunately, i don't have the knowledge to understand where is the cause for this issue, and i don´t know if there will be further issues to come.

I had to install El Capitan because of the incompatibility of my beloved Snow Leopard and new iOS 10 (and those to come), and now that i have tasted it, for me, it is very convenient to have Sierra because of the copy-paste integration through the i-devices, and the dictation. But i am wondering if there would be better to go back and install El Capitan.

ok, ok, i don't want to nag...

Dosdude, Foxlet, (Anyone!) can help us??

 

[Sedulous]

Hello all, first of all i want to express deep admiration and gratitude to dosdude and foxlet for their efforts.

i have the same problem with a not working integrated isight camera, and i don't have Virtualbox (and never had). Instead, i had Vmware, wich i have deleted in the hope of solving the problem, but i still haven't a working integrated cam (wich it was working before the instalation of sierra on my unsuported macbook pro 5.2, 17" late 2009).

As it was necessary, i migrated from Snow Leopard, through El Capitan, to Sierra (following all the steps and patches). I did it in a row, so i don't know if the cam was working during the few minutes El Capitan was instaled, so MAYBE it has any relation with something explained on the following site (written for El Capitan):
http://www.insanelymac.com/forum/topic/306777-guide-usb-fix-el-capitan-1011/

Unfortunately, i don't have the knowledge to understand where is the cause for this issue, and i don´t know if there will be further issues to come.

I had to install El Capitan because of the incompatibility of my beloved Snow Leopard and new iOS 10 (and those to come), and now that i have tasted it, for me, it is very convenient to have Sierra because of the copy-paste integration through the i-devices, and the dictation. But i am wondering if there would be better to go back and install El Capitan.

ok, ok, i don't want to nag...

Dosdude, Foxlet, (Anyone!) can help us??

I have had no serious issues with the same machine x2 (although I did a clean install [only issue is installer does not create recovery partition]). Are you certain the iSight was working before upgrading? Is it even detected by System Information? It is unlikely the iSight cable connection to the logic board came loose because there is a small black plastic block that holds connection in place.
[doublepost=1477547299][/doublepost]

Many of the machines in question are in their “Vintage” stage, which, if I remember correctly, means they’re only supported for repair in California. Whether they SHOULD be is a matter of the current state of the economy (longer life-cycles for products should mean longer support thereof), but I don’t recall Apple ever adding to a compatibility list, even in the beta cycles.

Also, I’ll rephrase my question: Is anyone having trouble installing Sierra AND finding your installer freezes before you can export the log? What are the most common errors with getting it to work?

But why intentionally prevent capable machines from running the OS? That just contributes to OS fragmentation. Most people aren't going to buy a new machine just to get the newest OS. Apple still releases security updates for previous OS releases so obviously they still have to do the testing. If anything, it makes Apple look bad and pushes customers to hacked options.

No problems with patched installer other than 1: Occassionally it gets stuck on language chooser and 2: Refuses to create recovery drive.