Contribute
Register
Has anyone had followed the whole guide (with Clover), gotten the contact customer code, and then the agent failed to fix it. I've had to contact them in the past and have been successful every time but this time she is trying to unblock to no avail.
 
Damn ! same here ....

I am locked out since more than 6 months from iMessage (´had never enough time to read through the tutorial, because of a
lot of work in real-life) now i have just applied all fixes to all my 3 Hacks and tried to call the apple support 2 days ago.
They said they have unlocked me, but i still get this customer support message on iMessage :(.

Hope You heroes out there will find a fix for this as soon as possible !

By the way, thank you for the great work you all doin out there!
and a question:
I´m still on 10.9.5 for now, but now that iMessage does not work for me, should i upgrade to 10.10.1 or would it be
better to stay at 10.9.5 and wait for a new fix for iMessage ???
 
Has anyone had followed the whole guide (with Clover), gotten the contact customer code, and then the agent failed to fix it. I've had to contact them in the past and have been successful every time but this time she is trying to unblock to no avail.

From a networking engineer standpoint this sounds too much like a failure to propagate. If so, give Apple time to fix their own internal issues. All I know is that I have no issues logging in and out, and have even gone as far as doing a complete Time Machine restore. No issues have surfaced with my iMessage functionality, and Im using the same methods as outlined by Jay.
 
@All,

To those of you that are experiencing login/authentication issues even after applying all the fixes and tips from the guide and you have persistent MLB, ROM and valid OSX S/N and SmUUID.

I've been looking in to this and following a few users attempts at trying to get iMessage to generate a contact Apple message with a customer code ...

In some cases, the user had multiple attempts at fixing each issue, i think its possible that one or more of the ID's have been black-listed whist the others are ok ....

Example ..

After going through the guide It possible that some users had valid MLB & ROM values .... but the OSX S/N is not valid (either black-listed or incorrect for system type) ... Subsequently the user discovers issue with OSX S/N and generates new one and this time they get Contact Apple Message.

After Activation iMessage works until new logout/login ...

On next login the ROM and/or MLB value have been to found to match more than one S/N ... so MLB & ROM are flagged or black-listed.

To resolve this you could generate a completely new identity for your system :-

  1. Run iMessage Debug and make sure to have a copy of the output
  2. Logout of all iMessage Apps
  3. Disconnect from network
  4. Mount EFI Partition and load Clover config file into Clover Configurator
  5. Goto SMBIOS page and click on Magic Wand, Click a few times on the two 'shake' buttons
  6. Check the new OS X S/N using the method described in Part-1, Step-3 of the guide
  7. Keep generating new S/N until you get a valid but un-registered S/N
  8. Run terminal and generate new SmUUID via 'uuidgen' command (See Part2, Step-7)
  9. Copy and paste new value from terminal to SmUUID
  10. Complete the new identity by injecting MLB & ROM via one of the methods in Part-1, Step-5d
  11. Save the Config file and exit Clover Configurator
  12. Reset the OSX Network setting plists - See Part-1, Step-2
  13. Clear iMessage Config Data - Part-1, Step-4
  14. Restart - keep disconnected form network
  15. Run iMessage Debug
  16. Check the output against your old values, ensure that Hardware(Platform) UUID, S/N, MLB. ROM are completely different, if it looks ok - shut down and restart
  17. Run iMessage Debug again.
  18. If all ID's are new and persistent then shut down, re-connect to network
  19. Run DPCI Manager and check BSD names en0...etc and are flagged as 'built-in'
  20. If all ok login into iCloud first then iMessage
  21. You may get the contact Apple Msg .... if so then its Part-2, Step-8 again ....
Let me know if this works ... if so i'll expand it a bit and put it in the guide ..

Cheers
Jay

Hi Jay, Just a update I did exactly as you said in these revised instructions and get the contact apple screen. Its a different code but its consistent. Unfortunately I am not able to call support tonight but just wanted to chime in to tell others my experience to perhaps save them the heartache.

I will update this post when I get with apple and see whats going on. I will use the same case id, however they will probably see the different s/n. I also tried instead of a 8,3 i7 sandy a 8,2 i7 sandy macbook to see if that changed anything being my laptop is a asus g74sx i7 sandy 2670qm built in 2011.

Thanks again for all your help and hopefully as a community we can find a breakthrough soon!
Pat
 
Has anyone had followed the whole guide (with Clover), gotten the contact customer code, and then the agent failed to fix it. I've had to contact them in the past and have been successful every time but this time she is trying to unblock to no avail.


I followed Jays awesome detailed guide all the way through and strictly use clover. I got the contact apple code message, spent almost 2 hours with the agent, then the senior advisor and had no luck despite them using numerous attempts to remove the registration block.

Im curious how long the registration block is lifted for when they remove it. If its an hour, 24 hours, etc. Im sure there's a time interval involved for security reasons but thats above me.
 
From a networking engineer standpoint this sounds too much like a failure to propagate. If so, give Apple time to fix their own internal issues. All I know is that I have no issues logging in and out, and have even gone as far as doing a complete Time Machine restore. No issues have surfaced with my iMessage functionality, and Im using the same methods as outlined by Jay.

Do you think the "an error occurred during activation. try again" error is due to Apple's servers having problems? Or is this something on my end (I doubt it since it was working perfectly last time I used it, but I want to hear from someone more knowledgeable)?

Thanks
 
Do you think the "an error occurred during activation. try again" error is due to Apple's servers having problems? Or is this something on my end (I doubt it since it was working perfectly last time I used it, but I want to hear from someone more knowledgeable)?

Thanks

Im not more knowledgeable but I can tell you I have had no issues changing my osx sn, MLB and ROM values to try to rectify the customer code issue recently popped up. I still get the customer code message but its a different code. Getting the customer code message is a good thing as it means you are communication with apples servers. The activation error means somethings not right so apples servers aren't communicating with your computer.

Id suggest verifying everything again from SN to MLB/ROM, regenerate a new smuuid via terminal uuidgen and try again. I had to change my smuuid to get the servers to communicate.

Hope this helps you a little. Im new but I have learned a lot already from these forums.
 
After being with Apple Care for 2 hours (2 techs + 1 Supervisor), I must also add myself as no success with a Customer Code. They informed me the code was used to remove the hold on my account. My code generates as the same code each time. I finally gave up and hung up on the supervisor. Hoping this is a temporary problem on their end and we can safely get back to business as usual soon.
 
Do you think the "an error occurred during activation. try again" error is due to Apple's servers having problems? Or is this something on my end (I doubt it since it was working perfectly last time I used it, but I want to hear from someone more knowledgeable)?

Thanks

"An error occurred during activation, try again" up until this point has always been a configuration error between MLB, ROM, SmUUID Serial, and type (model).
 
Back
Top