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
It can't currently. The GM is only available to the Dev's via a new redemption code. Hopefully we'll see it released to the public beta testers, but no-one knows yet.Will we see Dosdude's tool supporting Sierra GM today?
You could always install it and make the modifications manually, but everyone in this thread seems to have gotten lazy in that regard.Will we see Dosdude's tool supporting Sierra GM today?
I'm adding a new "advanced" feature to disable app verification, so if someone were to use it with the GM, it'd allow the user to use it even though it isn't fully recognized by the tool.You could always install it and make the modifications manually, but everyone in this thread seems to have gotten lazy in that regard.
I've got the GM release sitting here. I can install it manually (and have written a guide to do exactly that), but happy to test your tool instead.
Currently adding some error handling, but here's a "pre-release". Just go to Options>Skip App Verification in the Menu bar before browsing for an installer app. Final build will be uploaded to the regular directory probably tomorrow at some point. http://dosdude1.com/sierra/spbeta/macOS Sierra Patcher.zip
Well, I got the mCard 2, but, had I known that there's actually 3 antennae in the MacBookPro4,1(2008), I would have ordered the mCard 3.
I'm quite happy with the performance on 2 antennae though - I've connected as fast as 850Mb (3 antennae will get you up to 1.3Gbps).
Since you have the GM, could you open the installer app's Contents folder and send me Info.plist? I need it to add proper identification to my tool.
Using 4.0 of Patcher. Have GM. Tool installs just fine on to USB but when I go to install it says "This version of 10.12 cannot be installed on this computer." and all my disks are greyed out. Mac Pro 3,1 currently running early Dev Prev 16A201W just fine. Will your upload of the tool tomorrow address this issue or am I missing anything?
That's been a known (and solved) issue since PB3.
[doublepost=1473319789][/doublepost]The GM packages seem friendly enough for the alternate update catalog server, under internal testing. Interesting tidbit.
I see, however did it my way before I read your answer. Here it is:
Patch File /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller
with this bsdiff file - https://cloud.mail.ru/public/GJg1/okyuZwrTg (just a patchfile, doesn't contain OSInstaller file), bspatch can be installed with brew - brew install bsdiff
bspatch /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller_patched ./patchfile
mv /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller_patched /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller
codesign -f -s - /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller
Now it happily accepts edited OSInstall.mpkg
Patch File /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller
with this bsdiff file - https://cloud.mail.ru/public/GJg1/okyuZwrTg (just a patchfile, doesn't contain OSInstaller file), bspatch can be installed with brew - brew install bsdiff
bspatch /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller_patched ./patchfile
mv /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller_patched /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller
codesign -f -s - /System/Library/PrivateFrameworks/OSInstaller.framework/Versions/A/OSInstaller
Now it happily accepts edited OSInstall.mpkg
Question #1:
I already have Public Beta 7 installed on my early 2009 iMac, using dosdude1's tools -- a belated "thank you" for that, sir.
I acquired the full 4.78 GB Sierra GM installer from another source, and not via dosdude1's tool and the Mac App Store.
Can I just run the full GM installer, or will I run into some kind of problem?
The reason why I ask, is because in earlier comments, dosdude1 mentioned that he was in the process of updating the macOS Sierra Patcher Tool. There was also a comment by him regarding a new option in the patcher tool called "Skip App Verification".
I just don't want to run the GM installer on my machine, if there is something else that needs to be done first.
Question #2:
Please correct me if I am wrong, but the macOS Sierra Patcher Tool only needs to be run once, correct? In other words, once macOS Sierra is actually installed on your machine's hard drive, from that point forward, one only needs to use the macOS Sierra Software Update Patch Tool, correct? At least that is what I have been doing since Public Beta 1.
The reason why I ask, is because I got the impression -- perhaps mistakenly so -- that being as this is the full GM installer -- as opposed to just a beta update -- we might have to go through the whole install process again, beginning with the macOS Sierra Patcher Tool.
I'd rather play it safe, than be sorry, by asking about this, just in case.
If what I have stated about the macOS Sierra Patcher Tool having to only be run once, I think it would be good to add this important point to dosdude1's instruction page, so that it is made even clearer to folks like me who are not newbies at such things, but who yet also don't have the expertise that others here possess.
Thanks for listening, and thanks again for the tools to keep our older machines up-to-date.
I already have Public Beta 7 installed on my early 2009 iMac, using dosdude1's tools -- a belated "thank you" for that, sir.
I acquired the full 4.78 GB Sierra GM installer from another source, and not via dosdude1's tool and the Mac App Store.
Can I just run the full GM installer, or will I run into some kind of problem?
The reason why I ask, is because in earlier comments, dosdude1 mentioned that he was in the process of updating the macOS Sierra Patcher Tool. There was also a comment by him regarding a new option in the patcher tool called "Skip App Verification".
I just don't want to run the GM installer on my machine, if there is something else that needs to be done first.
Question #2:
Please correct me if I am wrong, but the macOS Sierra Patcher Tool only needs to be run once, correct? In other words, once macOS Sierra is actually installed on your machine's hard drive, from that point forward, one only needs to use the macOS Sierra Software Update Patch Tool, correct? At least that is what I have been doing since Public Beta 1.
The reason why I ask, is because I got the impression -- perhaps mistakenly so -- that being as this is the full GM installer -- as opposed to just a beta update -- we might have to go through the whole install process again, beginning with the macOS Sierra Patcher Tool.
I'd rather play it safe, than be sorry, by asking about this, just in case.
If what I have stated about the macOS Sierra Patcher Tool having to only be run once, I think it would be good to add this important point to dosdude1's instruction page, so that it is made even clearer to folks like me who are not newbies at such things, but who yet also don't have the expertise that others here possess.
Thanks for listening, and thanks again for the tools to keep our older machines up-to-date.
It's detecting the Beta installation and not allowing you to install on that drive. You need to nuke your beta installation (I just erased the drive myself). Installing it now using @dosdude1's tool.
It's detecting the Beta installation and not allowing you to install on that drive. You need to nuke your beta installation (I just erased the drive myself). Installing it now using @dosdude1's tool.
fischersd, are you confirming my suspicion that even if we already have a Public Beta installed on our machine, being as this is the full GM, we have to start all over again with the macOS Sierra Patcher Tool?
If that is the case, then I am going to have to erase an external partition again, install the GM there, and then use CCC to clone it to my internal hard drive, as I did the first time with Public Beta 1.
Thanks.
Ok, my opinion, you should use the Sierra Patcher that dosdude1 patched to give us the option to disable app verification (so it'll work with the GM installer) to create your USB installer (just like we did originally for PB1)
Looking like you can't install over the beta, so you need to do a fresh install (you can use disk utilities on the USB installer to erase the partition if that's an option for you).
After you install, you boot again from the USB and run the post-install patcher (that disabled the tests that Sierra runs that would invalidate our hardware).
[doublepost=1473341811][/doublepost]
Yep. (I was already typing that when you replied)
Edit: You're welcome to try it - pretty sure it's just going to kick you out - either it won't update the OS, or it'll do a hardware check and our systems are on the blacklist it has in its files (which, you'll need to patch anyways after installation, using the USB installer, to eliminate those checks).
I really don't think you can harm anything by trying it and seeing how far you get.
Last edited:
Ok, my opinion, you should use the Sierra Patcher that dosdude1 patched to give us the option to disable app verification (so it'll work with the GM installer) to create your USB installer (just like we did originally for PB1)
Looking like you can't install over the beta, so you need to do a fresh install (you can use disk utilities on the USB installer to erase the partition if that's an option for you).
After you install, you boot again from the USB and run the post-install patcher (that disabled the tests that Sierra runs that would invalidate our hardware).
[doublepost=1473341811][/doublepost]
Yep. (I was already typing that when you replied)
Ha! Looks like we crossed wires there a bit!
Anyway, oh dread! There goes a major chunk of my morning. Well, at least I am performing my daily internal drive backups right now, so that I am insulated from any unexpected surprises once I do begin this lengthy process . . . again.