How to Fix iMessage

[sofismatico76]

Esafeddie Could friend create values so I can activate Imessage ...?

 

[esafeddie]

Esafeddie Could friend create values so I can activate Imessage ...?

Sorry these values is best created and applied on your own machine and for me to do that for you I think borders on infringement of Forum Rules. Just follow the steps outlined in the Guide.

 

[P1LGRIM]

I've just been reading through this thread, especially the recent entries, and had a quick question.

@P1LGRIM, you said a bit back that if this was all set up correctly, there should be no need to call apple support. Does that include new apple ids?

That is, if I cleaned my system up (deleted imessage and icloud things), regenerated a serial and mlb etc, along with a new apple id, all through a new ip, do you think that I would be able to avoid the current customer code error?

It is my experience that when everything is set up correctly then everything just works as expected (assuming that there are no errors with your iCloud/AppleID accounts).
I do not subscribe to the new AppleID Vs old AppleID theory, to me an AppleID is an AppleID.

 

[esafeddie]

It is my experience that when everything is set up correctly then everything just works as expected (assuming that there are no errors with your iCloud/AppleID accounts).
I do not subscribe to the new AppleID Vs old AppleID theory, to me an AppleID is an AppleID.

I hear what you're saying Mr.P but don't you find it strange that quite a few members still has this problem i.e iamzacharys post. An old ID will work just fine but a newly created one will not on the same machine, ok so the assumption points to his new ID being flagged on the machine! I have read so many posts with the exact problem its hard to pinpoint exactly what the problem is.
I realise there are many variables and one can easily miss a vital step in the setup that can cause a glitch and screw up a trouble free successful iMsg/F-Time logon but even with the easily understandable condensed Guide To iMessage, how hard can it be?

 

[P1LGRIM]

I hear what you're saying Mr.P but don't you find it strange that quite a few members still has this problem

I agree but the truth is that I am not in possession of enough of the facts to fully understand all of the processes in place.
If a first time user buys a Mac and creates a new AppleID it works without question and does so every time, so as I see it if you set up your Hack correctly there should be very little difference.

 

[esafeddie]

Thanks for the reply!

I see, I might give that a go some time then. Because I know I'm creating the values correctly (show as invalid on apple's site but valid on the other). The thing that doesn't make sense is the old apple id works fine, versus the new one doesn't, but the only difference is that. That is, I created the new apple id after having successfully set everything up correctly.

Anyway, thanks again,
Zach

I don't think you've done anything wrong in the setup as you have proved with the two IDs, since the new security measures from a while back, I have seen this exact problem for a while now with quite a few members. Some go as far as chopping and changing values i.e s/n, MLB, SmUUID etc only to hit the same snag. I have also seen a few use the simple method of just changing the ID password and got it to work! So what can one say, as we are not privy to Apple's Server security methods, one can only assume and hope to get it right.

 

[esafeddie]

I agree but the truth is that I am not in possession of enough of the facts to fully understand all of the processes in place.
If a first time user buys a Mac and creates a new AppleID it works without question and does so every time, so as I see it if you set up your Hack correctly there should be very little difference.

Ahh yes I am in the same boat not understanding all the processes, but the difference, as you know, is one machine specifically made by Apple which should work from the word go and one cobbled together with bits of string and duct tape (sorry for the crap analogy but you get my drift). As I said I see a lot of these posts from members and I get a sense of hopelessness trying to point them in the right direction thinking the easy GUIDE should be enough and yet .........

 

[P1LGRIM]

So, I'm almost 100% sure I've followed the guide correctly, albeit using MacGen for the values. They show up as expected via the everymac/apple checks, which leads me to the what I think the difference is.

For a hackintosh, the serial is valid, but isn't registered on apples side. I suspect when you purchase a mac the serial is saved and submitted to apple, or perhaps just after production even. Thus they know the serials/some pattern in them. If it's a pattern, then we just needa figure that out.

I draw this conclusion because the new account works fine on a real mac, even after being flagged on the hackintosh. Also, the old account works flawlessly wherever. Also, from my reading and numerous calls to apple support, I know that even real macs have this issue. On my last call I spoke to a mac specialist who also said that it's because my serial isn't in the system that I get flagged. That is, my serial isn't in their support system. Sadly I had to take my 'mac' into the service center to actually get them to enter it into the system.

Hope that makes sense,
Zach

On the face of it it makes perfect sense but it just is not true.
I have ten Hacks and all of them work with iMessage etc, none of their serial numbers were entered on Apple's system.
The only time that I had any trouble (call support messages) was when a BIOS upgrade removed native NVRAM support and a previously perfectly working machine suddenly refused to cooperate. It took me a long while to figure that one out but the moment that I emulated native NVRAM support everything worked again.

 

[esafeddie]

All Apple devices has their values digitally added into them either on an EPROM memory chip or some other method at the manufacturing stage and is there for the life of the machine, these values are then added to Apple's data base. If for some reason work has to be done on an Apple device as drastic as changing the main board, this destroys the creditability of the machine so to speak, so to be allowed on some of Apple's Servers, the device has to be reregistered on the data base with the new values.

I have mulled over this a few times - It is near impossible (for an ordinary Joe) to change the values of a genuine Apple device because of how it's values are constructed and added. On a Hack it can be done on a whim with very little effort and this is where I think Apple gets the jitters about hack machines and the potential threats they pose on their Servers.

 

[esafeddie]

Mr. P if you look at your Console Log each time you logon to iMsg/F-Time, you'll see the hack and the Server goes through a kind of hand shake ritual of data sent back and forth. Before it reaches that stage though, a Security Token/Certificate - I think it is called 'Apple Application Integration Certification Authority' - is granted to enable the hack access. What and how this merits each machine access is still unclear and I am not near enough clever to fathom it out.