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.
So Update to DP3 finished.

DP1 -> PB1 -> PB2 -> DP3 all done without patching after the Update (MB5.1)

DP3 is 031-68147 and the folder is on /private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/k/031-68147
After switching the catalog to seed.


Anyone else having Problems with .m3u8 streams on safari? Getting a missing plugin error.
 
Last edited:
  • Like
Reactions: therawapple
The update was successful. MB5,1 late 2008 pb1 to pb2. I should use first macOS Software Update Patch and next earlier instructions file copy. My update shows after copy folder 031-68146 to "D" /private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/d/031-68146.

Tell me whether pb2 should be auto unlock?? because they still don't have the option in the Security & Privacy.
Io10beta3,watchos3 and enabled 2FA. Any ideas?
 
I've just done a bit of an overhaul to the user interface of the macOS Sierra Patcher, I think it looks a whole lot better. Also, I'm in the process of creating an easy-to-use software update patch, to allow users to update to newer Sierra releases on unsupported machines without issue.
 

Attachments

  • Screen Shot 2016-07-25 at 1.45.12 AM.png
    Screen Shot 2016-07-25 at 1.45.12 AM.png
    116.8 KB · Views: 326
I've just done a bit of an overhaul to the user interface of the macOS Sierra Patcher, I think it looks a whole lot better. Also, I'm in the process of creating an easy-to-use software update patch, to allow users to update to newer Sierra releases on unsupported machines without issue.
Thanks, dosdude!

I can't wait for the new version!
 
Wow - that looks FANtastic!
Thanks so much for ALL you have done to help us out!

I've just done a bit of an overhaul to the user interface of the macOS Sierra Patcher, I think it looks a whole lot better. Also, I'm in the process of creating an easy-to-use software update patch, to allow users to update to newer Sierra releases on unsupported machines without issue.
 
thanks for the detailed information!

My question is if I am using the DP version rather than PB, how would the instructions be different? Is it just a matter of using a directory other than 031-68146? (I assume that the process would need to be done twice: once to go from DP1 to DP2 and a second time to go from DP2 to DP3)

And is it necessary to run the post-install patch tool after update?

thanks for any responses.

Same here!
 
I've just done a bit of an overhaul to the user interface of the macOS Sierra Patcher, I think it looks a whole lot better. Also, I'm in the process of creating an easy-to-use software update patch, to allow users to update to newer Sierra releases on unsupported machines without issue.
not all heroes wear capes.
 
Make sure you're actually going to get the OTA updates. Run my macOS Update Patcher with the Developer Beta CatalogURL checked and Software Update patch unchecked.
Whenever any updates come for 10.12, follow @dosdude1's instructions to keep the kexts running.

Hi all,

I installed the public beta 1 on a late 2008 MacBook from the mega link in dosdudes post on youtube, all running just fine. I tried this patcher last night and its not working, I read dosdudes post from earlier today so that sounds really cool.

I was wondering what files the patcher I tried installed and where are they installed to? Will they conflict in some kind of way with dosdudes new stuff?

Thanks anyway, brilliant stuff, always good to be on the latest os
 
Hi all,

I installed the public beta 1 on a late 2008 MacBook from the mega link in dosdudes post on youtube, all running just fine. I tried this patcher last night and its not working, I read dosdudes post from earlier today so that sounds really cool.

I was wondering what files the patcher I tried installed and where are they installed to? Will they conflict in some kind of way with dosdudes new stuff?

Thanks anyway, brilliant stuff, always good to be on the latest os
No, it should not conflict with dosdude1's updated patcher. You should be fine.
 
I've just done a bit of an overhaul to the user interface of the macOS Sierra Patcher, I think it looks a whole lot better. Also, I'm in the process of creating an easy-to-use software update patch, to allow users to update to newer Sierra releases on unsupported machines without issue.

Hi - I tried the new patcher to recreate my Sierra install but it appears to not work with the DP version, just the Public Beta - is that correct?
 
Thanks, what files and where do they install to with your App Store catalogue patch?

There may be a plist file in /Library/LaunchDaemons. Other than that, just reopen the patch and return to the previous CatalogURL. If you installed the Public Beta just go back to the Public Beta CatalogURL. There should be no more temp files anywhere if you recently restarted your Mac.
 
  • Like
Reactions: indigotheory
Hey guys,

I've been doing everything exactly as in post 1464, but pb 2 isn't showing up...

What am I doing wrong? I navigated to the right folder, added myself as owner to give the folder read/write permission, edited the file - with text edit - removed my iMac (8,1), added my board... I tried with a restart and without.

But never did pb2 show up. Any help...

Thanks

Dave
 
Hey guys,

I've been doing everything exactly as in post 1464, but pb 2 isn't showing up...

What am I doing wrong? I navigated to the right folder, added myself as owner to give the folder read/write permission, edited the file - with text edit - removed my iMac (8,1), added my board... I tried with a restart and without.

But never did pb2 show up. Any help...

Thanks

Dave


I found dosdude1's advice really helpful. Rather than adding your board. Change the value of "boardid" from "==-1" to "==0" according to him, this overrides the system check of the board Id as a whole, and should solve your issue. Mine worked like a charm after I did it. I did restart my iMac after making the changes. ALSO make sure that the file extension is still .dist the first time I tried it, the extension was changed to .txt
 
So Update to DP3 finished.

DP1 -> PB1 -> PB2 -> DP3 all done without patching after the Update (MB5.1)

DP3 is 031-68147 and the folder is on /private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/k/031-68147
After switching the catalog to seed.


Anyone else having Problems with .m3u8 streams on safari? Getting a missing plugin error.


Having the exact same issue any fix?
 
I've been testing and testing the entire day, and come up with these two bulletproof ways bellow to update from PB1 to PB2 on a fresh install of macOS Sierra PB1 pacthed with @dosdude1 's tool.

First of all I would like to say that there is no reason to change the urls of the software update catalog, and it's also not to change all "return false" with "return true". These things might be why you keep having the update showing up.

Secondly I don't know if it will work on a already used installation where you've tried a lot of things in order to get the update to work, but the guide bellow does work on a fresh clean and patched PB1 install (method 2 might also work for an already running installation). I've confirmed that 5-6 times in a row now, so it should work.

Method 1 - Login at the Apple Store under install of macOS Sierra PB1
  • On first boot allow the Mac to run its stuff after you start the OS for the first time. It will create the folders and files needed in order to update.
  • After this is done the App Store icon in the dock shows that 1 update is ready. This is an update to the recovery tool. Just keep the App Store closed for now. We'll open it later. Also ignore the two notifications about that there is an update and about enabling automatic updates.
  • After this go to this folder:
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146

(note that the folders C and softwareupdated are locked and you have to give them read/write access)
  • In the above folder (031-68146) there is a .dist file. It's named 031-68146.*.dist (the * is the language of your macOS installation). In the file you delete your Mac in the "nonSupportedModels" array. In my case it is the MacBookPro 5,1. You also need to add your board ID in the "boardIds" array. In my case it is Mac-F42D86A9. It is important that you keep the syntax, so make sure that your entries follows the same pattern as the ones allready there. If you don't know your board ID you can find it with the Terminal command:
sysctl hw.model | awk '{ print $2 }'
ioreg -l | awk -F\" '/board-id/ { print $4 }'


(note that the number of files in the folder com.apple.SoftwareUpdate.SUCatalogDataManager shouldn't be increasing when you edit the .dist file as it then might be overwritten later. It apparently taskes a while after software update check before the entire process has completed)
  • Next step is to use Terminal to trigger the update to appear. In the terminal use the command:
sudo softwareupdate --list
  • Notice how 4 files appear after a while in the 031-68146 folder from before (see thumbnail). When the command finishes in Terminal it should list the update to PB2.
  • You can close the Terminal now and open the App Store and update like you normally would have done.
Method 2 - Login at the Apple Store after install of macOS Sierra PB1
  • On first boot of the Mac open the App Store and let it look for updates. It will only find the recovery tool update, and it is perfectly fine for now. The step is necessary as It will create the folders and files needed in order to update.
  • When the check for software updates has finished, you can close the App Store. (Ignore the notification about enabling automatic updates)
  • After this go to this folder:
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146

(note that the folders C and softwareupdated are locked and you have to give them read/write access)
  • In the above folder (031-68146) there is a .dist file. It's named 031-68146.*.dist (the * is the language of your macOS installation). In the file you delete your Mac in the "nonSupportedModels" array. In my case it is the MacBookPro 5,1. You also need to add your board ID in the "boardIds" array. In my case it is Mac-F42D86A9. It is important that you keep the syntax, so make sure that your entries follows the same pattern as the ones allready there. If you don't know your board ID you can find it with the Terminal command:
sysctl hw.model | awk '{ print $2 }'
ioreg -l | awk -F\" '/board-id/ { print $4 }'


(note that the number of files in the folder com.apple.SoftwareUpdate.SUCatalogDataManager shouldn't be increasing when you edit the .dist file as it then might be overwritten later. It apparently taskes a while after software update check before the entire process has completed)
  • Next step is to use Terminal to trigger the update to appear. In the terminal use the command:
sudo softwareupdate --list
  • Notice how 4 files appear after a while in the 031-68146 folder from before (see thumbnail). When the command finishes in Terminal it should list the update to PB2.
  • You can close the Terminal now and open the App Store and update like you normally would have done.
[doublepost=1469196615][/doublepost]@LarrikinAus - how did you find out what the update identifier was for the PB2 update? It would be nice to know so that it is easy for us to update when the PB3 comes out ;)

Thanks for the concise instructions, very helpful. Just want to add my 2 bits for some who may be in the same boat as I am - with a solution:

MY PROBLEM: Not only does PB2 NOT show up in the App Store but my Sierra Patched PB1 from a while ago (old version 2.5?) did NOT contain a .../r/031-68146. Looked for it literally everywhere, but nada! Tried any number of App Store updates, resetting CatalogUrls to seed or beta or even just clearing and restarting combinations. No progress. Then I remembered that my original patch did two things to my system (maybe @dosdude1 has addressed them in the new update) :
1) removed my /System/Library/CoreServices/PlatformSupported.plist and
2) disabled SIP.

