How to Fix iMessage

[redzacke]

Hi jaymonky,

i really tried everything you described in your guide. But iMessage still does not sign in. I always get the message: "please contact Apple Support".

Things I tried:
Your Guide,
changing my password,
turning off 2-Step-Verification
turning off all of my Apple devices

I don't have any further idea to solve this issue.
Please help me.

Cheers
redzacke

 

[carpentryplus25]

Hi jaymonky,

i really tried everything you described in your guide. But iMessage still does not sign in. I always get the message: "please contact Apple Support".

Things I tried:
Your Guide,
changing my password,
turning off 2-Step-Verification
turning off all of my Apple devices

I don't have any further idea to solve this issue.
Please help me.

Cheers
redzacke

Is it giving you an error code along with telling you to contact apple cause if so I got that exact message before and just called them and they fixed something and it magically started working

 

[jaymonkey]

Hey Guys,

Just a little bit more info, have just installed all recent OSX updates including the Safari 7.0.3 update and iMessage is still working for me. So definitely nothing to do with these recent OSX updates.

Can i ask all those who have seen the recent "Recipient is not registered iMessage User" issue.

Is there a valid Apple device (iPhone, iPad, Mac ..ect) associated with both your own Apple ID account and the contact your trying to send the message to ?

I beginning to wondering if this issue only effects users who do not own any Apple device(s) ?

I will try a fresh/clean build in the next few days and see what happens.

Cheers
Jay

 

[mhollow]

Hi, Jaymonkey!
As I sad before, I have two different builds, and one is expericencing issue with Messages, while another one doesn't! (Different appleId). So, can I say that issue doesn't associated with original Apple devices?

And yes, I have an iPad with the same appleId(which doesn't work on main rig) and Messages works on it without a hitch with same contacts.

I beginning to wondering if this issue only effects users who do not own any Apple device(s) ?

 

[vinhsonnguyen]

This is pretty much 100% on Apple's side i.e. they have changed something their end because I know I was messaging with this Hack last week. I even got the App Store telling me there was a Safari upgrade waiting for me so I know I had restored properly.

Yes, definitely seems like it's from Apple's side as I haven't updated anything on my Hackintosh for weeks. No system, application, or driver updates, etc.

I beginning to wondering if this issue only effects users who do not own any Apple device(s) ?

Yeah, definitely not true as I own an iPhone, iPad, and MacBook all signed into iMessage just fine

 

[redzacke]

Hi guys,

if you got a message like:

"Your Apple ID "[My Mail ID]" can't be used to set up iMessage at this time. If this is a new Apple ID, you do not need to create another one. To use This Apple ID with iMessage, contact iMessage support with the code below.
Customer Code: 9732-7292-2080"

then just call the support. They'll make it easy!
Don't worry saying that you are using a Hackintosh. But you must have an original Apple device like an iPhone associated to your Apple ID.

 

[jaymonkey]

Yeah, definitely not true as I own an iPhone, iPad, and MacBook all signed into iMessage just fine

Thats what I was suggesting, as long as you have at least one Apple device associated to the Apple ID then it looks like iMessage can be made to work (as long as you apply the steps in the guide).

I think this recent change at Apple's end is causing two types of issues:-

Recipient is not registered iMessage User

In this case I think the message is generated if no genuine Apple device is associated either with your Apple ID or the Contact your trying to send to ?

Your Apple ID "[My Mail ID]" can't be used to set up iMessage at this time.
If this is a new Apple ID, you do not need to create another one.
To use This Apple ID with iMessage, contact iMessage support with the code below.

Customer Code: 9732-7292-2080"

In this instance as redzacke suggests a call to Apple customer support seems to resove the issue, as long as you own at least one Apple Device (some sort of account status change/update made by customer support) ?

I'm really just trying to clarify things at the moment, so if you can prove that either of the above cases are true (or false) please give some feedback.

Cheers
Jay

 

[mhollow]

If it's on the Apple's side, why do some hackintosh users have that issue and others don't?
The main question is - what's the common between problematic builds?
I still think - It's hardware characteristic, especially Ethernet device and kext.

Yes, definitely seems like it's from Apple's side

 

[MaDxCrEaM]

Hey Guys,

Just a little bit more info, have just installed all recent OSX updates including the Safari 7.0.3 update and iMessage is still working for me. So definitely nothing to do with these recent OSX updates.

Can i ask all those who have seen the recent "Recipient is not registered iMessage User" issue.

Is there a valid Apple device (iPhone, iPad, Mac ..ect) associated with both your own Apple ID account and the contact your trying to send the message to ?

I beginning to wondering if this issue only effects users who do not own any Apple device(s) ?

I will try a fresh/clean build in the next few days and see what happens.

Cheers
Jay

Can't be it. I have an ipod and Iphone associated with my apple id and all users on my contact list are actually apple users, not hackintosh users. So not sure what the problem is. GA-Z77X-UP5-TH That's the board I'm using on my build.

 

[jaymonkey]

Can't be it. I have an ipod and Iphone associated with my apple id and all users on my contact list are actually apple users, not hackintosh users. So not sure what the problem is. GA-Z77X-UP5-TH That's the board I'm using on my build.

@MaDxCrEaM,

Thanks for the confirmation, if thats the case then we can eliminate that theory.

What is the exact error are you getting ?

If its the second message as in post #238 have you tried calling Apple customer support ?, like carpentryplus25 & redzacke suggest ?

Cheers
Jay