- Joined
- Jul 29, 2014
- Messages
- 175
- Motherboard
- Gigabyte GA-Z87X-UD5H
- CPU
- i7-4770K
- Graphics
- RX 580
- Mac
- Classic Mac
- Mobile Phone
Jays iMessage Guide
I had iMessages up and running with Clover for several weeks, but it just stopped working late last week. Now I'm getting the following error:
I suspect the problem is that I used Clover to pick my serial number, ROM, and MLB numbers. I only noticed this was contrary to the guide's advice after I had iMessages up and running for a while, so I just stuck with it. But would it really take them this long to blacklist Clover-generated serial numbers?
My ROM, MLB, and serial numbers are still constant, my network remains EN1, etc. Nothing else should have changed.
My best guess is that I should create a new serial number, ROM, and MLB with Chameleon Wizard and give that a try.
But I'm reluctant to ping Apple with yet another new serial numbers etc. unless I'm sure that's the most likely solution. So I figured I'd mention it in case anyone else had experienced something similar, had other theories or ideas for fixes.
Thanks in advance!
I had iMessages up and running with Clover for several weeks, but it just stopped working late last week. Now I'm getting the following error:
"Could not sign into iMessage.
An error occurred during activation. Try again."
An error occurred during activation. Try again."
I suspect the problem is that I used Clover to pick my serial number, ROM, and MLB numbers. I only noticed this was contrary to the guide's advice after I had iMessages up and running for a while, so I just stuck with it. But would it really take them this long to blacklist Clover-generated serial numbers?
My ROM, MLB, and serial numbers are still constant, my network remains EN1, etc. Nothing else should have changed.
My best guess is that I should create a new serial number, ROM, and MLB with Chameleon Wizard and give that a try.
But I'm reluctant to ping Apple with yet another new serial numbers etc. unless I'm sure that's the most likely solution. So I figured I'd mention it in case anyone else had experienced something similar, had other theories or ideas for fixes.
Thanks in advance!