That would be awesome, so that we can get a more clear look of what exactly is doing the trick. Did you also manually edit the two files mentioned in post 1418? -> https://forums.macrumors.com/thread...ted-macs-thread.1977128/page-57#post-23146117
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.12 Sierra Unsupported Macs Thread
- Thread starter redheeler
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
That would be awesome, so that we can get a more clear look of what exactly is doing the trick. Did you also manually edit the two files mentioned in post 1418? -> https://forums.macrumors.com/thread...ted-macs-thread.1977128/page-57#post-23146117
I keep an installer USB stick of El Capitan around. Main reason is my Mini has a DIY Fusion that I did not preserve the recovery drive on. In hind site I could have but well, didn't. So when I need disk utility or terminal to turn SIP on/off I have it around to boot.
My setup in general is basic. All of my important files are in the cloud and my apps are few and available for re download. So, a rebuild from start to finish is less than 45 minutes on average. This is why I take the chance to play with these patches and this newer software.
Wuuhuu - I managed to update from PB 1 to PB 2 without even downloading or running the 4 files mentioned earlier. Everything that needs to be done is to edit this file:
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146.da.dist
(.da.dist because my Mac is set to Danish). Note that the folders are locked so you need to give them read+write access.
In the file you delete your Mac model from the not supported paragraph as well as adding your board ID to the supported paragraph. That's it. You can find your board ID with this terminal command:
sysctl hw.model | awk '{ print $2 }'
ioreg -l | awk -F\" '/board-id/ { print $4 }'
Afterwards I tried both to check for software updates through the app-store, and through terminal with the: sudo softwareupdate --list command and restarted a couple of times and suddenly the update was showing in the App Store and flawlessly updated my Mac.
It's late here now, so I'm trying to figure out the correct order tomorrow, but I just wanted to let you guys know that it is not necessary at all to go download the .pkg files manually or run them.
/private/var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/softwareupdated/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146.da.dist
(.da.dist because my Mac is set to Danish). Note that the folders are locked so you need to give them read+write access.
In the file you delete your Mac model from the not supported paragraph as well as adding your board ID to the supported paragraph. That's it. You can find your board ID with this terminal command:
sysctl hw.model | awk '{ print $2 }'
ioreg -l | awk -F\" '/board-id/ { print $4 }'
Afterwards I tried both to check for software updates through the app-store, and through terminal with the: sudo softwareupdate --list command and restarted a couple of times and suddenly the update was showing in the App Store and flawlessly updated my Mac.
It's late here now, so I'm trying to figure out the correct order tomorrow, but I just wanted to let you guys know that it is not necessary at all to go download the .pkg files manually or run them.
Attachments
Last edited:
Instructions (thanks to various people)
What's weird is that PB2 is still showing up as an update even though I have have it installed. Anyone else see this?
On a separate note, my keyboard issue seems to have fixed itself.
- sudo /usr/sbin/softwareupdate --set-catalog https://swscan.apple.com/content/ca...ion-snowleopard-leopard.merged-1.sucatalog.gz
- sudo vi /var/folders/zz/zyxvpxvq6csfxvn_n00000s0000068/C/com.apple.SoftwareUpdate.SUCatalogDataManager/r/031-68146/031-68146*dist (this will vary based on language)
add boardid to boardIds array, ( ioreg -l | awk -F\" '/board-id/ { print $4 }' )remove Mac model from nonSupportedModels array, ( sysctl hw.model | awk '{ print $2 }' )- change "return false" to "return true", see #1526
- quit App Store if running
- sudo softwareupdate --list (repeat as necessary)
boot from usb using dosdude1 tool and reapply post install patch (if necessary)
What's weird is that PB2 is still showing up as an update even though I have have it installed. Anyone else see this?
On a separate note, my keyboard issue seems to have fixed itself.
Last edited:
I really appreciate the work and effort put into this. I tried step by step the instructions listed above but unfortunately it does not work for me either. I was able to find the dist file and modify it per instructions. Could there be a missing step?
First a big Thank You to everyone, especially @dosdude1 and @parrotgeek1, for all their hard work and help in this forum. I am excited to report that not only was I able to get DP3 successfully installed on my MacPro 3,1 (Early 2008), but with my modified BCM94360CD wifi+BT4 module installed, both Wifi and all Continuity features are fully operational at this time! (Including Apple Watch unlock).
To do this, I did have to use the external USB drive method from @parrotgeek1's post, and install Sierra using a supported mac first (including running the DP3 delta update after initial install). After the DP3 update, I re-ran @parrotgeek1's script and copied back the modified PlatformSupport.plist from the original post.
To do this, I did have to use the external USB drive method from @parrotgeek1's post, and install Sierra using a supported mac first (including running the DP3 delta update after initial install). After the DP3 update, I re-ran @parrotgeek1's script and copied back the modified PlatformSupport.plist from the original post.
I've just finished working on the Recovery Partition Patch for the macOS Sierra Patcher. I've updated the download, and changed the version number to 3.0. As of now, the contents of the recovery partition haven't been edited, however in the future I plan on adding the post install patch as an option in the main menu. As with all newly added features, there may be some bugs, so please test and let me know. Download here: http://dosdude1.com/sierra/macOS Sierra Patcher.zip
Attachments
Where can I download PB2 or DP3???
I have rey to upload from PB1 but don't work, and I see is more easy reinstall than update.
I have rey to upload from PB1 but don't work, and I see is more easy reinstall than update.
I can confirm that these instructions work flawlessly!!! Because I am newbie at these things and even I did it. I was able to update and install Public beta 2 directly from the Mac Appstore on my unsupported Macbook pro 17 mid 2009! I didn't even have to run dosdude1's patch after. However I'm experiencing the same issue, the update installed successfully but it's still showing up on the App Store to install...
So just a heads up, I made a copy of the original file and saved it, so now after I installed the update I placed back the original file so on the Mac appstore would not show the symbol for updates....
Im guessing somewhere around all those things we changed from false to true, there might be something that should stay false LOL but that's just me guessing.
Still awesome works you guys!!! I mean with just a little tweaking this is almost perfect!
Last edited:
I tried it again and modified the file per instruction. Seems that every time I run the the "softwareupdate --list" command, the folder where the dist is reverts back to its original version. Has anyone else experienced the same issue? In addition wanted to confirm "031-68146.English.dist" for systems in English? Isn't that odd considering that we've seen Portuguese and Danish ones as "031-68146.pt/da.dist"?
Are you sure when you edit the file it actually saves the alterations that you have made? Make a copy of the 031-68146 file to your desktop, use an app called textwrangler to edit it and save it on your desktop, now save the original file somewhere safe and replace the file! Hope it helps
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:
(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:
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:
- 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.
- 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)
- 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)
- Next step is to use Terminal to trigger the update to appear. In the terminal use the command:
- 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.
Attachments
I was able to install it successfully! I think it was the SIP that was reverting the file back. I followed the instructions in a previous post to setup the recovery partition. Once I disabled the SIP and followed the instructions, the update showed up and went smoothly.
[Quote = "dosdude1, posta: 23.150.968, membro: 669.685"] Ho appena finito di lavorare sul Patch Partition Recovery per il MacOS Sierra Patcher. Ho aggiornato il download, e ha cambiato il numero di versione alla 3.0. A partire da ora, il contenuto della partizione di ripristino non sono stati modificati, ma in futuro ho intenzione di aggiungere post installazione delle patch come opzione nel menu principale. Come per tutte le nuove funzioni aggiuntive, ci possono essere alcuni bug, quindi per favore prova e fammi sapere. Scarica qui: http://dosdude1.com/sierra/macOS Sierra Patcher.zip [/ quote]
Molte grazie da Italia per il tuo lavoro.
Molte grazie da Italia per il tuo lavoro.
Last edited:
Hello Every one,
I have installed Sierra patched by @dosdude1 on macbook5,1 unibody late 2008. System works great by I can't update pb1 to pb2. Everyone tutorial doesn't work for me. My apps store update does not show updates. Please help or something suggestion. My language system is polish, I don't know whether does it matter.
I have installed Sierra patched by @dosdude1 on macbook5,1 unibody late 2008. System works great by I can't update pb1 to pb2. Everyone tutorial doesn't work for me. My apps store update does not show updates. Please help or something suggestion. My language system is polish, I don't know whether does it matter.
I have the same problem with my MacBook late 2008.
Tutorial is with the same MacBook 5.1, so this night will go to try other time. Don't be so hard to get update PB1 to PB2.
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.
What is complete command for sudo ( full path pls )
Anyone who has the problem with really loud sound on iMac7,1 (or others, but tell me which computer you have)
Please send me the el Capitan and Sierra applehda kexts so I can compare them, thanks
Please send me the el Capitan and Sierra applehda kexts so I can compare them, thanks
Sent via PM. iMac7,1 here. Only thing is I haven't upgraded to PB2/DP3 yet, I have to do that and see if that made a difference.
Can someone please help me with adding my board-id.
I've used the terminal command to find my board-id which is "Mac-F42D86C8". My question is where do I add my board-id in the following text string in the file 031-68146.English.dist?
var boardId = system.ioregistry.fromPath('IOService:/')['board-id'];
if (boardIds.indexOf(boardId) == -1) {
my.result.message = system.localizedString('ERROR_1');
my.result.type = 'Fatal';
return false;
Thanks in advance.
I've used the terminal command to find my board-id which is "Mac-F42D86C8". My question is where do I add my board-id in the following text string in the file 031-68146.English.dist?
var boardId = system.ioregistry.fromPath('IOService:/')['board-id'];
if (boardIds.indexOf(boardId) == -1) {
my.result.message = system.localizedString('ERROR_1');
my.result.type = 'Fatal';
return false;
Thanks in advance.
Just change the line "if (boardIds.indexOf(boardId) == -1)" to "if (1==0)" (so it will never be true). That should bypass the board-ID check.