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.
I'm amazed as my MacBook Pro 2009 runs macOS Sierra very well (with 8GB RAM and SSD), it looks better than El Capitan that is officially supported. I wonder if there is a justifiable reason for Apple remove the official support for this model, not just to force people to buy a new Mac.
So how did you go about updating to PB6, it is not showing in my App Store and I don't see the latest update patcher available, I'm on PB5 at the moment.
 
Now getting "Can't load data from the Apple Software Update server." when I try to run "sudo softwareupdate --list".

Erk
 
The patch tool has been updated, so you should be able to use that to patch PB6. http://dosdude1.com/sierraswupatch - If you need to re-download.
Thank you for the link.
Downloaded and unfortunately I am getting no further, keeps on telling me the update doesn't exist

Screen Shot 2016-08-23 at 07.36.54.png
 
Now getting "Can't load data from the Apple Software Update server." when I try to run "sudo softwareupdate --list".

Erk
Ooh. Maybe you've been trying too hard and they temporarily blacklisted you? Hopefully you haven't been hammering them since you wrote that. :). (me, I would have rebooted and tried again...maybe after about an hour delay?). :)
[doublepost=1471950307][/doublepost]
Thank you for the link.
Downloaded and unfortunately I am getting no further, keeps on telling me the update doesn't exist
So, what have you done in terms of troubleshooting?
*hint*. The message above the last one you posted was actually something you could have tried.
One page back, I posted where the .dist file is. /private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/s/031-72720
If you have that folder, then there's a .dist file for dosdude1's tool to patch. If you don't, then the software updater hasn't properly done an update.
If you monitor the folder
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager when you do a software update, you'll see when it adds updates, as you'll have folders with the current date and time when they're snatched.
Until there's a software update for dosdude1's tool to patch, you're waiting for an update from Apple's servers.
 
Ta for replying.
Unfortunately there is no folder 031-72720. The dates of other .dist files in folder 's' have changed to todays date
so the software updater tool is doing something but not introducing the 0131-72720. Previous versions of the software updater from dosdude1s have worked.
Until there's a software update for dosdude1's tool to patch, you're waiting for an update from Apple's servers.
I am not entirely sure what you mean by that sentence.
The software updater tool is to allow me to install PB6, which is available.
 
Ta for replying.
Unfortunately there is no folder 031-72720. The dates of other .dist files in folder 's' have changed to todays date
so the software updater tool is doing something but not introducing the 0131-72720. Previous versions of the software updater from dosdude1s have worked.
I am not entirely sure what you mean by that sentence.
The software updater tool is to allow me to install PB6, which is available.
*sigh*. "You can lead a horse to water....."

The post above yours that I referenced...the one by dlfgma?

He's doing the command line version of what the Updates tab does in the App Store (you know, the software update mechanism built into MacOS?). Which is what dosdude1's tool is doing in the background when you click on "refresh updates"

