Search results

Do you have a valid AppleID which has purchased some version of the OS at some point? If so, you should be able to delete whatever email account is associated from the System Preferences and re-add it to the system and then log back into the AppStore as your own email address. If you've done...

FWIW, I'm having the same issue with the same mobo/processor combo, although I seemed to have it in Mavericks as well.

I can't be certain, but this may not be the actual cause of your crash. When I was setting things up on Chameleon I would see a page or two of this scroll by without any real problems booting. The next stage I believe is the USB drivers - I would double check all of your settings are correct for...

Huzzah. Is there a way to change my vote from "Not Working" to "Working" ? :) Once I followed ALL of the steps in the guide, including the 2nd page steps for making sure all the proper UUID values etc. were setup correctly and persistent and Z77 issue was addressed, I naturally got locked again...

Well, I got Apple to unblock my iMessage... I generated a new serial number, performed the SMbID bug fix, etc. following the guide. AppStore works fine and so does FaceTime. No love from iMessage though. I reset my AppleID password as well. Realized that I didn't setup the MLB correctly, so I...

Note to those having the red contact error and the inability to send sms... I was looking into my console logs and then Google searched the error messages. Most came up with articles regarding people's Mac's who have been hacked. I suspect this issue is directly related to using the default...

Well, Apple was able to unlock me... They said something about IP address blocks seem to happen to people randomly, so I guess perhaps it's happing to those with real Mac hardware as well occasionally. I am able to sign in but not actually send iMessages, so perhaps it's not quite fixed... or...

I was never ever able to get it working with Mavericks with Chameleon... I switched to Clover now on Yosemite and am now getting the message to contact support. I suspect this was the reason things weren't working under Mavericks as well (being locked out). Given the reports I'm currently on...

Looking back at one of the things I did which helped and might for your issue - try backing up then removing the "/System/Library/Extensions/GenericUSBXHCI.kext/" kext file. Given where it has stalled... A couple of other things come to mind: - Do you have any USB 3.0 devices currently...

I tested the drivers extracted from the 10.10 beta that Netkas provided a few months ago with Mavericks, and now with ones provided directly with Yosemite (on Yosemite naturally) In neither case was the R9 290x working with multiple displays - any attempt at connecting a 2nd monitor either to...

I have a Sabertooth Z77 based system working with Yosemite. As suggested, try booting with the "-f" flag and/or "UseKernelCache=No"