Jump to content


  • Content Count

  • Joined

  • Last visited

About Capsule

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
  1. Capsule

    How to Solve Imessage Login Problem

    Using another ROM value would have probably avoided having the real Mac blacklisted but now it's too late ;-) Btw I've now cloned another real mac which I know will never be used to connect to iMessages/FT and it worked right away.
  2. Capsule

    How to Solve Imessage Login Problem

    I had this one day before it worked again. Maybe try resettting the network preferences, who knows... Using Finder navigate to: /Library/Preferences/SystemConfiguration/ Delete the following two files: NetworkInterfaces.plist preferences.plist Empty the trash and reboot.
  3. Capsule

    [Guide] AIO Guides For Hackintosh

    Yep, same here. After 4 days my Macbook was unblocked. Before that, I could still log into iMessage but sending messages was just resulting in a "delivered" status, and the message was going nowhere. You should receive the "Your Apple ID and phone number are now being used for iMessage and Facetime on a new Mac. If you recently signed into "Name of your real mac here"..." alert box on any other iDevice when it's unblocked.
  4. Capsule

    How to Solve Imessage Login Problem

    They tried a few things on Wednesday when I had a chat with them, like signing out from all devices, removing contact emails or change the "start new conversations from" setting with no luck. The guy I was chatting with was supposed to get some more info from a senior advisor but he couldn't reach him and I was supposed to call them back, which I never did. On Friday I couldn't send messages anymore, like always, but this time iMessage was aware something was wrong because it was telling me it couldn't send the messages. Yesterday I saw new messages in system.log I had never seen before, but still no luck. The messages were: Jan 4 16:52:18 Macapsule discoveryd[50]: WCFNameResolvesToAddr: called Jan 4 16:52:18 Macapsule discoveryd[50]: WCFNameResolvesToAddr: entering Repeated a few times. And today, I received a notification on my iDevices saying "Your Apple ID and phone number are now being used for iMessage and Facetime on a new Mac" + the computer name so I knew something had definitely been unblocked. In fact, you're supposed to receive such a notification everytime you sign in on a devices (if the previous state was signed out). And indeed, I can send and receive iMessages from my Macbook. Facetime works again too (I could call other devices but once they accepted the call, it hang up, and I couldn't receive any call. So, either they did something on the server or my Hackintosh session automatically expired after 4 days (I've reverted it back to a random serial/MLB/rom since then) and my Macbook is recognized again as the "master" computer behind these MLB/ROM values. When did the blocking occur on your side?
  5. Capsule

    How to Solve Imessage Login Problem

    Same here, I still have to contact them again with some system.log extracts to show there's something wrong.
  6. Capsule

    How to Solve Imessage Login Problem

    With myself ;-) (yes, I have a real Macbook Pro AND a Hackintosh)
  7. Capsule

    How to Solve Imessage Login Problem

    That would help me as well... My real macbook pro is stuffed now. I even tried with a new apple ID. It connects OK but I can't send or receive any iMessage :-(
  8. Capsule

    How to Solve Imessage Login Problem

    I've used MLB and ROM values from my real Macbook Pro and got iMessage running on my Mavericks hackintosh but now I don't get any new iMessage on my real Mac! Which somehow makes sense... Apple servers decided the last registered hardware was the one to receive the messages, since they look like clones now. Does someone know how to revert this or have it working on both computers? I'm upgrading the Macbook Pro to Yosemite, maybe it will solve the issue, or maybe not :-)
  9. Why don't you update your kext permissions and delete their cache manually? All it takes is a few commands: http://www.macbreaker.com/2012/01/how-to-manually-install-kexts.html I've got the same MB/CPU and currently running 10.9.3 with network (obviously ;-)) and sound. The sound patching was a bit tricky, I patched my DSDT using these instructions (just the DSDT part) : http://www.insanelymac.com/forum/topic/280468-applehda-patching-in-mountain-lion/page-4?do=findComment&comment=1839042 And used this kext: http://www.insanelymac.com/forum/files/file/17-applehda-for-ad2000b-108/ For the network, you can follow these instructions: - Open a terminal and enter: sudo nano /System/Library/Extensions/IONetworkingFamily.kext/Contents/Plugins/AppleYukon2.kext/Contents/Info.plist - Find Yukon-88E8053 and make it Yukon-88E8056 - Find 0x436211ab and make it 0x436411ab Of course you need the purge cache/fix kexts permissions everytime you make a change to them. HTH
  10. Did you try this? https://discussions.apple.com/thread/4255454?start=150&tstart=0 First time I installed 10.9, I had to do this. If the 10.9.2 update messed with your network interfaces, you probably need to delete /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist