How to Fix iMessage

[zhuangzi]

I don't think it matters if you have both on line at the same time or not, as suggested Apple could now be checking not only ROM and MBL but also SmUUID and Hardware UUID against the Serial Number. There are quite a few posts of real Macs and Hacks being kicked off from the service due to cloning. The fact that yours is still working is because they haven't got around to your system yet. I would do as Jay suggests and Generate new values for your Hack specially if you can still access the services on you macbook and save your self the hassle of having both you rigs black-listed.

Is there conclusive proof it's just a matter of time? Not sure I've seen that so far (itt).

edit: Not trying to be a contrarian, just approaching the matter rationally.

 

[MysticalOS]

That's just common sense really. No script could do everything at once. It'd be too much load on a complex system that has millions of appleIds and even more devices (often multiple per household). maybe not millions of macs but millions of iphones and many millions of apple Ids for a bot to crawl through. it's pretty logical to assume that they didn't hit a button and magically scan that many accounts in a day. It'd be a bot that crawls and flags accounts over time. this is true for any kind of ban wave. Although you sometimes get the appearance they banned em all at once because sometimes they run the bot for days/weeks first then hit kill switch after flagging all the accounts. Others though flag/flip account as they are found. The ladder being the more likely from apple since we've seen many reports that were staggered which indicate it is being done this way.

 

[esafeddie]

Is there conclusive proof it's just a matter of time? Not sure I've seen that so far (itt).

edit: Not trying to be a contrarian, just approaching the matter rationally.

Have a read of the many other forums not just here - but hey! if you are happy with your set-up then by all means.........

 

[esafeddie]

That's just common sense really. No script could do everything at once. It'd be too much load on a complex system that has millions of appleIds and even more devices (often multiple per household). maybe not millions of macs but millions of iphones and many millions of apple Ids for a bot to crawl through. it's pretty logical to assume that they didn't hit a button and magically scan that many accounts in a day. It'd be a bot that crawls and flags accounts over time. this is true for any kind of ban wave. Although you sometimes get the appearance they banned em all at once because sometimes they run the bot for days/weeks first then hit kill switch after flagging all the accounts. Others though flag/flip account as they are found. The ladder being the more likely from apple since we've seen many reports that were staggered which indicate it is being done this way.

Exactly!!!!!!

 

[jaymonkey]

it's pretty logical to assume that they didn't hit a button and magically scan that many accounts in a day. It'd be a bot that crawls and flags accounts over time. this is true for any kind of ban wave.

@MysticalOS,

Agreed although I believe that most of the ID validation is done during the process of creating/sending the iMessage security token, that way the ID's can be checked on a as needed basis .... don't forget that Apple can also force a iMessage logout and/or a token re-fresh ....

Based purely on the feedback from users on this and other forums, it would seem that if a real Mac has never connected to iMessage but its ID's are used on a hack then the hack will take priority in Apples database over the real Mac .... thus at a later date if the real Mac connects to iMessage it will be flagged/black-listed (incorrectly) as a clone.

I cant prove this theory myself as i don't have a Mac that has never connected to iMessage but it seems to be the case if recent reports are correct. Like i said in my previous post if this indeed what is happening then one can only assume that Apple will be implementing further changes soon to avoid this situation and that this recent change/issue is a short term quick fix to remove what Apple consider cloned systems from its database.

Right now all we can do is wait to see what happens over the next few weeks.

Cheers
Jay

 

[Azimuth1]

@JayMonkey

Today something weird happens to my Hack.

iMessage is still working (with white MLB imported) but Continuity is not working as expected anymore... :

I still receive missed call on OS X but I cannot send/receives normal SMS (green ones) to/from other phones and if I go to :

Setting > Messages > Text Message Forwarding, and look for enabled devices I would like to forward messages to, my Hack in NOT listed anymore!

I'm still logged in Messages on OS X but I'm kind of isolated... ... I can send messages ... but nor receiving them ...

any ideas?

 

[esafeddie]

@JayMonkey

Today something weird happens to my Hack.

iMessage is still working (with white MLB imported) but Continuity is not working as expected anymore... :

I still receive missed call on OS X but I cannot send/receives normal SMS (green ones) to/from other phones and if I go to :

Setting > Messages > Text Message Forwarding, and look for enabled devices I would like to forward messages to, my Hack in NOT listed anymore!

I'm still logged in Messages on OS X but I'm kind of isolated... ... I can send messages ... but nor receiving them ...

any ideas?

It dosn't take an expert to tell your iMessage account has been flagged by Apple - Not wanting to sound like a despot or in the same knowledgeable league as Jay, but quite a few posts back on the first Outage I did predict the method of cloning real mac values to enable some Apple Services was going to end in tears and so I rest my case.

 

[jaymonkey]

@JayMonkey

Today something weird happens to my Hack.

iMessage is still working (with white MLB imported) but Continuity is not working as expected anymore... :

I still receive missed call on OS X but I cannot send/receives normal SMS (green ones) to/from other phones and if I go to :

any ideas?

This is a symptom of the latest (late December) issue ... please see top news article in the guide .....

Quote ...

Symptoms of this latest issue seem to be no messages being sent or received from OSX devices despite being able to log in and out of iMessage without issues, mobile devices such as iPhone and iPad are unaffected.

Cheers
Jay

 

[miketress]

Symptoms of this latest issue seem to be no messages being sent or received from OSX devices despite being able to log in and out of iMessage without issues, mobile devices such as iPhone and iPad are unaffected.

This also happens on the virtual Yosemite I run in a VMFusion 7.1 virtual machine on my MacBook.
Seeing as Fusion also uses the same MLB and ROM (but not serial) as my MacBook, it might be interesting to wait and see how Fusion fixes this.

 

[oOoo]

I read back about ten pages, but I couldn't find any temporary solutions. I fall in the camp of using the same IDs for my hackintosh as my mac. It seems my mac iMessage stopped working on 12/31 later towards the evening.

I contacted Apple support and after about thirty minutes, their diagnosis was to reinstall my OS... How should the dialogue go? I just stated my iMessage was no longer sending / receiving messages.

I'm assuming reinstalling the OS will have no effect. Should I just bring it into the genius bar, let them fiddle around with it and possibly end up giving me a new laptop?