Jump to content

iMessage not working - iCloud/Internet etc working - Changed boot.plist file and network.plist file - Help


  • Please log in to reply
419 replies to this topic

#341
cosmo1t

cosmo1t

    InsanelyMac Protégé

  • Developers
  • 98 posts
  • Gender:Male
actually, just

[font='courier new', ', courier, monospace} ']sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=f1:2a:14:52:9a:[/font][font="Verdana, Geneva, sans-serif"]60[/font]

[font='courier new', ', courier, monospace} ']it should be base64 encoded[/font]

[font="courier new, , courier, monospace}"]I think[/font]


#342
dmazar

dmazar

    InsanelyMac Sage

  • Coders
  • 274 posts
  • Gender:Male
No, no. It's not base 64. It's %HexHex for one byte and if byte is printable character, then this character can be used. Just look how it prints other vars.

#343
Toonces Katt

Toonces Katt

    InsanelyMac Protégé

  • Members
  • PipPip
  • 63 posts
  • Gender:Male

Ok two things. First, what version of OSX are you running? Second, i thought the MLB was supposed to be 17 characters but yours is 16. Lets try changing it, reboot and try iMessage again.

sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK916531XYL123456

If it still doesn't work, run imessage_debug again and make sure the MLB is the correct length.


Sorry for the delay in replying. I am running 10.8.1 booting with Chameleon 2170 installed from earlier in the thread.

Still not working, I entered 17 digits when I did the nvram command previously and it looks like things change between putting it in and rebooting.

Here's iMessage_debug:


localhost:Desktop erik$ nvram -xp
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key>
<data>
Q0s5MTY1MzFYWUwxMjM0NTYA
</data>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM</key>
<data>
MDAwNjRmNDliZTg2
</data>
<key>IOPowerManagement</key>
<dict>
<key>CurrentPowerState</key>
<integer>1</integer>
<key>MaxPowerState</key>
<integer>1</integer>
</dict>
<key>IOPowerManagement:CurrentPowerState</key>
<data>
AAAAAA==
</data>
<key>IOPowerManagement:MaxPowerState</key>
<data>
AAAAAA==
</data>
<key>boot-args</key>
<data>
IC12IC1mAA==
</data>
<key>boot-gamma</key>
<data>
rBAAAC6gAABVTkMxtgAAAAAAAAANAAEB4wQCAgUIBAQpDQcHoRMODjQgGBhULyMj+D0w
MKdNPT0nXE5O121ycguQmpqQssnJ+9cNAAEB4wQCAgUIBAQpDQcHoRMODjQgGBhULyMj
+D0wMKdNPT0nXE5O121ycguQmpqQssnJ+9cNAAEB4wQCAgUIBAQpDQcHoRMODjQgGBhU
LyMj+D0wMKdNPT0nXE5O121ycguQmpqQssnJ+9esEAAAPEAAAFMyRkO2AAAAAAAAAA0A
AQHjBAICBQgEBCkNBwehEw4ONCAYGFQvIyP4PTAwp009PSdcTk7XbXJyC5CampCyycn7
1w0AAQHjBAICBQgEBCkNBwehEw4ONCAYGFQvIyP4PTAwp009PSdcTk7XbXJyC5CampCy
ycn71w0AAQHjBAICBQgEBCkNBwehEw4ONCAYGFQvIyP4PTAwp009PSdcTk7XbXJyC5Ca
mpCyycn716wQAABCQAAATDI3MbYAAAAAAAAADQABAeMEAgIFCAQEKQ0HB6ETDg40IBgY
VC8jI/g9MDCnTT09J1xOTtdtcnILkJqakLLJyfvXDQABAeMEAgIFCAQEKQ0HB6ETDg40
IBgYVC8jI/g9MDCnTT09J1xOTtdtcnILkJqakLLJyfvXDQABAeMEAgIFCAQEKQ0HB6ET
Dg40IBgYVC8jI/g9MDCnTT09J1xOTtdtcnILkJqakLLJyfvX
</data>
</dict>
</plist>


