- Joined
- Jul 29, 2014
- Messages
- 175
- Motherboard
- Gigabyte GA-Z87X-UD5H
- CPU
- i7-4770K
- Graphics
- RX 580
- Mac
-
- Classic Mac
-
- Mobile Phone
-
First, I'm very grateful to Jaymonkey for the guide and others here who have been so helpful. Thank you!
Overview:
1. My build/fix steps
I did a clean, Clover EFI install of Yosemite but couldn't log into iMessages. I had the pop-up with the Customer Code, saying I needed to call Apple.
I have the SID bug on my GA-Z87X-UD5H, so the fix required most the guide.
2. Unblock took overnight to kick in
When Apple lifted the block, I could log in. However, I soon discovered that I couldn't send or receive messages and all contacts were in red. However, when I woke up this morning, it was working. So I guess it just needed some time for the fix to propagate fully. Hooray!
3. My call to Apple
The guide was very helpful here, as you will see. Overall the call took 30 minutes; 15 minutes before I spoke to anyone, and another 15 minutes on the call with the technician, most of which was spent on hold as he researched the problem.
To begin the call, I gave the serial number for my genuine MacBook Air, not my Hackintosh. At no point during the call did they ask for my serial number again. This was different from the last time I called about two months ago, where they refused to help because they couldn't match my Hackintosh serial number.
This technician did not recognize the problem and wanted to do a screen simulcast on my computer. This was bad for several reasons. Fortunately he came back from hold and said that system was down.
He then wanted to walk me through troubleshooting steps. Per the guide, I tried to explain that the problem wasn't with my computer but rather that Apple had put a hold on the account. He asked for the error message and disappeared for several minutes. He then tried to troubleshoot for Yosemite. I explained again, he put me on hold. This happened several times over 15 minutes.
When I finally got his full attention, I said that I had read through the Apple support forums and was fairly sure I knew what the problem was. I then explained the problem was caused by new security measures. All he needed to do was enter my Customer Code number and lift the block. I then read the error message in full.
He put me on hold yet again. When he returned, he directed me to the Apple ID website (which I already had ready). I generated a security number, gave it to him, and he lifted the block. Hooray!
He was very nice and I made sure to be friendly and upbeat. It helped that I was able to direct him to the solution (once I finally got his full attention
.
4. A few notes on the guide
The guide is excellent, comprehensive, and a lifesaver.
Re: Calling Apple to lift the block
If it's not already mentioned, it might be worth noting in bold that even after Apple unblocks you, it may still take several hours or even overnight before you can send and receive messages.
I mention this because I mistakenly assumed that my inability to send/receive messages meant there was still a problem with my settings and continued troubleshooting and nearly shot myself in the foot in the process. (see below)
Clover MLB values
I am using MLB values generated by Clover. Only after getting off the phone with Apple, did I notice that the guide (now) says these Clover-generated values are blocked by Apple. Oops. So I assumed this was my problem. I then changed my MLB values manually. Only then did I notice that I had missed a FaceTime call! So I tried logging into FaceTime only to see the error saying to call Apple and give them the Customer Code! In other words, FaceTime had been working, I didn't realize it, and had now broken it.
So I rolled back my MLB to the Clover-generated values (the ones I had when I called Apple). It worked! I could now log in to FaceTime. But Messages still didn't sent or receive texts. Oh well.
12+ hours later, I picked up where I left off only to discover Messages was now working.
Morals of the story:
Overview:
- my build/fix steps
- unblock took overnight to kick in
- my call to apple
- a few notes on the guide
1. My build/fix steps
I did a clean, Clover EFI install of Yosemite but couldn't log into iMessages. I had the pop-up with the Customer Code, saying I needed to call Apple.
I have the SID bug on my GA-Z87X-UD5H, so the fix required most the guide.
- reset ethernet ports so they were en01 and en02;
- generated a unique serial number that I checked on Apple's website;
- set the computer profile to match the i7 build (iMac 14,2);
- made sure the MLB and ROM etc. did not change after reboots;
- deleted all caches and extensions;
- called Apple to unblock iMessages.
2. Unblock took overnight to kick in
When Apple lifted the block, I could log in. However, I soon discovered that I couldn't send or receive messages and all contacts were in red. However, when I woke up this morning, it was working. So I guess it just needed some time for the fix to propagate fully. Hooray!
3. My call to Apple
The guide was very helpful here, as you will see. Overall the call took 30 minutes; 15 minutes before I spoke to anyone, and another 15 minutes on the call with the technician, most of which was spent on hold as he researched the problem.
To begin the call, I gave the serial number for my genuine MacBook Air, not my Hackintosh. At no point during the call did they ask for my serial number again. This was different from the last time I called about two months ago, where they refused to help because they couldn't match my Hackintosh serial number.
This technician did not recognize the problem and wanted to do a screen simulcast on my computer. This was bad for several reasons. Fortunately he came back from hold and said that system was down.
He then wanted to walk me through troubleshooting steps. Per the guide, I tried to explain that the problem wasn't with my computer but rather that Apple had put a hold on the account. He asked for the error message and disappeared for several minutes. He then tried to troubleshoot for Yosemite. I explained again, he put me on hold. This happened several times over 15 minutes.
When I finally got his full attention, I said that I had read through the Apple support forums and was fairly sure I knew what the problem was. I then explained the problem was caused by new security measures. All he needed to do was enter my Customer Code number and lift the block. I then read the error message in full.
He put me on hold yet again. When he returned, he directed me to the Apple ID website (which I already had ready). I generated a security number, gave it to him, and he lifted the block. Hooray!
He was very nice and I made sure to be friendly and upbeat. It helped that I was able to direct him to the solution (once I finally got his full attention
4. A few notes on the guide
The guide is excellent, comprehensive, and a lifesaver.
Re: Calling Apple to lift the block
If it's not already mentioned, it might be worth noting in bold that even after Apple unblocks you, it may still take several hours or even overnight before you can send and receive messages.
I mention this because I mistakenly assumed that my inability to send/receive messages meant there was still a problem with my settings and continued troubleshooting and nearly shot myself in the foot in the process. (see below)
Clover MLB values
I am using MLB values generated by Clover. Only after getting off the phone with Apple, did I notice that the guide (now) says these Clover-generated values are blocked by Apple. Oops. So I assumed this was my problem. I then changed my MLB values manually. Only then did I notice that I had missed a FaceTime call! So I tried logging into FaceTime only to see the error saying to call Apple and give them the Customer Code! In other words, FaceTime had been working, I didn't realize it, and had now broken it.
So I rolled back my MLB to the Clover-generated values (the ones I had when I called Apple). It worked! I could now log in to FaceTime. But Messages still didn't sent or receive texts. Oh well.
12+ hours later, I picked up where I left off only to discover Messages was now working.
Morals of the story:
- follow the guide *closely*;
- allow up to 12 hours for Apple's block to fully lift before continuing to troubleshoot;
- don't troubleshoot angry.