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
i've a problem.
after an error i tried to reinstal sierrra on my macbook pro 5,5 with @dosdude1 tool
but the installer shows me:
Impossibile installare macOS sul computer
nessun pacchetto idoneo per l'installazione
Any suggestion?
Please someone can help me?
I tried 2 different tools and 2 different usb key, but i have the same problem...
Sip is disabled
RESOLVED...it's a problem of date!!
after an error i tried to reinstal sierrra on my macbook pro 5,5 with @dosdude1 tool
but the installer shows me:
Impossibile installare macOS sul computer
nessun pacchetto idoneo per l'installazione
Any suggestion?
Please someone can help me?
I tried 2 different tools and 2 different usb key, but i have the same problem...
Sip is disabled
RESOLVED...it's a problem of date!!
Last edited:
Aren't those headphones? So they wouldn't be listed as an audio source (unless I am not understanding question).
Ok, had to look up to see if these have the W1 chip. They do. I'm guessing that the W1 chip supports both wifi as well as bluetooth and using the former's "time of flight" feature to determine proximity and switching / auto-pairing.
Without changing your airport card on your MBP 5,5 out for a new one that supports 802.11AC, your wifi won't have this feature.
To have them work as regular bluetooth headphones, you need to have them paired under bluetooth before you'll see them appear under audio.
Edit: Scratch that. While they may do some extra-cool things for those that do have 802.11AC cards, that's not required for the auto-pairing via iCloud (a buddy of mine has the AirPods - they auto-paired with his 2012 Mac Mini - which also doesn't have AC).
As long as you have the latest version of Sierra, using the same iCloud / AppleID across all of your devices it should work (might be good to have 2FA - two factor authentication enabled as well - that way your MBP is already authenticated with iCloud).
Last edited:
My MacBook Pro 4,1 17-inch Early 2008 is running MacOS Sierra 10.12.2 thanks to this thread's contributors.
I had been able to run Chrome Remote Desktop until I upgraded to 10.12.2
Without any other new settings or upgrades I can connect from the MacBook Pro to the the remote desktops via LAN or WAN, however, I no longer see the desktop ... a blank screen is displayed ... on the receiving computer it shows that I have connected but nothing more can progress.
Sierra 10.12.2 no longer is compatible with Chrome Remote Desktop for me unless I use another iMac conventionally upgraded to Sierra 10.12.2 and then that machine works normally.
Teamviewer does function remotely.
I cannot fix the incompatibility problem with Chrome Remote Desktop and this latest upgrade to OS 10.12.2
Ideas? Suggestions?
Thanks.
I had been able to run Chrome Remote Desktop until I upgraded to 10.12.2
Without any other new settings or upgrades I can connect from the MacBook Pro to the the remote desktops via LAN or WAN, however, I no longer see the desktop ... a blank screen is displayed ... on the receiving computer it shows that I have connected but nothing more can progress.
Sierra 10.12.2 no longer is compatible with Chrome Remote Desktop for me unless I use another iMac conventionally upgraded to Sierra 10.12.2 and then that machine works normally.
Teamviewer does function remotely.
I cannot fix the incompatibility problem with Chrome Remote Desktop and this latest upgrade to OS 10.12.2
Ideas? Suggestions?
Thanks.
It's not the update...or, at least, it's not the update on all Mac's.
I was able to replicate your issue on my MBP 4,1 (same system).
But, on my MB 5,2 (13" '09) CRD worked fine to control my 2012 mac mini.
What release of MacOS/OSX was this working under on the MBP? (The MB was originally running 10.12.1 and wouldn't run CRD - had to be upgraded to 10.12.2 to work).
[doublepost=1482846338][/doublepost]I know Chrome Remote Desktop worked on El Capitan with my MacBookPro 4,2
I thought it was working with the initial Sierra 10.12.1 but I may be wrong.
Thanks for your reply and any efforts you make to fix the issue....you have been a terrific forum member and help in keep my MacBook Pro 4,2 up to date...I will work around the Chrome Remote Desktop issue by using our iMac in the meantime.
Well, I suspect it may be a graphics driver issue - obviously, by it working on one but not the other, it means that the host system (in my case, my mini) is at least sending the information. The client (the MBP) simply isn't drawing the information it's receiving.
Unfortunately, the last version of the drivers that Nvidia did for this chipset was January of 2015. This should mean, however, that the version of the driver is the same for the last version of El Capitan and Sierra...just that there will be API changes.
Also probable that other chipsets are affected by this. Think I might try some of the El Capitan kexts to see if they make any difference.
Can you install that launch agent into /Library instead of /System/Library and the program into /usr/local/sbin instead? I prefer to avoid these locations, just for transparency. I also experimented with ‘csrutil enable --without kext’ to keep most of the SIP restrictions intact, except kext signing, which means that I could not disable that launch agent myself.
Also, I found that some of the items that are installed still have some extended attributes. For example, PlatformSupport.plist has a quarantine flag. Perhaps you can add a ‘xattr -c’ to the operation whenever you place a file somewhere. The Info.plist file in LegacyUSBInjector.kext is made executable, but should be read-only.
H.264 videos are working with Chrome? (i don't use it, and i don't want to install it). The nVidia GPU is nearly the same (8xxx/9xxx/1xx/2xx/3xx are all based on Tesla), the only thing thats is diffrent is the hardware decoding of H.264 codec. With standard SMBIOS (MacBookPro4,1) Apple don't enable hardware H.264 support on 8xxx GPU-s, but the VDADecoder subsystem reports "it's supported but currently busy" state (with MacBookPro2,1 SMBIOS, VDADecoder simply returns the "non supported" state). When i'm using any other (newer) SMBIOS string (iMac11,1 or MacBookPro5,5; checked with Chameleon) or booting Linux or Windows, H.264 decoding with hardware acceleration are working fine. Chrome Remote Desktop using H.264 videos and maybe the new Chrome/plugin failing when failback to the software decoder are required.
Can you report it to the Chrome bugtracker? Maybe they can fix it on a later release. Turning off hw acceleration degrade performance more (i'm thinking, not only H.264 acceleration are disabled).
So, I finally got around to trying this. I successfully created an installer media on a USB drive. When I reboot from this device, I get to a progress bar that stops roughly three fourths of the way in, before it ends up in a white screen with a crossed out circle sign.
I read up on that problem, but for everyone else who ended up in this, it seems, that their Mac just rebooted without them noticing, trying to boot from an unpatched instatallation. This is not the case with me, I don't get as far as to even launching the installer.
I retried the whole process with the Sierra Installer hosted on Mega, with the same result. I doubt that the drive is broken, because I installed a clean Sierra installation from it just a few days ago, but I don't know how to thoroughly check that, either.
The Hardware I'm trying to get this to run on is a Mac Pro Early 2008, genuine ATI Radeon 5770 HD, Wifi and Bluetooth updated with the kit from osxwifi.com.
Any ideas?
I read up on that problem, but for everyone else who ended up in this, it seems, that their Mac just rebooted without them noticing, trying to boot from an unpatched instatallation. This is not the case with me, I don't get as far as to even launching the installer.
I retried the whole process with the Sierra Installer hosted on Mega, with the same result. I doubt that the drive is broken, because I installed a clean Sierra installation from it just a few days ago, but I don't know how to thoroughly check that, either.
The Hardware I'm trying to get this to run on is a Mac Pro Early 2008, genuine ATI Radeon 5770 HD, Wifi and Bluetooth updated with the kit from osxwifi.com.
Any ideas?
Last edited:
Well, if you're grabbing the Sierra 10.12.2 Installer, I don't think dosdude1's updated his USB creation tool / patcher for that version yet. It simply sounds like your USB installer hasn't been patched, whitelisting your Mac Pro 3,1.
If you're not using his tool located here http://dosdude1.com/sierrapatch.html to create your USB installer, then that'll be why it isn't working.
btw - you did read on the first post of this thread that the BCM4321 wifi chipset isn't supported, right? (there's workarounds to get it working, but there's been reports of random kernel panics from those that have). Most people have found alternate airport cards that they can install.
Well, the patcher at least says it recognized the installer, and gives me no errors while patching it. I had an old copy of the installer package of the golden master and, as I said, retried the process with the installer hosted on Mega, with the same result.
The Wifi card, as I said, is replaced with a 801.n & BLE 4.0 card by osxwifi, and checking the controller model in the System Information, I should be good in that department.
-- edit: Reading up on other problems with newer versions of the installer, you may be on spot, fischersd. The version hosted on Mega may in fact be too new for the patcher. Any idea on where to obtain the right version of the installer?
--edit:
cat "/Applications/Install macOS Sierra.app/Contents/Info.plist" | grep -A 1 DTSDKBuild
gives me "16B2656z", which is 10.12.1. I'm still not sure if thats covered by the patcher.
--edit: aaand once more. Retried with an installer I wisely laid aside a backup of, version 12.0.49, the golden master. So the version shouldn't be the problem, right?
Last edited:
Well, to see if there were any issues with 10.12.2 and dosdude's latest patcher (4.2.2), I downloaded the full installer and created the USB installer. (and now installing it on my MB 5,2).
So, yes, his latest patcher works with the 10.12.2 installer.
If you look at the info.plist under /Contents on the installer, you'll see that the build machine is actually 16C67 (which is a system upgraded from 10.12.1 to 10.12.2). Funny enough, it's also saying DTSDKBuild is 16C67 (thought that was supposed to be the OS build of the package) - any who - we'll see if the build number hasn't been incremented once the install is complete.
As to where to get it....I see there's a torrent that's titled "macOS Sierra 10.12.2 and the latest necessary Office utilities" - just deselect the files you don't want. (ideally, you have a supported machine to grab the installer directly from Apple).
Last edited:
Thanks so much for the efford. I'll retry with the newest version of the installer.
Finished install without any issues. As expected, the build number for a full 10.12.2 install has been incremented to 16C68.
Did you have any issues with the disk utility? I can't figure out why my IMac does.