How to Fix iMessage

[Walril]

Tony,

You should have a razzie award on this thread.

 

[zee2]

Hello there,

Followed your tutorial, and the one on insanely and I'm able to log in and out and in and out as many times as I please. Initially, I was able to send a message to myself and it would come back. However, only on the hackintosh, my other devices using the same apple ID did not get the messages.

Now, when I try to send a message, this is what console logs:

[Warning] *********** Failing message: FZMessage[outgoing: YES sender=(null); service=iMessage; handle=+1xxxxxxxx00; unformatted=(null); country=(null); roomName='(null)'; flags=100005; subject='<< Message Not Loggable >>' text='<< Message Not Loggable >>' messageID: 32 GUID:'56C2B86A-B336-4E63-9515-293FE79414A7' date:'443337476.000000' date-delivered:'0.000000' date-read:'0.000000' transfer guids: '(null)' empty: NO finished: YES sent: NO read: NO delivered: NO from-me: YES DD results: NO DD Scanned: YES Downgraded: NO emote: NO error: 0]    empty source ID or idsAccount supplied ((null):IDSAccount: 0x7f8f93604c90 [Service: com.apple.madrid  User: [email protected]  ID: 32E14E05-8030-4778-8AC7-5389C9D6CBF2  Type: Apple ID  Active: YES  Registration Status: Registered])

Any clues as to what's going on? Thanks

I'm running 10.9.5, latest clover, used my early 2011 MBP real numbers.

 

[underlircs]

Is there a working solution for someone running Mavericks? I have a MacBook Pro that I do not need to have iMessage running on it. If there is a solution for a machine running Charmelion and Mavericks, can someone point me in the right direction?

 

[jaymonkey]

If I were to purchase the bare minimum equipment on eBay (a machine that will never be OS-loaded) to obtain a valid MLB, how low can I go?

@jminiman,

I cant give you specific model numbers, but any 2008 Mac or older with a 13 digit or 17 digit MLB should work, however if it is a dead system you may not be able to extract all of the ID's such as ROM ... etc, MLB should be printed on the system board.

Use Mac Tracker to check system compatibility / hardware configuration against the system type.

Followed your tutorial, and the one on insanely and I'm able to log in and out and in and out as many times as I please. Initially, I was able to send a message to myself and it would come back. However, only on the hackintosh, my other devices using the same apple ID did not get the messages.

@zee2,

The iMessage issue are on-going, if you uses the cloned ID's on more than one system (inc your Mac) then the chances are the MLB/ROM is temporally blocked. Logout of iMessage on all systems and revert to local generated values for your hacks - then you'll have to wait for the security tokens to expire - see the news items at the start of the main guide.

Is there a working solution for someone running Mavericks? I have a MacBook Pro that I do not need to have iMessage running on it. If there is a solution for a machine running Charmelion and Mavericks, can someone point me in the right direction?

@underlircs,

Follow the guide, use the MLB & ROM value from your MacBook (use iMessage debug or Darwin dumper to get these values) - see Part-1, Step-5d. Ensure that you logout of iMessage on your Macbook before cloning the values to your hackingtosh. If possible also logout of of your AppleID if not needed. You can use either Clover or the new version of FileNVRAM to inject the MLB & ROM values.

Cheers
Jay

 

[ydp]

I'd just like to note that I have both my real Mac and my hack logged into iMessage and both work fine still. I've had it through December with no issues. I don't use it too frequently on either machine though. I might send 20 messages a day through it on my most used day. And almost all of that is on my hack at my office, not my real Mac.

 

[Foxtrot]

I'd just like to note that I have both my real Mac and my hack logged into iMessage and both work fine still. I've had it through December with no issues. I don't use it too frequently on either machine though. I might send 20 messages a day through it on my most used day. And almost all of that is on my hack at my office, not my real Mac.

@ydp, is your smUUID also cloned?

 

[zee2]

@zee2,

The iMessage issue are on-going, if you uses the cloned ID's on more than one system (inc your Mac) then the chances are the MLB/ROM is temporally blocked. Logout of iMessage on all systems and revert to local generated values for your hacks - then you'll have to wait for the security tokens to expire - see the news items at the start of the main guide.

@jaymonkey, I have yet to activate iMessage on my old macbook pro. Does that make a difference? And when they ban your computer based on MLB or whatever, do they still allow logins/logouts from that machine?

 

[mattystonnie]

I did a fresh install of Yosemite 10.10.1 and was able to signin to iMmessage and FaceTime,but again can't send messages,only to myself.
When i look at iMessages settings everything is enabled, i get the error "this number is not registered with imessage".
Same thing with Mavericks 10.9.5.

 

[zee2]

I did a fresh install of Yosemite 10.10.1 and was able to signin to iMmessage and FaceTime,but again can't send messages,only to myself.
When i look at iMessages settings everything is enabled, i get the error "this number is not registered with imessage".
Same thing with Mavericks 10.9.5.

Yup, same here. So there's still something missing. MLB/ROM is most likely not the only thing that needs to be real/official.

I was going to install 10.10.1 but now that you did, no need

 

[MysticalOS]

I think a lot of you are failing to read the part where if you clone Ids, it needs to be from an INACTIVE system. so many users posting "i cloned my ID and used it on two machines and now message delivery fails". Please read through original post and other posts in this thread to figure out why this is happening to you. even if you sign out of that system, before doing it. You probably have to wait a while for it's token to expire before booting up clone with it, or as far as apple system will be concerned, it still has two registered machines using those values and it'll trigger the block. This is why old unused systems are the ideal ones. It's just a shame my old macbook pro is a 1,1 model from 2006. DOH!

I have yet to call apple back with my generated values to see if they'll pass the bill or not. I probably will at some point because i think they will work, at least until they tighten it up and find rom was generated from non apple interface. I thought about fixing that too but the thing is, they already whitelisted my rom in past so i figure i'm getting off calling back with same rom that is already whitelisted and just act dumb on why the whitelist stopped working (i know why it did, 17 char serial with a 3,1 instead of 13, which i have fixed now).