It could be possible that your software update manager (again, this is the AppStore I'm talking about) is messed up. Try booting into safe mode, then boot back into regular mode and see if the update shows up.
 
So finally got the software update patch to 'patch' the folder 031-72720 is in the folder 's'
but the App Store refuses to offer any updates.
Terminal also says there is no software available.

Strangely trying to start in Safe mode comes up with the 'no entry symbol'
but yet the machine will boot up quite happily in normal mode.
Hardly been using Sierra since updating to PB5 at the weekend,
been back in the warm embrace of El Capitan.
 
Refresh updates one time, the update should appear. If not, reboot, patch update again, refresh updates ONCE, and check App Store.

Tried that didn't work, still no update showing.
Whats different with this one............
 
[QUOTE="dosdude1, .[/QUOTE]

Updated to PB6 all right for now.

There's only one thing I can not explain ........

I thought I had done something strange when I did the 'upgrade to PB5 using Patch for PB4.

I tried to upgrade to PB6 with the same Patch, just started, select the drop-down menu to choose the version I have been found to PB6 version in the menu ......

How is this possible, automatically updates itself, in practice I do not need the Patch updated by you, and it leaves me somewhat surprised, because as soon as I click on Patch Update or Refresh Update, appears on the AppStore Available immediately upgrade to the selected version .....

sorry dosdude1, the patch works like this or is it something that only happens to me .......

Thank you......
 
I have a 2009 MBP 15" 2.53 Ghz and it too seems to be running really well (8GB RAM and SSD too). Looking at the specs of some of the closely related models that are supported with identical hardware, it doesn't make sense why this model got dropped. I'm amazed that a 7 year Mac, once I dropped an SSD into it, runs so quick and smooth. This is the first computer I've had that I don't see a need to buy anything newer because it does everything I throw at it without delay. It sure is different than "back in the day" where a Mac seemed slow (compared to the new models) after just a year or two.
[doublepost=1471973849][/doublepost]I'm wondering if some users are as confused as I was when trying to use @dosdude1 SW Update Patcher. I originally thought the patcher would update ITSELF when I clicked on "Refresh Updates" and I'd be good to go to patch PB6. But you actually have to re-download his update patcher app every time a new version of Sierra is released, then run that new version.

Even after downloading the updated version of his patch, I still had some issue with it saying the patch was successful, but nothing ever showed up in the App Store. Then I followed his instructions to REBOOT, then run the patch again (ONLY ONCE), and then everything worked flawlessly.

Hope that helps.
 
Has anyone been getting an error with the Feedback Assistant? Since Sunday it has been giving me this whenever I try to submit a new issue:

"Error Sending Feedback. There was an error sending your feedback to Apple. Please go back or use the AppleSeed feedback site to try again."
 
Has anyone been getting an error with the Feedback Assistant? Since Sunday it has been giving me this whenever I try to submit a new issue:

"Error Sending Feedback. There was an error sending your feedback to Apple. Please go back or use the AppleSeed feedback site to try again."
Surely you shouldn't be using feedback assistant on an unsupported machine, your just giving Apple more ammunition to plug the holes in their installation process for all these unsupported machines.
 
Servers have been upgraded and Public Beta 6 (031-72720) is now available through the alternative catalog method at the same URL.
 
Servers have been upgraded and Public Beta 6 (031-72720) is now available through the alternative catalog method at the same URL.
Hi thanks.

Yesterday was unable to download having used the server mentioned in #1802, reverted back to Apple servers and
used software update patch all to no avail.
Today tried the alternative catalog again and have now downloaded and installed PB6.

Thank You.
 
It seems that there has been some confusion about the update process so I wrote a simple tool to help troubleshoot. I'm not sure how useful it will be, but the basic idea is provide the abiiity to check the software catalogs (either Developer Preview or Public Beta) to determine the current OSX 10.12 update dist file and then to check on your install volume to see if the dist file is there.

The tool does NOT patch the dist file (although I am working on that) and does NOT change the access permissions on the software manager (use the Patch tool for that purpose).

Included are a couple of screen shots:

(1) select Catalog and then press CHECK CATALOG button
(2) select Volume and then press CHECK VOLUME button (which will show the local directory)

NOTE: the program remembers the selected values for Catalog and Volume from run to run

I'm not sure how to provide this tool but if anyone is interested in trying it, let me know and will figure out a way to make it accessible.


SierraCheck1.png
SierraCheck2.png
 
It seems that there has been some confusion about the update process so I wrote a simple tool to help troubleshoot. I'm not sure how useful it will be, but the basic idea is provide the abiiity to check the software catalogs (either Developer Preview or Public Beta) to determine the current OSX 10.12 update dist file and then to check on your install volume to see if the dist file is there.

The tool does NOT patch the dist file (although I am working on that) and does NOT change the access permissions on the software manager (use the Patch tool for that purpose).

Included are a couple of screen shots:

(1) select Catalog and then press CHECK CATALOG button
(2) select Volume and then press CHECK VOLUME button (which will show the local directory)

NOTE: the program remembers the selected values for Catalog and Volume from run to run

I'm not sure how to provide this tool but if anyone is interested in trying it, let me know and will figure out a way to make it accessible.


View attachment 646462 View attachment 646463
I've actually written a tool that works similarly to this, that patches the dist file (or, rather, copies a pre-patched dist file from the app bundle's resources). Figuring out a way to get it to actually detect the available update was something I'm working on, currently the update information is stored in a plist, where the user selects the update that needs to be patched. More information and a download can be found here: http://dosdude1.com/sierraswupatch If you want to collaborate, I can share source code with you. It's written in Cocoa/Objective-C.
 
So how did you go about updating to PB6, it is not showing in my App Store and I don't see the latest update patcher available, I'm on PB5 at the moment.

You have to have a supported Mac to download the update, copy it to the Mac that isn't supported, and then run the Public Beta 6 patcher tool. Now I have an Early 2008 iMac running Public Beta 6 and the only things that don't work are the things you would like to have (like a consistent mouse cursor or to b fair built-in speakers-didn't play with the version I first installed so I don't know if it's an unsupported Sierra problem in general or not. Hope this helps ;-)
 
I've actually written a tool that works similarly to this, that patches the dist file (or, rather, copies a pre-patched dist file from the app bundle's resources). Figuring out a way to get it to actually detect the available update was something I'm working on, currently the update information is stored in a plist, where the user selects the update that needs to be patched. More information and a download can be found here: http://dosdude1.com/sierraswupatch If you want to collaborate, I can share source code with you. It's written in Cocoa/Objective-C.

thanks; I'll try to take a look at it later and maybe send you a PM. My program is written in Swift 3 using Xcode beta 6 and is not real sophisticated (probably won't work on non-English machines). When you press the CHECK CATALOG button, it downloads the appropriate Apple catalog gzip and parses it to find the latest OS X 10.12 Update patches, displays that string in the Latest field and then uses it for searching the local volume. So, it will continue to "work" for later versions (although it won't know the DPx or PBy values). It assumes that the .../C/ folder access attributes have been modified so that it can access the sub-folders; if that folder is not writable it will display an error message.

PS - I did make a newer version which will "patch" the .dist file, although currently it saves the edited version on the Desktop rather than writing it back to the catalog sub-folder - this is just for testing.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.