Contribute
Register
Not sure r3021 is the culprit here, been using it with new injection method and it's rock stable, upgraded to 10.0.1 same.

Now for the dual injection...yeah it's odd I would opt for one or the other.
 
I'm still not convinced that Apple has done anything to the iMessage Lock Code system, other than possible breakage due to their associated issues that occurred on 10.10.1's release. iMessage unlock requests are extremely rare for the average Apple Specialist let alone the consumer. I have spoken with a person in the know that each individual Apple ID is allowed a minimum of 2 iPhones, 2 iPads and 5 Macs, before the system even considers requiring iMessage re-registration of the Apple ID. In most cases those who are calling on iMessage Activations have hundreds of serial numbers associated with their ID, probably due to bad installs utilizing new randomly generated serials.

If you see "Waiting for Activation", "Activation unsuccessful", or "An error occurred during activation", Apple recommends waiting 24 hours prior to re-trying. This is purely a provisioning issue, where some of the servers are not actually synced up completely.

A word of caution:

Continuing to contact Apple to resubmit an ever changing iMessage Activation Code, for what should be a 'static' same code only message, possibly result in banning that ID permanently.
 
Has anyone had iMessage randomly stop working in the last day or so? I've had it running beautifully ever since Yosemite came out with the newer Clover method. All of a sudden though, it signed me out of iMessage (my contacts were all showing up as offline, and my account says inactive in preferences.)

Trying to log back in hits an error that says "An error occurred during activation, please try again". I've verified that all of the proper values are still in Clover, etc.

It's also worth noting that I'm still signed into iCloud.

Edit: I had clicked page 101 thinking it was the last page and just saw that clearly something's up. Please ignore the ignorant post.

This is the same problem I'm experiencing. My iMessages had been working since mid-to-late October until about 10 days ago, when it just mysteriously stopped working. No changes were made to the system (I haven't updated to 10.10.1 yet), no fiddling Clover, nothing. It just stopped working.

Last night I tried changing the Password to my AppleID. That slightly worked; I was able to log into iMessages for the first time in almost two weeks. However, I couldn't send or receive messages. I hoped it just needed time to propagate (when I called Apple to unblock my iMessages in October, it took a day before it started working). Unfortunately, this morning, I could no longer log in, so I'm back to square one.

Presumably Apple has done something on their side.

The one caveat is that I used Clover to generate my ROM/MLB values, etc. contrary to what the guide suggested (I hadn't noticed the updated advice until several days after I had everything up and running, so I just let it be. So it's possible it took Apple 3+ weeks to block bad values, but I'm skeptical it would take so long).

P.S. My Clover version is r2953, so I don't think that's it either.
 
So, as said, I installed Clover v2999 as it was, without customizing anything. Ethernet cable out and reboot.
Mounted EFI, loaded config and went to SMBIOS to create a new serial. Checked it on the site. Used uuigen, pasted it on the SmUUID field of SMBIOS, copied the last 12 characters and pasted it on the ROM field in the Rt Variables tab.
Got the Serial Number I generated that was on the Serial Number field on the SMBIOS tab, added a couple letters so it's 17 characters long and pasted it on the MLB field on Rt Variables. So on SMBIOS the Board Serial Number is not blank, Serial Number and SmUUID are filled. Saved.
Deleted the iMessage files.
Reboot.
Ran iMessage debug 2, all good.
Plug ethernet. Try to log in. Customer code, different one obviously.
 
So, as said, I installed Clover v2999 as it was, without customizing anything. Ethernet cable out and reboot.
Mounted EFI, loaded config and went to SMBIOS to create a new serial. Checked it on the site. Used uuigen, pasted it on the SmUUID field of SMBIOS, copied the last 12 characters and pasted it on the ROM field in the Rt Variables tab.
Got the Serial Number I generated that was on the Serial Number field on the SMBIOS tab, added a couple letters so it's 17 characters long and pasted it on the MLB field on Rt Variables. So on SMBIOS the Board Serial Number is not blank, Serial Number and SmUUID are filled. Saved.
Deleted the iMessage files.
Reboot.
Ran iMessage debug 2, all good.
Plug ethernet. Try to log in. Customer code, different one obviously.

Got exactly same thing. Im calling apple support again now
 
So, as said, I installed Clover v2999 as it was, without customizing anything. Ethernet cable out and reboot.
Mounted EFI, loaded config and went to SMBIOS to create a new serial. Checked it on the site. Used uuigen, pasted it on the SmUUID field of SMBIOS, copied the last 12 characters and pasted it on the ROM field in the Rt Variables tab.
Got the Serial Number I generated that was on the Serial Number field on the SMBIOS tab, added a couple letters so it's 17 characters long and pasted it on the MLB field on Rt Variables. So on SMBIOS the Board Serial Number is not blank, Serial Number and SmUUID are filled. Saved.
Deleted the iMessage files.
Reboot.
Ran iMessage debug 2, all good.
Plug ethernet. Try to log in. Customer code, different one obviously.

Sounds promising. Thank you for the update and rundown of the steps. Let us know if it works! :)

FWIW last time I called Apple, it took a day before the block lifted.
 
Got exactly same thing. Im calling apple support again now

They are clossing here in 20 seconds, so I guess if it works for you I'll call tomorrow. Tell us if it works, by chance.
 
They are clossing here in 20 seconds, so I guess if it works for you I'll call tomorrow. Tell us if it works, by chance.

As I live in Serbia, and we dont have apple official support I have to call USA support with skype, Im calling number +18002752273 , I guess they work all the time. :D Its free btw
 
They have tried to fix it, but still not working.. After that they transfered my call to Supervisor and he told me to wait so he can check something, after that my call just dropped out. I will call them again later today, as I dont want to wait again now for 30+ minutes for operater.:crazy:
 
Back
Top