Contribute
Register

How to Fix iMessage

Continuation from #405 and answer to #406

Those last #c were indeed different one from another.
My Hardware UUID is always the same after a fresh install.
Based on these 2 facts, I assume I am not impacted by the SID bug.

I just called Apple support, they said they activated the device which the Customer Code was generated for. Fingers crossed for now.

UPDATE:
I can confirm that calling Apple Support fixed the issue. Apparently devices get blocked by their servers. There must be some sort of certification that Hacks can't deal with (as I was able to login from a real Mac).

Please bare in mind that until you don't have that "Customer Support" number, they won't help you so you need to get at least until the point where you get this code from iMessage. Following the initial steps from the 1st post and then in How to Fix iMessage-Part2 was enough to get there. Then I called them. I gave them the number and they said they activated iMessage for use with that device.

They seem to have some console where they see the support number, they see the device (most likely an UUID) and they have the option to activate iMessage for that device specifically.

They wouldn't say more about what could be the cause of the issue. Most probably a security measure.

Update 2:
OK guys, let's call the UUID on which I got iMessage activated by Apple support, the Magic UUID.
What I did was to use the Magic UUID on a fresh install:

add to org.chameleon.Boot.plist
Code: 
<key>SystemId</key>
<string>********-****-****-****-************</string>
Worked without issues. The HW UUID and Platform UUID became the same as the test install.

Worth to mention: I basically copied the Extra folder from the test install on the fresh install (I'm using 2 HDDs for this) which as well copied the nvram.xxxxxx.plist. There must be something in there as well that impacts the final result. Going to quickly delete it and see what happens.

UPDATE 3:

I deleted the old nvram.xxxxx.plist and changed the SN and iMessage still works. After a comparison I can see that the new nvram.xxxx.plist has the same content as the old one (although differently structured but the content is the same).

My conclusion: In my case, If I perform a fresh install, to get iMessage to work without calling Apple support again I need to do the following:


  1. Fresh install by using Unibeast+MultiBeast
  2. use the "Magic UUID" in org.chameleon.Boot.plist;
  3. have FileNVRAM (the recommended version) module in my /Extra/modules/ folder;
  4. reboot;
  5. enjoy.

@jay, I leave it up to you to consolidate this information. The bottom line is that without FileNVRAM iMessage will not work. As well (and that's just a theory) if your ID has simply too many UUIDs associated with it, Apple support needs to authorise the device you are currently using.
 
Mac Pro Mainstream
X79 EXTREME4 |  Xeon E5-1650 v2 |  GeForce GTX 760
Klorin said:
@3square

double-check that you added your SystemId correctly to org.chameleon.Boot.plist

<key>SystemId</key>
<string>the id from random generator here</string>

try boot with:

<key>UseKernelCache</key>
<string>No</string>
Click to expand...

it is correct. i can see in the boot log that it is injected.
i might try calling customer support later today.
thanks
 
icezar said:
My conclusion:[/B] In my case, If I perform a fresh install, to get iMessage to work without calling Apple support again I need to do the following:


  1. Fresh install by using Unibeast+MultiBeast
  2. use the "Magic UUID" in org.chameleon.Boot.plist;
  3. have FileNVRAM (the recommended version) module in my /Extra/modules/ folder;
  4. reboot;
  5. enjoy.
Click to expand...


so… fresh install in the test drive and use the Magic UUID in the fresh install to place that into our current install?

i rather not do a fresh install to my current install at all, that's what i'm trying to see.
Also the above method is without having to call apple support at all?
 
3square said:
so… fresh install in the test drive and use the Magic UUID in the fresh install to place that into our current install?

i rather not do a fresh install to my current install at all, that's what i'm trying to see.
Also the above method is without having to call apple support at all?
Click to expand...

I didn't want to perform a fresh install either so what I did was to copy the Extra folder from the test drive to the main one and like magic, the uuid changed in system profiler and iMessage started to work.

You need to call apple to activate your device once you get to the point where iMessage tells you to do so and gives you that Customer Support code. I think for US they might have an online chat option if you prefer to use that. I'm not sure though.

so
  1. Follow the instructions in the first post
  2. Create an UUID
  3. add it to the boot plist
  4. copy the FileNVRAM to modules folder
  5. reboot
  6. login to iMessage
  7. Call apple and pass them the Customer Support code
  8. they activate it
  9. keep that UUID that you generated safe
  10. on fresh install follow the steps I mentioned previously

If you have the customer support code now, you only need to call them.
 
Mac Pro Mainstream
X79 EXTREME4 |  Xeon E5-1650 v2 |  GeForce GTX 760
Wolfie81 said:
Thank you very much!

iMessage WORKS!!

For a quick guide until JayMonkey updates post and for other users its a easy fix.

1. Open your system profiler. Go to Apple symbol top left corner - about this mac/more info/system report.
In hardware (first line on left column) there is 'Hardware UUID' with 5 blocks of text separated by a dashed line. Copy that somewhere or take note of it.

2. Open your org.chameleon.boot.plist and add at bottom of the key and string texts enter the following into the file with the appropriate UUID number as seen below.

<key>SystemId</key>
<string>INSERT UUID number here</string>

</dict>
</plist>

3. Save file, and reboot.

Upon reboot you will be immediately promoted to enter your iCloud, Mail accounts, cloud accounts, FaceTime, iMessage passwords and possibly some others.
Click to expand...

I am a little late to the party, but doing exactly that fixed iMessage for me, without any reinstallation, NVRAM change what so ever. I only had to reboot and voila.

Thanks guys!
 
icezar said:
@jay, I leave it up to you to consolidate this information. The bottom line is that without FileNVRAM iMessage will not work. As well (and that's just a theory) if your ID has simply too many UUIDs associated with it, Apple support needs to authorise the device you are currently using.
Click to expand...

@icezar

Many thanks for your post's, what you have described is how i see it as detailed in How to Fix iMessage - Part 2,

I'm confident now on how to write this up in the main guide but in essence:-

1. Check for SID bug, if true inject SystemId using the procedure in How to Fix iMessage - Part 2.

2. Complete iMessage check list as per main guide.

3. If iMessage still does not work and displays a dialogue box with Contact Apple with a Customer code then you need to do this as your AppleID has basically been flagged with a UUID and/or S/N miss-match. The customer code basically authenticates the reset of the flag on your AppleID - it does matter if hackingtosh - customer code validates the request.

Cheers
Jay
 
icezar said:
Jay, I'm with you on that new Apple ID thought. I actually logged in with another ID and it worked while my main iCloud one did not. That made me believe that most likely, without a call to Apple, my ID won't work on my Hack.
Click to expand...

good to know. thanks for narrowing that down.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top