SOLUTION: So what the hell,
- I plugged in my source Sierra PB1 OS X Base stick
- located the original PlatformSupported.plist its /System/Library/CoreServices
- Verified that my board ID and system was "supported" per your instructions above.
- copied it back to my /System/Library/CoreServices folder. (Note: With SIP disabled, Sierra just asks for a password, otherwise you'll have to restart to Recovery (or whatever other favorite route you have) and "csrutil disable" - then reboot to perform the copy)
- Restarted Sierra PB1 just for safe measure
- Then App Store -> Updates - still no new DPs or PBs. Not to panic...
- In Terminal software update --list
- Pop! the directory appears (Also Note: that my catalog was set to the 10.12beta.)

Hope this helps someone. Your mileage may vary of course. Wasn't exhaustively tested (didn't want to press my luck too hard...)

QUICK EDIT : I am typing this on PB2 (10.12 Beta (16A254g)). So another successful update! I can confirm again that the Sierra Patched PB1 -> PB2 route works. Kudos @Banan911 and @dosdude1 again!
Now back to testing drivers, new system frameworks and applications. BTW, looks like I may skip DP3 since they have the same build numbers. Yes....Plus got some new MAS updates goodies:

{
CatalogURL = "https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz";
LastAttemptSystemVersion = "10.12 (16A254g)";
LastBackgroundSuccessfulDate = "2016-07-26 09:08:42 +0000";
LastFullSuccessfulDate = "2016-07-26 09:00:23 +0000";
LastRecommendedUpdatesAvailable = 2;
LastResultCode = 0;
LastSessionSuccessful = 1;
LastSuccessfulDate = "2016-07-26 09:17:00 +0000";
LastUpdatesAvailable = 2;
PrimaryLanguages = (
"en-US"
);
RecommendedUpdates = (
{
"Display Name" = iTunes;
"Display Version" = "12.5";
Identifier = iTunesX;
"Product Key" = "zzzz031-67195";
},
{
"Display Name" = "Safari Technology Preview";
"Display Version" = 9;
Identifier = SafariTechPreview;
"Product Key" = "031-67263";
}
);
SkipLocalCDN = 0;
}
 
Last edited:
  • Like
Reactions: Banan911
I found dosdude1's advice really helpful. Rather than adding your board. Change the value of "boardid" from "==-1" to "==0" according to him, this overrides the system check of the board Id as a whole, and should solve your issue. Mine worked like a charm after I did it. I did restart my iMac after making the changes. ALSO make sure that the file extension is still .dist the first time I tried it, the extension was changed to .txt

Thanks! That worked! Installed pb2 flawlessly!
 
I dunno - I have MacPro late 2009 I bought new in 2010.
It just keeps working great, tho I did have to swap the WiFi broadband card for Sierra.
I have 8 drives in and around it now, swapped in an nVidia GTX285 display card, have a USB3 card coming today,upped the memory to 24GB of 1333mHz, and have a new processor board coming with the W3680 3.33 hex Core processor ... I am not into laptops and don't want a Mac Pro waste-can model ... This one is a workhorse, is STILL upgradable, and its a beautifully made piece of kit.
I hear you. My pro 3,1 is still solid. What wifi card did you get?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.