Search results

I'm on 10.12.4 with a GTX 970, updated to the latest drivers. Since then, after the computer is idle for a bit when moving the mouse again it doesn't freeze but it's really really really laggy for a minute and two and then goes back to normal. No sleep, no screensaver. Anyone seeing this?

Mmm will check the cables tomorrow, just in case, but in my case before booting macOS or when booting macOS with the default drivers the fans are stopped. They only go 100% when macOS is loading with Nvidia's drivers. Given that you tried to boot without the Nvidia drivers, I'm guessing it may...

I have a GTX 970, I'm using the iMac14,2 definition and with Nvidia drivers enabled I also have the fans at full speed. When disabling the drivers the fan is quiet.

I still have this issue. I have the FakeSMC and some sensor kexsts, plus audio and LAN kexts. How is your setup in regard to hard drives? Do you have one HD, SSD+HD...? As I said above, this started happening when I made a SSD Raid 0 boot drive.

Tried updating to the latest macOS build (10.12.1 16B2657), latest Nvidia driver 367.15.10.15f03 without luck.

Tried coping all the files from my old EFI partition to the new EFI partition, reinstalling Nvidia drivers. Still the same. Only difference between my old setup and my new is that instead of having an SSD boot drive with the EFI partition, now I have an SSD software raid and the EFI partition...

I changed hard drives today and installed the latest version of clover on the new drive and I'm too seeing this issue. I have a GTX 970. Previously I had r3793, so I though maybe there's been some change between the latest version and the one I had. Closest version I could find to the one I had...

It's working again, without me having to do anything. There were some issues with the Mac App Store, probably some connectivity problems that affected iMessage.

I'm not gonna even bother with deleting caches and all that, I've already been the one of the first to get a new weird issue a in the past so I'm pretty sure it's Apple either having some issues or making some changes. If it's not resolved at the beginning of next week, probably Apple made some...

I'm seeing the same issue, with a computer build just this week. Yesterday morning (CET) was the last time it was working.

Logged in today fine, no need to call nor reset iOS config. I did delete the cache and preferences files as going through the guide I saw that the S/N I had didn't have the proper suffix, so I created a new identity.

Using iOS?: Yes, 8.3 OS X version: 10.10.3 Boot-Loader type and version: Clover, revision 3202 Continuity/Handoff binary patch installed?: No, I don't remember installing this. Confirm that Continuity/Handoff is working: It was, but it appears that it's not working now. Don't use it much, except...

Created a new identity following the guide, starting by deleting the cache and preference files. But at the end got the customer code when logging in. The previous identity I had was working since last year (except during the november-february period during the "blackout") until yesterday...

Changed my AppleID password yesterday and now when trying to login, with an app specific password due to two factor authentication, I'm getting the customer code. I'll go through the guide to check that all is still as it should and see if there's any info since the last time I did all the guide.

New stuff was added with Yosemite for sure, like SMS forwarding. And with that, security must have been tightened because someone with an Apple ID could use it to bypass two factor authentication that send a code via SMS, for example.

There's a security token you need to keep iMessage working, and it expires after a certain time. When the token has expired, your computer tries to generate a new one sending your information to Apple, they say nope because the information they received did not pass their checks, so you don't...

The least risky case when spoofing ids from a real mac is when the real mac has the same system type as the hackintosh and the real mac stays offline. Apple probably still could figure out if it's real or not, but doesn't seem like it right now. In any other case: system type mismatch...

I had my MLB split in two lines, with the second one just having one character/byte 000000: 43 ... 000010: 43 Number of Bytes making up the MLB .... eg: 17 Number of Characters in the string .... eg: 17 Your System Type .... eg: MacBookPro 11,1 Last four digits of OSX S/N .... eg: G3QH First...

If they are checking if a MLB is fake, instead if looking if the MLB is stored in some database of theirs, then it's just a matter of finding how the last digits of the MLB are generated on real macs instead of putting in random characters. Regarding the 13 character long, if it really works...

Hi, reading the post about the 13 character long MLB, I decided to try and boot with one of those. Tried to log in with an AppleID that hasn't been unlocked by calling Apple and I'm getting the customer code at this window Yet if I try with one account that was unlocked by Apple I get the...