Here's what I did and where I see a change.

1. sudo nvram -d 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
2. sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK916531XYL123456
3. nvram -xp

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key>
<data>
Q0s5MTY1MzFYWUwxMjM0NTY=
</data>

4. reboot
5. nvram -xp
localhost:Desktop erik$ nvram -xp
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">
<plist version="1.0">
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key>
<data>
Q0s5MTY1MzFYWUwxMjM0NTYA
</data>


Not sure if that has anything to do with it but the value changes after the reboot.

Thanks Again!

#344
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,944 posts
  • Gender:Male
Toonces Katt, what exactly happens when you try to log in?

#345
rcork

rcork

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 167 posts
what do you get when you execute:

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB



@Toonces - also might be worthwhile trying to use a different system definition like iMac12,2. If you do try that, you'd need to follow the same procedure to disable the module, delete nvram.plist, change system definition, reinstall module and let it recreate the nvram.plist.

#346
antipop2323

antipop2323

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts

Just a note: ROM is suppose to contain MAC address of your primary network card. Although, it seems it's not important at all for now.

But, if you still want to set ROM to your MAC address, then do it like this: if MAC address is f1:2a:14:52:9a:60 (note: it's 6 bytes) then do
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%f1%2a%14%52%9a%60


i tried this and in my plist ROM looks like <12eg487e 506e>

is that how it should look in plist?

#347
dmazar

dmazar

    InsanelyMac Sage

  • Coders
  • 274 posts
  • Gender:Male
if you open plist in plist editor, then you should get your MAC address (6 bytes) inside < and >. Your example above looks ok, except it has letter 'g' which is not possible - not a hex digit.

But again, from the current user experience, ROM value must be present but it's not required to be MAC address to sign in to iMessage. For now.

#348
antipop2323

antipop2323

    InsanelyMac Protégé

  • Members
  • Pip
  • 48 posts

if you open plist in plist editor, then you should get your MAC address (6 bytes) inside < and >. Your example above looks ok, except it has letter 'g' which is not possible - not a hex digit.

But again, from the current user experience, ROM value must be present but it's not required to be MAC address to sign in to iMessage. For now.


ok, well i just made up the #s, but that's more or less what mine looked like heh... it did create a space though, so it appeared like <12ef487e 506e> /shrug

#349
Toonces Katt

Toonces Katt

    InsanelyMac Protégé

  • Members
  • PipPip
  • 63 posts
  • Gender:Male

Toonces Katt, what exactly happens when you try to log in?


I go through authentication it gets to the next screen of activating iMessage then gives the message "Could not sign in to iMessgae/ The server encountered an error processing registration. Please try again later."

Same message I was getting since the iMessage beta ended.

I am able to get in using Clover but would much rather use Chameleon.

what do you get when you execute:

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB



@Toonces - also might be worthwhile trying to use a different system definition like iMac12,2. If you do try that, you'd need to follow the same procedure to disable the module, delete nvram.plist, change system definition, reinstall module and let it recreate the nvram.plist.


I get 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK916531XYL123456

I'll give iMac 12,2 a try and see if that makes a difference.

what do you get when you execute:

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB



@Toonces - also might be worthwhile trying to use a different system definition like iMac12,2. If you do try that, you'd need to follow the same procedure to disable the module, delete nvram.plist, change system definition, reinstall module and let it recreate the nvram.plist.


I followed your instructions above and removed the model, reboot, remove nvram.plist (both), changed to iMac 12,2 reboot, reinstall module and it created nvram.plist. I tried to sign in and got the same error. Pic shows nvram -xp, iMessage_debug & 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB output.

Attached File  Screen Shot 2013-01-23 at 3.57.40 PM.png   562.13KB   167 downloads

I'll boot up in Clover and try to run some comparisons to the values I have under that. Maybe something with my hardware is treaded differently? I do have a PCI gigabit ethernet card (eth0) the only card that is actually recognized by the system as the built in is disabled in BIOS and I don't load the kext for it. Though I suspect that shouldn't really matter since the primary card is the one that is being used and it works under Clover.

Thanks Again, for your assistance!


Update: I set the same values I found in Clover and still not getting in except with Clover. Attached are the screenshots of the relevant output.

Clover: Attached File  Screen Shot 2013-01-23 at 4.48.50 PM - Clover.png   518.08KB   204 downloads

CHameleon: Attached File  Screen Shot 2013-01-23 at 5.14.19 PM - CHameleon 2170.png   565.24KB   134 downloads

After comparing the two outputs, I even changed the serial via sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02HK578DHJP7E1I1 and still not able to get in.

iMessage_debug output after the change:


localhost:Desktop erik$ sudo ./imessage_debug
2013-01-23 17:22:26.479 imessage_debug[373:a07] Gq3489ugfi: <4176ffdf af516d90 07c9854b 6145ed56 ff>
2013-01-23 17:22:26.481 imessage_debug[373:a07] Fyp98tpgj: <8d94ca87 3b8d86b9 9f60c03c 800c87de 4c>
2013-01-23 17:22:26.481 imessage_debug[373:a07] kbjfrfpoJU: <d8f48566 3454c887 bec9ea22 9059be4a 9e>
2013-01-23 17:22:26.482 imessage_debug[373:a07] IOPlatformSerialNumber: W80CF65ADHJF
2013-01-23 17:22:26.482 imessage_debug[373:a07] IOPlatformUUID: 371A61AF-D774-58C5-870D-82C4D7054ED8
2013-01-23 17:22:26.483 imessage_debug[373:a07] board-id: Mac-942B5BF58194151B
2013-01-23 17:22:26.484 imessage_debug[373:a07] product-name: iMac12,1
2013-01-23 17:22:26.484 imessage_debug[373:a07] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <00000000 00000000 00000000 000000>
2013-01-23 17:22:26.485 imessage_debug[373:a07] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02HK578DHJP7E1I1
2013-01-23 17:22:26.485 imessage_debug[373:a07] oycqAZloTNDm: <c32e324e 39692550 a7909594 d43fc4af c1>
2013-01-23 17:22:26.486 imessage_debug[373:a07] abKPld1EcMni: <589311eb 31fb5e70 f471a5d3 46206890 4d>

#350
nyolc8

nyolc8

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 802 posts
  • Gender:Male
  • Location:Budapest, Hungary
If I change MLB value with the nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK111111XYL123456 command, and I check the data with nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB, I get this:
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK111111XYL123456

If I restart, and check the data again with nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB, I get this:
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK111111XYL123456%00

So a "%00" added to the end. Same thing happens with ROM value on restart. Is this normal?

(The serial is just example in my post, I use valid serial.)

#351
mcdougal33

mcdougal33

    InsanelyMac Protégé

  • Members
  • PipPip
  • 99 posts
  • Gender:Male

I have lion on my mba (work laptop) so no imessage. Am I stuck?


I'm getting the same error as you and like you, I also only have access to a 10.7 mac. I wish I knew what to do. I've tried signing in to icloud and facetime on my mac and that doesn't seem to help. Funny thing is my wife's appleid works fine on my hack for imessage. I even created a new appleid for myself and still got the same error with that.

#352
dgrx

dgrx

    InsanelyMac Protégé

  • Donators
  • 75 posts
  • Gender:Not Telling
Thanks to all involved :thumbsup_anim:
Everything working good again.

#353
mendietinha

mendietinha

    mendi

  • Members
  • PipPipPipPipPipPipPip
  • 835 posts
  • Gender:Male
  • Interests:full hackintosh.
i've try to log in into a real mac to fix the call support error in imessage, but it didnt work. i log in 2 times but didnt solve the problem. can anyone help me here? try to change the password too without any results.

thanks!

#354
eep357

eep357

    Triple Platinum

  • Retired
  • 2,527 posts
  • Gender:Male
  • Location:Dark Side of The Wall
  • Interests:things and stuff

If I change MLB value with the nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=CK111111XYL123456 command, and I check the data with nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB, I get this:

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK111111XYL123456

If I restart, and check the data again with nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB, I get this:
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK111111XYL123456%00

So a "%00" added to the end. Same thing happens with ROM value on restart. Is this normal?

(The serial is just example in my post, I use valid serial.)

Are you using newer mac model in smbios with 12 digit serial?

i've try to log in into a real mac to fix the call support error in imessage, but it didnt work. i log in 2 times but didnt solve the problem. can anyone help me here? try to change the password too without any results.

thanks!

Credit card linked to account? This seems to be the key for others with this problem.

#355
froalskiner

froalskiner

    InsanelyMac Protégé

  • Members
  • Pip
  • 14 posts
  • Gender:Male
  • Location:93003
Where do you check for that? ITunes? Mine is already linked but ill try changing to another card.

#356
nyolc8

nyolc8

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 802 posts
  • Gender:Male
  • Location:Budapest, Hungary

Are you using newer mac model in smbios with 12 digit serial?

I'm using macpro3,1, it has 11 digit serial. So this fix is only for newer mac models? Or it should work with this %00, just leave it as it?

#357
cosmo1t

cosmo1t

    InsanelyMac Protégé

  • Developers
  • 98 posts
  • Gender:Male
the %00 is irrelevant. when u initally set it , it's a String, it then gets saved to the file as Data, so the next time u print it u see the %00 ie '\0' the null terminator.
if u look @ it in

ioreg -p IODeviceTree -lw0

search for options

you'll notice it's the same. The data values are the exact same, this entire idea about the %00 mattering is not valid.

#358
mcdougal33

mcdougal33

    InsanelyMac Protégé

  • Members
  • PipPip
  • 99 posts
  • Gender:Male

Are you using newer mac model in smbios with 12 digit serial?

Credit card linked to account? This seems to be the key for others with this problem.


Thanks! This did the trick for me. No more contact support error. I'm not even sure how adding a credit card could solve this but it sure does.

#359
dzj

dzj

    InsanelyMac Protégé

  • Members
  • Pip
  • 9 posts
  • Gender:Male
  • Location:Germany
  • Interests:Basic Research - Biology, Chemistry, Physics, Technology
Adding credit card info does not solve this for me. Also, the output of

ioreg -lw0 | grep PlatformUUID

in terminal changes occasionally (already twice since Tuesday). It should remain the same, not? I have a recent MBP (2011) and two MacMini, late 2009 and late 2012, which work with the same Apple_ID. I can sign in and out without problems with these and with an iPhone 4S, ios 6.01, (all with the same apple_id).

PS: It worked for me for a brief time last Monday. Since Monday evening I get "contact support" most of the time, but sometimes it just says that its currently not possible to sign in (while it works on all systems, but this hacked MacPro from 2006).

PPS:


$ ./imessage_debug
2013-01-25 18:26:25.844 imessage_debug[1088:707] Gq3489ugfi: <cecef0c3 115fe1c5 5a3d9897 4b1462f1 25>
2013-01-25 18:26:25.847 imessage_debug[1088:707] Fyp98tpgj: <ed820c68 505735b2 86f3f590 d6f08ad9 20>
2013-01-25 18:26:25.848 imessage_debug[1088:707] kbjfrfpoJU: <ce09187e 0277aa7a 1da4cd3b 5ab8cc74 cf>
2013-01-25 18:26:25.849 imessage_debug[1088:707] IOPlatformSerialNumber: C11DIGITSNO
2013-01-25 18:26:25.850 imessage_debug[1088:707] IOPlatformUUID: D69F6069-B89B-5984-8BAA-BCC663A59FFB
2013-01-25 18:26:25.851 imessage_debug[1088:707] board-id: Mac-F4208DC8
2013-01-25 18:26:25.851 imessage_debug[1088:707] product-name: MacPro2,1
2013-01-25 18:26:25.852 imessage_debug[1088:707] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <0127fa03 fe5f>
2013-01-25 18:26:25.853 imessage_debug[1088:707] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C11DIGITSNO5OY18
2013-01-25 18:26:25.854 imessage_debug[1088:707] oycqAZloTNDm: <342ef921 9614c2e6 7bda55f1 90187be5 d4>
2013-01-25 18:26:25.854 imessage_debug[1088:707] abKPld1EcMni: <c54ba9d8 17fa4365 6476e8b0 b7b9ed1d 1c>

#360
eep357

eep357

    Triple Platinum

  • Retired
  • 2,527 posts
  • Gender:Male
  • Location:Dark Side of The Wall
  • Interests:things and stuff

Adding credit card info does not solve this for me. Also, the output of

ioreg -lw0 | grep PlatformUUID

in terminal changes occasionally (already twice since Tuesday). It should remain the same, not? I have a recent MBP (2011) and two MacMini, late 2009 and late 2012, which work with the same Apple_ID. I can sign in and out without problems with these and with an iPhone 4S, ios 6.01, (all with the same apple_id).

PS: It worked for me for a brief time last Monday. Since Monday evening I get "contact support" most of the time, but sometimes it just says that its currently not possible to sign in (while it works on all systems, but this hacked MacPro from 2006).

PPS:


$ ./imessage_debug
2013-01-25 18:26:25.844 imessage_debug[1088:707] Gq3489ugfi: <cecef0c3 115fe1c5 5a3d9897 4b1462f1 25>
2013-01-25 18:26:25.847 imessage_debug[1088:707] Fyp98tpgj: <ed820c68 505735b2 86f3f590 d6f08ad9 20>
2013-01-25 18:26:25.848 imessage_debug[1088:707] kbjfrfpoJU: <ce09187e 0277aa7a 1da4cd3b 5ab8cc74 cf>
2013-01-25 18:26:25.849 imessage_debug[1088:707] IOPlatformSerialNumber: C11DIGITSNO
2013-01-25 18:26:25.850 imessage_debug[1088:707] IOPlatformUUID: D69F6069-B89B-5984-8BAA-BCC663A59FFB
2013-01-25 18:26:25.851 imessage_debug[1088:707] board-id: Mac-F4208DC8
2013-01-25 18:26:25.851 imessage_debug[1088:707] product-name: MacPro2,1
2013-01-25 18:26:25.852 imessage_debug[1088:707] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <0127fa03 fe5f>
2013-01-25 18:26:25.853 imessage_debug[1088:707] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C11DIGITSNO5OY18
2013-01-25 18:26:25.854 imessage_debug[1088:707] oycqAZloTNDm: <342ef921 9614c2e6 7bda55f1 90187be5 d4>
2013-01-25 18:26:25.854 imessage_debug[1088:707] abKPld1EcMni: <c54ba9d8 17fa4365 6476e8b0 b7b9ed1d 1c>

No it should not change. That is one of 2 issues....MacPro 2,1? That maybe also a problem. Mountain Lion is not officially supported to run on MacPro 1,1 or 2,1, therefore your telling Apple that messages shouldn't be able to work while still trying to use it at the same time. The credit card thing, I believe applies most often to those who have no iOS device and only have free apple ID not tied to a device, not certain on that bit.

Nyloc8-No both are fine, listen to Cosmo1t, sorry to confuse

On a side not, I just learned that VMware running seems to cause message problems as well, or just did for me at least, fine again after reboot





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy