Jump to content

How to Solve Imessage Login Problem


  • Please log in to reply
164 replies to this topic

#161
besweeet

besweeet

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 168 posts
  • Gender:Male

I had this one day before it worked again. Maybe try resettting the network preferences, who knows...
 
Using Finder navigate to:[/size]

/Library/Preferences/SystemConfiguration/[/size]

Delete the following two files:[/size]

NetworkInterfaces.plist
preferences.plist 
[/size]


Empty the trash and reboot.[/size]


Done. Same error :(. I'll call Apple to get the VM activated with the code from Messages and maybe it'll free it up so I can use my MacBook Air again.

#162
besweeet

besweeet

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 168 posts
  • Gender:Male

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?


Is changing the ROM similar to changing the MLB? I modified one number in the ROM that I injected via the VMX and will see if it happens to do anything. Apple said that there may be a serial number issue now with my MacBook Air, even though that and my VM don't share the same serial, and now they don't share the same MLB or ROM.

#163
Capsule

Capsule

    InsanelyMac Protégé

  • Members
  • Pip
  • 10 posts
  • Gender:Male
  • Location:Brussels

Is changing the ROM similar to changing the MLB? I modified one number in the ROM that I injected via the VMX and will see if it happens to do anything. Apple said that there may be a serial number issue now with my MacBook Air, even though that and my VM don't share the same serial, and now they don't share the same MLB or ROM.

 

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.



#164
besweeet

besweeet

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 168 posts
  • Gender:Male
So I finally had iMessage in my VM activated again, using the activation code that Messages gave me, and things are fine over there. It's using a random MLB and ROM that I generated. Still a no-go for my MacBook Air.

Again, here's my VMX file if anybody's interested: http://pastebin.com/raw.php?i=mawuUDGY

My MacBook Air did bring up the "your iMessage account is being used from XXXXX computer" (or however it was worded), yet I still can't sign in on it.

Hmm.
 
For your problems with MBAir, try this: http://www.ehow.com/...al-command.html


"serversetup" is an unknown command.

#165
besweeet

besweeet

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 168 posts
  • Gender:Male
Just a quick update for anybody who may happen to be following this. I just tried signing into iMessage on my MacBook Air, and it successfully decided to sign in. Everything now appears to be working as it should. I have a feeling that it'll be my desktop that decides to stop working when I boot it back up in the morning, although it hopefully won't, as its MLB and ROM are different.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2015 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy