Contribute
Register

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,997
Motherboard
GB Z490 Vision G
CPU
i9 10850K OC @ 5.2 GHz
Graphics
Vega 64 LC + HD 630
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Mobile Phone
  1. iOS
I have replaced my NIC Dlink DGE-528T by completely new one - HP NC360T, then generate new S/N and NO result :banghead::banghead:.
Then i switched back to Dlink.Now my NIC has MAC c8:be:19:xx:xx:xx

@jay
Am I right, that you still have no problem with iMessages? According to your theory, you just have to replace your NIC or generate new S/N and you will immediately get this issue. (may be forever, he-he)

Absolutely no problems at all across all my hackingtosh systems (7 desktop and 2 laptop) I am often logged into iMessage on two or three machines at the same time and all send and receive and sync perfectly. I maintain the same S/N and BCD names on all NIC's on all systems no matter what version of OSX.

Cheers
Jay
 
Joined
Jan 11, 2014
Messages
21
Motherboard
Asrock Z77m
CPU
Intel i3-3225
Graphics
HD4000
Mac
Classic Mac
Mobile Phone
Shiitaki and jaymonkey,

First of all, everyone's help in diagnosing and solving this is really tremendous, so thank you! I do understand the hypothesis regarding the serial number, MAC address and UUID. However, for those of us that did not make any recent changes (i.e., iMessage was working normally, we shut down the computer and the next time we booted it was not working), does that situation fit with the hypothesis? I am a fairly new hackintosh convert, and must admit that I was lucky in that my setup required very little messing with after the initial install, so can't imagine many times that my serial number or mac address have changed -- though I can think of at least two times that the S/N has changed off the top of my head.
 
Joined
Jul 26, 2011
Messages
60
Motherboard
GA H170N-Wifi
CPU
I3-6100
Graphics
UHD 530
Shiitaki and jaymonkey,

First of all, everyone's help in diagnosing and solving this is really tremendous, so thank you! I do understand the hypothesis regarding the serial number, MAC address and UUID. However, for those of us that did not make any recent changes (i.e., iMessage was working normally, we shut down the computer and the next time we booted it was not working), does that situation fit with the hypothesis? I am a fairly new hackintosh convert, and must admit that I was lucky in that my setup required very little messing with after the initial install, so can't imagine many times that my serial number or mac address have changed -- though I can think of at least two times that the S/N has changed off the top of my head.

agreed, i didn't make any changes in bios or kext related items. iMessage works fine after 10.9.2 update.
I'm still betting it's something on apple server side.

can anyone CONFIRM this? I'm able to make FaceTime AUDIO calls, but once pickup by the other end it disconnect automatically shortly after a few seconds of audio.

FaceTime VIDEO call works as usual.
 

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,997
Motherboard
GB Z490 Vision G
CPU
i9 10850K OC @ 5.2 GHz
Graphics
Vega 64 LC + HD 630
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Mobile Phone
  1. iOS
I was lucky in that my setup required very little messing with after the initial install, so can't imagine many times that my serial number or mac address have changed -- though I can think of at least two times that the S/N has changed off the top of my head.

agreed, i didn't make any changes in bios or kext related items. iMessage works fine after 10.9.2 update. I'm still betting it's something on apple server side.

Well i guess it would depend on how long Apple have been storing UUID's (I would think they have been doing so for a long time) and when (if) they introduced a MAC Addr+SN / UUID check and how many times they allow such a miss-match to occur before flagging it in the database ?

If Apple where clever (which they are) they could gain a lot of interesting stats from identifying such mis-matches ? ie - Hackingtosh users v real MAC users ?

I'm not saying that this is the case, just offering a possible explanation and how i see it, it also doesn't mean we cant solve this issue, it just means we got a bit more investigative work to do ;)

Cheers
Jay
 
Joined
Jun 13, 2012
Messages
203
Motherboard
Gigabyte GA-P67A-UD3-B3
CPU
Intel Core I7 2600K
Graphics
Nvidia Geforce GTX 960
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
For those experiencing the "Your Apple ID can't be used to set up Imessage" error, and subsequently being told to contact support, I just fixed mine by putting a credit card number. I previously had a credit card associated with my Apple account, but recently left that field empty. Re-adding a credit card seems to fix it. The strange thing is that my MacBook Air wasn't experiencing this problem, but from reading the Apple forums, even real Macs can suffer from this strange requirement/bug.
 
Joined
Aug 3, 2012
Messages
17
CPU
Intel I5 3570K
Graphics
GTX 660
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
agreed, i didn't make any changes in bios or kext related items. iMessage works fine after 10.9.2 update.
I'm still betting it's something on apple server side.

can anyone CONFIRM this? I'm able to make FaceTime AUDIO calls, but once pickup by the other end it disconnect automatically shortly after a few seconds of audio.

FaceTime VIDEO call works as usual.

I didn't make any changes as well. It stopped working by itself all of sudden.

I just tried FaceTime audio and it still works here. I talked for a minute and no drop.
 
Joined
Oct 10, 2012
Messages
587
Motherboard
Wolfies BeQuiet
CPU
6700k + Gigabyte Z170X Designare
Graphics
EVGA 1080ti FTW3
Mac
  1. iMac
I can't wait to go home and see if this issue has affected my UP5-TH build. If Apple is collecting/blocking users on such systems, why do it through iMessage. Seems to be a soft way or generally insignificant way of blocking hackintoshes. Why not go full monty and block iTunes/icloud and software updates? While iMessage is pretty cool feature, it isn't vital.

Having said though, I'm a iMessage junky and hope this can be resolved.
 
Joined
May 22, 2013
Messages
26
Motherboard
GA-Z77X-UP5 TH
CPU
Intel i7 3770K
Graphics
EVGA GeForce GTX 660
Mac
  1. MacBook Pro
Classic Mac
Mobile Phone
  1. iOS
Add another to the list. App store and all the other things work fine, but all contacts in iMessage come up red and as "not registered". This started a little while ago and figured maybe it was something with my internet as in the past iMessage randomly stopped working, then started up again a few hours or days later, but I did a clean install and update of Mavericks, and still can't send anything from iMessage.

On a GA-Z77-UP5-TH. Also, iMessage works absolutely fine on my iPhone and iPad.
 

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,997
Motherboard
GB Z490 Vision G
CPU
i9 10850K OC @ 5.2 GHz
Graphics
Vega 64 LC + HD 630
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Mobile Phone
  1. iOS
So, Why don't you change S/N on any of your system and as far as I understand your theory - you'll stuck in this issue with iMessage?

Because that is the behaviour of a real mac, nether S/N or LAN MAC address would ever change.

We need to collect more information on systems that are suffering from this recent issue, I think a good start would be comparing the first three octets of MAC address's (the OUI), to see if there is a patten which could be identified against a black or white list on Apple's servers.

Cheers
Jay
 
Top