macOS 10.12 Sierra Unsupported Macs Thread

[fischersd]

Man, people just have such an itchy update finger, haha.. I do too, but really only with non-beta releases

Well, I was running betas for Sierra, iOS and WatchOS for this last round as they were major updates and wanted to test them out (but, I also wouldn't come on here and throw a tantrum if something broke...I'd figure it out)
That's what really drives me bat5#!T crazy...when non-technical people throw beta code on their stuff (remember all the whining around the WatchOS 2 beta?) *shudder* - then come on here, give no-where near enough info to help diagnose their problem - heh - and don't read before they post...making multiple threads.
/end rant

 

[Bennoach]

Heh, well, if you're going to be running beta code I hope you're capable of fixing your own problems.

It's all Good. I run IOS beta on my 6 and my Ipad Pro.
I run insider preview on my Surface.
It is part of my job. OSX/MacOS is my weakest. Linux experience helps but, not so much.
I'm just an old SysV guy, trying to keep in the game.

 

[fischersd]

It's all Good. I run IOS beta on my 6 and my Ipad Pro.
I run insider preview on my Surface.
It is part of my job. OSX/MacOS is my weakest. Linux experience helps but, not so much.
I'm just an old SysV guy, trying to keep in the game.

Well, having *nix experience does help a lot....being based on BSD. I spent several years at IBM, so i was an OS/2 and AIX nut for the longest time. Hard to recall all of the flavours over the years (someone did a thread of that recently...decided not to partake...date ourselves too much)

 

[ac2334]

@Howmanyds - if it's still sitting there (now 6 hours later) then methinks there could be an issue either with your USB installer or your target disk - boot in recovery mode and check your disk for errors (repair them if they exist). If no errors, I'd grab a different USB flash drive and remake the installer USB.

@ac2334 - only update after the initial Sierra install was the iTunes update (12.5.1.21). Yes, you should get all of the updates through the AUS patch.

@nitramwin - look in the thread for info on foxlet's AUS patch. That will give you a configuration that allows you to get updates, despite being an unsupported mac. And (2) - Yes, Time Machine works fine.
Edit: I'll save you searching (it's 10 pages back) - https://forums.macrumors.com/thread...ed-macs-thread.1977128/page-121#post-23592364

thank you

 

[Bennoach]

Well, having *nix experience does help a lot....being based on BSD. I spent several years at IBM, so i was an OS/2 and AIX nut for the longest time. Hard to recall all of the flavours over the years (someone did a thread of that recently...decided not to partake...date ourselves too much)

Its running - just needed keyboard input.

Question: To go back to production do I do a full install from my usb?

Thanks again

 

[fischersd]

Its running - just needed keyboard input.

Question: To go back to production do I do a full install from my usb?

Thanks again

To point you back to the production catalog on the AUS server, you should be able to just run the tool again and select the production catalog this time.

As far as getting to the production code from the beta .1 release...in theory the GM you have should be the same as production - if it isn't, hopefully you get the production update showing up via MAS.
(failing that, there will likely be people from the dev side that have links to download the .1 update once it's publicly released).

 

[psu7276]

Folks, just to let everyone know, for the time being, I have abandoned using macOS Sierra on my early 2009 iMac, and I have returned to using the last build of El Capitan.

I won't take up all of your time with the details, but suffice it to say that I had a very nasty experience with the 10.12.1 update this morning which resulted in my keyboard, my Magic Mouse, and even my wired mouse becoming totally inoperable, so that I could not log into my active system.

I tried everything multiple times: resetting the SMC, zapping the PRAM, booting into Recovery Mode, and trying to boot into Safe Mode.

Ultimately, I had to install Mountain Lion on another external partition, and then from there reformat my internal hard drive, and do a clean install of El Capitan.

I have been at this all day working on getting everything back in order, and I am still not done yet, and I am tired.

This old iMac -- almost eight years old -- doesn't have too much time left on it, so I will be sticking with El Capitan until I can afford to purchase a new machine. Everything I have been through with Sierra on this machine just isn't worth the hassle for features which I really don't need, and which I even wouldn't use.

Thanks again to those of you who have worked so hard, and invested so much of your time, to help us get Sierra installed on our machines.

The question is, given the general age of our machines, and the problems and challenges we have had to endure, in order to get it working on our machines, is a Sierra upgrade really worth it? Looking at Apple's list of selling points for Sierra, I have come to the conclusion that at least in my case, the Sierra upgrade has not been worth it. Thus I have abandoned it, and I in fact have a peace about it.

Not only that, but because I performed a clean install of El Capitan, and also stopped using a number of apps and system enhancements, I have noticed a renewed snappiness in my machine, particularly in how fast apps load now. So again, I am pleased.

RumorzGuy

This is my 1st post here. I had the exact same problem/experience that you described. It occurred after trying to upgrade my trackball driver which required a restart. Driver was said to include Sierra. Tried everything to both my main drive and my backup emergency startup drive. Both exhibited the same. Decided to reinstall Sierra on both drives. Did fix the problem on both.

Decided to experiment w/ Siri. Worked for a few minutes and then stopped. Did a restart and the loss of mouse and keyboard occurred again. Erased my backup drive and reinstalled El Cap. via USB drive.
Luckily I made a SuperDuper (1st time) backup of my main drive. I gave up on Time Machine. Took 6 hours to reinstall orig. El. Cap. but now I am good. No idea what the issues were.

 

[coasterOneEightThree]

Just a hint for users in a similar situation. I updated my MacBookPro5,5 (13", Mid 2009), nearly without a problem. The only problem was a non-working Recovery Partition. It was there (checked this in Terminal), but I couldn't boot from it (patched with the tool or not). The SSD in this MacBook Pro was encrypted with FileVault. So I tried the following: I decrypted the SSD completely (switched off FileVault) and installed Sierra again. On post installation I had to activate the Recovery Partition patch manually (it's not checked by default for the MacBookPro5,5). Now I was able to boot from the Recovery Partition (via boot screen or CMD-R). After this it's no problem to encrypt the boot volume again, because this way the Recovery Partition remains functional.

Closing note: If your volume is encrypted with FileVault, you won't see the Recovery Partition on the boot screen. But you are able to boot from it directly with CMD-R right after a reboot.

Hope this helps ...

 

[coasterOneEightThree]

[doublepost=1474900540][/doublepost]
Did you patch the recovery partition? (that's an option on the post-install tool) - it also has to be patched to allow our non-supported systems to work.

Yes, more here:

-> #3283

 

[fischersd]

Yes, more here:

-> #3283

You mean one post up? Yep, there's been a bunch of people that realized that the Sierra installer had issues with encrypted drives. It really shouldn't be that way, but it has been (something Apple should have fixed before the beta testing was complete).

 

[Bennoach]

To point you back to the production catalog on the AUS server, you should be able to just run the tool again and select the production catalog this time.

As far as getting to the production code from the beta .1 release...in theory the GM you have should be the same as production - if it isn't, hopefully you get the production update showing up via MAS.
(failing that, there will likely be people from the dev side that have links to download the .1 update once it's publicly released).

Well I played with it enough to blow it up. I tried a usb boot update in place over the beta. Ended up with a grey circle with a line through it. It would not let me boot anything. I am getting a crash course in what not to do in MacOS. ;-)

I booted off my Snow Leopard disk. I used the installers disk utility and formatted the drive. It would then let me boot the usb stick. Reinstalled 10.12 followed all the instructions then loaded AUS and set to production, said lesson learned and stopped screwing with it.

 

[fischersd]

Well I played with it enough to blow it up. I tried a usb boot update in place over the beta. Ended up with a grey circle with a line through it. It would not let me boot anything. I am getting a crash course in what not to do in MacOS. ;-)

I booted off my Snow Leopard disk. I used the installers disk utility and formatted the drive. It would then let me boot the usb stick. Reinstalled 10.12 followed all the instructions then loaded AUS and set to production, said lesson learned and stopped screwing with it.

Ugh! You still should have been able to boot from the USB (just hold the Option/Alt key on boot-up).

In case you don't have it bookmarked, the key combinations can be found here: https://support.apple.com/en-ca/HT201255

The forbidden sign means that the install hasn't been patched - you could have booted from dosdude1's USB installer and ran the post-install utility to patch it.

 

[Bennoach]

Ugh! You still should have been able to boot from the USB (just hold the Option/Alt key on boot-up).

In case you don't have it bookmarked, the key combinations can be found here: https://support.apple.com/en-ca/HT201255

The forbidden sign means that the install hasn't been patched - you could have booted from dosdude1's USB installer and ran the post-install utility to patch it.

I held done option key and selected the usb but it would come back to the circle of death.
Not a problem.
Thanks for the link I was hoping to find them.
I need a good book on MacOS command line etc.

 

[Pinarek]

This time there was no Problem with the update Beta 3 for 10.12.1 on my Macmini3,1
Without changing the AUS-Tool.

 

[foxlet]

This time there was no Problem with the update Beta 3 for 10.12.1 on my Macmini3,1
Without changing the AUS-Tool.

You shouldn't have to change the catalog in AUS except to reset back to Apple's catalog, it's set once and SoftwareUpdate handles the rest.

 

[Pinarek]

foxlet.. Yes you are totally right.

 

[pkouame]

Well, having *nix experience does help a lot....being based on BSD. I spent several years at IBM, so i was an OS/2 and AIX nut for the longest time. Hard to recall all of the flavours over the years (someone did a thread of that recently...decided not to partake...date ourselves too much)

Old nix guy here too! We are not alone...how about Eunice on VAX VMS...
[doublepost=1475629382][/doublepost]

You shouldn't have to change the catalog in AUS except to reset back to Apple's catalog, it's set once and SoftwareUpdate handles the rest.

Yes beta updates are pretty smooth on my end.
Rumor has it 10.12.1 is slated to coincide with the announcement of new book pros. Sadly no Kaby Lake in sight, falling behind again...

 

[vynu]

any one having problems with camera ? {macbook 5,1 late 2008 aluminum}

 

[axd1152]

any one having problems with camera ? {macbook 5,1 late 2008 aluminum}

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

 

[pkouame]

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

Same here. VB doesn't play well with shared iSight. There are 4 kexts that are culprits. Only uninstalling VB resolves the problem. Still don't know if it's just us or a more general Sierra issue.

 

[Ultracyclist]

Last piece of my Mac mini 3,1 Siërra puzzel

 

[Bennoach]

View attachment 663077

Last piece of my Mac mini 3,1 Siërra

I just ordered on of these. Any tips on mounting it - double stick tape maybe?

 

[Ultracyclist]

I just ordered on of these. Any tips on mounting it - double stick tape maybe?

No, I'll get to that when I'm putting it in.

 

[fischersd]

Old nix guy here too! We are not alone...how about Eunice on VAX VMS...
[doublepost=1475629382][/doublepost]
Yes beta updates are pretty smooth on my end.
Rumor has it 10.12.1 is slated to coincide with the announcement of new book pros. Sadly no Kaby Lake in sight, falling behind again...

Heh...yep, spent some time on VAX as well...funny thing, the same place still had a Burroughs!! Yep, that's right - doing batch jobs with punch cards (was bewildered that they still had that dinosaur)
[doublepost=1475673792][/doublepost]

No, I'll get to that when I'm putting it in.

Amazingly enough, had one of these at my place the last couple of days (buddy got it cheap ($69) from one of the school boards - giving it to another friend to use as an HTPC). We didn't put Sierra on it though....dude isn't technical, so I didn't swap out the NIC - don't want another friend to support.

If I were you guys, I'd find some flat plastic - preferably about 1/8" thick - use the existing card to make a template and then screw the new card to the template. (heard someone did this already....somewhere on here) - seems like an ideal solution. Hell, even an old expired credit card may work, trimmed down.

 

[longjohnsjon]

the public release and gold master are the same version.

if you try to use just dosdudes patch and run the installer from the usb thumb stick it will come back with the error that no packages where found for this model of Macintosh try it.

it does display this message and its because the beta was missing information where the gold master has some new security and yes the great thing is that dosdudes Mac OS X Sierra tool works to create media as well as creating a patch usb stick to patch the o.s every time the App Store version and the gm are the same revision number.

Hi guys,

I just installed a new hard drive on my MacBook Pro 5,5 and thought this was a good moment to install the GM version of macOS Sierra. I had installed the Public Beta versions on this MacBook Pro before, using dosdude's patcher (and update patcher) but now with the GM version (I had downloaded the GM on my iMac that is supported and am working with that very installation file, so I am just going to continue calling it the GM version) and the completely empty drive, I run into the same problem as mrdunderhead describes.

I also tried installing it from the iMac with the MacBook Pro connected in target disk mode but for some reason the iMac started re-downloading macOS. I haven't let it finish the download yet since I can't use the clean, downloaded installer.

Any ideas?

UPDATE 1:

In my desperation to get the MacBook Pro working again, I tried to install OS X El Capitan to then restore from my backup. I get the same error message as when I try to install a patched macOS Sierra: "No packages were eligible for install."

So this error has nothing to do with the Sierra Patcher or macOS Sierra.

UPDATE 2:

Realizing this had nothing to do with the Sierra Patcher, I found a solution for the error online:

The date of my computer was reset to 01.01.2001 and needed to be set manually from Terminal. After that, the patched macOS installer worked flawlessly.

See
https://tinyapps.org/blog/mac/201510140700_el_capitan_install_error.html
http://www.istrategy.com.au/knowledge-base/unable-install-el-capitan-no-packages-eligible-install/#