Someone recheck this on dp3 please
Have you enough time to check ALS kexts? How you check it? Disassembler?
Someone recheck this on dp3 please
Thanks, dosdude!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.
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.
not all heroes wear capes.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.
Sounds good. Could you activate the wireless lan of your MBP?
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.
No, it should not conflict with dosdude1's updated patcher. You should be fine.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
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.
No, it should not conflict with dosdude1's updated patcher. You should be fine.
Thanks, what files and where do they install to with your App Store catalogue patch?
That is correct.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?
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
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.
Use Finder, then from the top menu click on Go -> Got to Folder.can i know how can i locate the folder : /private/var/folders/
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
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146
- 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:
(note that the folders C and softwareupdated are locked and you have to give them read/write access)
sysctl hw.model | awk '{ print $2 }'
- 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:
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)
sudo softwareupdate --list
- Next step is to use Terminal to trigger the update to appear. In the terminal use the command:
Method 2 - Login at the Apple Store after install of macOS Sierra PB1
- 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.
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146
- 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:
(note that the folders C and softwareupdated are locked and you have to give them read/write access)
sysctl hw.model | awk '{ print $2 }'
- 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:
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)
sudo softwareupdate --list
- Next step is to use Terminal to trigger the update to appear. In the terminal use the command:
[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
- 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.
![]()
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
I hear you. My pro 3,1 is still solid. What wifi card did you get?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.