How to Fix iMessage

[deke]

Hey guys ! I called Apple this afternoon to fix the customer code error. That i said :
There's a problem with my MacBook Pro (say your fake model, serial, and apple id.)
Say imessage worked before, and since an update (10.9.5 if you want), imessage stopped working.
Say you had nvram problems and reset it reseted your UUID, and Apple thinked, after reboot, that your hackintosh was a new mac. So you reached the limit of devices that can be linked to your Apple ID. Ask to the men it he can reset your account linked macs. Say you heard somewhere it can solve the issue. He will say he needs a conformation code : it's the customer code iMessage gives with the error. Give it to the man. He will reset your account and iMessage and Facetime will work instantly, of course if you have working NVRAM.
EDIT :After you did it, save your serial, mlb, rom and uuid somewhere to use it everytime you reinstall OSX. Dont connect your hackintosh to your Apple ID if these serials are not active. So, save clover config plist somewhere in icloud, dropbox, to use it later if you install yosemite for example
EDIT 2 : When i gave the serial to the Apple man, he said the Macbook was purshased in Japan. I answered i bought it on ebay few months ago. That was ok for the man.

PS : New iPad introduce is tomorrow, stay tuned

 

[MysticalOS]

Yes that is my plan, once i figure out how to get nvram file to stop changing rom every reboot. I may try 1.1.2 and see, even though chameleon 2401 comes with 1.1.3. I do have latest BIOS already.

 

[deke]

Yes that is my plan, once i figure out how to get nvram file to stop changing rom every reboot. I may try 1.1.2 and see, even though chameleon 2401 comes with 1.1.3. I do have latest BIOS already.

**** off filenvram use clover it's 1000 times better ^^ in clover configurator; RT Variables, choose your rom (tip : rom = en0 mac adress )
And mlb choose what you want i don't know.
If you've the customer error message, use my tip

 

[MysticalOS]

I tried everything imaginable from 5d and more. filevnram ALWAYS generates a new rom. also my board does NOT have SiD bug, it's always same SiD without hacking that, so that's a plus. However, aside from maybe writing an applescript that fires on startup to write to nvram every bootup to force consistent rom, i can't find any other workable solution. Unless it's possible to put rom IN the smbios.plist so nvram just reads that instead of auto generates a random one every boot?

 

[Kris404]

EDIT 2 : When i gave the serial to the Apple man, he said the Macbook was purshased in Japan. I answered i bought it on ebay few months ago. That was ok for the man.

This is the equivalent of "I was adopted"

 

[jaymonkey]

I tried everything imaginable from 5d and more. filevnram ALWAYS generates a new rom. also my board does NOT have SiD bug, it's always same SiD without hacking that, so that's a plus. However, aside from maybe writing an applescript that fires on startup to write to nvram every bootup to force consistent rom, i can't find any other workable solution. Unless it's possible to put rom IN the smbios.plist so nvram just reads that instead of auto generates a random one every boot?

@MysticalOS,

The only time i've seen or heard of this behaviour (if your 100% sure about MLB & ROM ..etc) is that you may have another - possible hidden /Extra and /or nvram.uuid.plist folder sitting somewhere on anther drive or usb stick, even external drive ... this can confuse chimera and/or chameleon during boot using the settings in the other location.

Might be worth a check .....

Failing that make the jump to clover ... its not that far ....

Cheers
Jay

 

[odds]

Welp, I had iMessage working flawlessly in Mavericks using FileNVRAM.dylib. Unfortunately, after upgrading to Yosemite, imessage_debug no longer shows ROM and MLB values. Instead, it reports "failed" for each. I tried deleting my old NVRAM plist file that existed in my Extra folder so that FileNVRAM.dylib might generate new values, but that didn't work. I have not tried inject ROM and MLB values manually, though that is what I may try if a new version of FileNVRAM.dylib is not released soon.

How is everyone else doing now that they're running Yosemite?

 

[MysticalOS]

You're not far off is right Jay. Between this and now 10.10 has NO nvram cause file nvram doensn't work. 10.10 is perfect time for a clean install of clover and 10.10 going forward. then go from there

 

[odds]

Can you confirm working NVRAM/iMessage with Clover and 10.10?

 

[MysticalOS]

Can you confirm working NVRAM/iMessage with Clover and 10.10?

I'm sure i'll find out soon, but still waiting on 10.10 download. about 3 more hours. country internet. :\