Jump to content

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

hamzab

By hamzab,
in OSx86 10.8 (Mountain Lion)

 Share
418 posts in this topic

Recommended Posts

rcork
rcork
Posted
Posted

Works great here. At first boot it generated the nvram plist but i noticed that the ROM was all zeros. Although not a big deal and iMessage still works, i wanted ROM to be equal to the MAC address of en0 so i updated with nvram and after next boot it now is the correct value.

 

Glad i can stop using Clover and go back to Chameleon. While Clover is interesting, it's still early in its development and is going through to many underlying changes to keep track of. Plus, Chameleon loads much faster than Clover was (at least for me using UEFI boot). No offense to the Clover dev team.

Link to comment
Share on other sites
meklort
meklort
Posted
Posted

Thanks!, sudo lets me enter the values but it enters them into /Extra/nvram.44454c4c-5400-1037-8058-b1c04f544631.plist. My UUID is supposed to be "371A61AF-D774-58C5-870D-82C4D7054ED8" according to ioreg so I don't understand why the difference. Is there a way I am supposed to enter the UUID I got from ioreg?

The UUID is read out form your machine's SMBios, we used the value in the bios and not the overwritten value, so it may be different if you have manually specified a uuid / system id somewhere.

 

Manually specifying the plist path is not supported.

Link to comment
Share on other sites
Toonces Katt
Toonces Katt
Posted
Posted

I don't know why but when I use the uuid from ioreg, it gives me the value 371A61AF-D774-58C5-870D-82C4D7054ED8. When I delete the nvram.plist and the one in Extra, it creates new ones with a different UUID, 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 and populates nvram with that. I've had up to 3 different UUID:MLB combinations in nvram at the same time according to nvram -p and still get the server error message from iMessage.

 

This last time I went through and deleted all of the nvram UUID except for 371A61AF-D774-58C5-870D-82C4D7054ED8:MLB & ROM entries and got 2 kp in a row. on the 3rd boot, it booted but now has 2 UUID:MLB & ROM entries for the 2 UUID's above.

Link to comment
Share on other sites
rcork
rcork
Posted
Posted

I don't know why but when I use the uuid from ioreg, it gives me the value 371A61AF-D774-58C5-870D-82C4D7054ED8. When I delete the nvram.plist and the one in Extra, it creates new ones with a different UUID, 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 and populates nvram with that. I've had up to 3 different UUID:MLB combinations in nvram at the same time according to nvram -p and still get the server error message from iMessage.

 

This last time I went through and deleted all of the nvram UUID except for 371A61AF-D774-58C5-870D-82C4D7054ED8:MLB & ROM entries and got 2 kp in a row. on the 3rd boot, it booted but now has 2 UUID:MLB & ROM entries for the 2 UUID's above.

 

My NVRAM file has the UUID of 00020003-0004-0005-0006-000700080009 (file is named nvram.00020003-0004-0005-0006-000700080009.plist). This looks to be faked value. When i export PlatformUUID fro ioreg, i get 55ADE930-5FDF-5EC4-8429-15640684C489. Doesn't look to be impacting anything but wanted to report it in case it's a bug.

 

Also, usually when you execute nvram -p you don't see the MLB and ROM (verified on a hack running clover and on a real mac) but when i'm using this Chameleon fix, it prints out. Not sure if it should be there or not. Without seeing the source code for the nvram module it's hard to say whether that's the intended result or not.

Link to comment
Share on other sites
Toonces Katt
Toonces Katt
Posted
Posted

The UUID is read out form your machine's SMBios, we used the value in the bios and not the overwritten value, so it may be different if you have manually specified a uuid / system id somewhere.

 

Manually specifying the plist path is not supported.

 

I haven't specified a UUID anywhere that I am aware of. the output of my nvram and ioreg are below. The 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 UUID is generated when I boot nvram.plist removed. If I delete the 4D1E values using nvram and reboot, it comes back.

 

 

$ sudo ioreg -lw0 | grep PlatformUUID

| "IOPlatformUUID" = "371A61AF-D774-58C5-870D-82C4D7054ED8"

| "IOPlatformUUID" = "371A61AF-D774-58C5-870D-82C4D7054ED8"

 

 

$ sudo nvram -p

IOPowerManagement:MaxPowerState %00%00%00%00

371A61AF-D774-58C5-870D-82C4D7054ED8:ROM 00064f49be86

IOPowerManagement:CurrentPowerState %00%00%00%00

boot-gamma %ac%10%00%00.%a0%00%00UNC1%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%ac%10%00%00<@%00%00S2FC%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%ac%10%00%00B@%00%00L271%b6%00%00%00%00%00%00%00%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7%0d%00%01%01%e3%04%02%02%05%08%04%04)%0d%07%07%a1%13%0e%0e4 %18%18T/##%f8=00%a7M=='\NN%d7mrr%0b%90%9a%9a%90%b2%c9%c9%fb%d7

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB CK916531XYLODT3Q%00

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM %00%00%00%00%00%00%00%00%00%00%00%00%00

IOPowerManagement <INVALID>

boot-args -v -f%00

371A61AF-D774-58C5-870D-82C4D7054ED8:MLB CK916531XYL123456%00

 

If you can PM me a picture of the panic as well as the nvram.plist, the output of nvram -xp and of bmesg, I'll look into it.

 

Will do.

Link to comment
Share on other sites
meklort
meklort
Posted
Posted

I haven't specified a UUID anywhere that I am aware of. the output of my nvram and ioreg are below. The 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 UUID is generated when I boot nvram.plist removed. If I delete the 4D1E values using nvram and reboot, it comes back.

 

I missread your earlier post.

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 is the UUID that apple uses to specify an nvram variable is really an efi runtime variable. If the MLB or ROM values do not exist, these will be generated for you.

 

You should also have a file in /Extra with the name nvram.

371A61AF-D774-58C5-870D-82C4D7054ED8.plist where the UUID here corresponds to your machine's UUID.

 

My NVRAM file has the UUID of 00020003-0004-0005-0006-000700080009 (file is named nvram.00020003-0004-0005-0006-000700080009.plist). This looks to be faked value. When i export PlatformUUID fro ioreg, i get 55ADE930-5FDF-5EC4-8429-15640684C489. Doesn't look to be impacting anything but wanted to report it in case it's a bug.

This probably means that the SMBios UUID was never filled in by your motherboard manufacturer, making the UUID not so unique.

 

Also, usually when you execute nvram -p you don't see the MLB and ROM (verified on a hack running clover and on a real mac) but when i'm using this Chameleon fix, it prints out. Not sure if it should be there or not. Without seeing the source code for the nvram module it's hard to say whether that's the intended result or not.

We decided to make the hidden variables visible, this is supposed to happen. We can always hide it in the future if it's requested.

Link to comment
Share on other sites
Toonces Katt
Toonces Katt
Posted
Posted

I missread your earlier post.

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 is the UUID that apple uses to specify an nvram variable is really an efi runtime variable. If the MLB or ROM values do not exist, these will be generated for you.

 

You should also have a file in /Extra with the name nvram.

371A61AF-D774-58C5-870D-82C4D7054ED8.plist where the UUID here corresponds to your machine's UUID.

 

 

The name of the file I have in Extra is nvram.44454c4c-5400-1037-8058-b1c04f544631.plist which was also automatically generated. I tried to change the file name and I don't have permissions. I can always change the permissions but didn't want to unless that's what I need to do.

 

I wasn't able to send you a PM.

 

Thanks Again!

 

Here's the output of nvram -xp. It lists 2 different UUIDs but not the same as the file name from above. I swear I'm not makin these numbers up :D

 

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>371A61AF-D774-58C5-870D-82C4D7054ED8:MLB</key>

<data>

Q0s5MTY1MzFYWUwxMjM0NTYA

</data>

<key>371A61AF-D774-58C5-870D-82C4D7054ED8:ROM</key>

<data>

MDAwNjRmNDliZTg2

</data>

<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB</key>

<data>

Q0s5MTY1MzFYWUxPRFQzUQAA

</data>

<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM</key>

<data>

AAAAAAAAAAAAAAAAAAAA

</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>

LXYgLWYA

</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>

Link to comment
Share on other sites
p.H
p.H
Posted
Posted

The name of the file I have in Extra is nvram.44454c4c-5400-1037-8058-b1c04f544631.plist which was also automatically generated. I tried to change the file name and I don't have permissions. I can always change the permissions but didn't want to unless that's what I need to do.

 

I wasn't able to send you a PM.

 

Thanks Again!

 

Here's the output of nvram -xp. It lists 2 different UUIDs but not the same as the file name from above. I swear I'm not makin these numbers up :D

 

 

Same here. The output by nvram -xp shows uuid which is not same as my hardware uuid in system profile or the systemid I inject in Chameleon.

 

I missread your earlier post.

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 is the UUID that apple uses to specify an nvram variable is really an efi runtime variable. If the MLB or ROM values do not exist, these will be generated for you.

 

So you are saying that all real mac has the same 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 for nvram variable or just got this string from one real mac ?

BTW, chameleon did not automatically generate any UUID.plist in my extra folder. I am using GPT, efi partition.

Link to comment
Share on other sites
cosmo1t
cosmo1t
Posted
Posted

Same here. The output by nvram -xp shows uuid which is not same as my hardware uuid in system profile or the systemid I inject in Chameleon.

 

 

So you are saying that all real mac has the same 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14 for nvram variable or just got this string from one real mac ?

By the way, chameleon did not automatically generate any UUID.plist in my extra folder. I am using GPT, efi partition.

 

Yes that 4D1 is an application specific UUID.. There may be more. Every mac has them stored in efi/nvram. The UUID that the nvram.plist is named with comes from YOUR MOTHERBOARD. IE, it's not related to anything else.

Link to comment
Share on other sites
p.H
p.H
Posted
Posted

Yes that 4D1 is an application specific UUID.. There may be more. Every mac has them stored in efi/nvram. The UUID that the nvram.plist is named with comes from YOUR MOTHERBOARD. IE, it's not related to anything else.

Gotcha. Will the module generate plist automatically? It does not in my efi partition though

Link to comment
Share on other sites
meklort
meklort
Posted
Posted

Gotcha. Will the module generate plist automatically? It does not in my efi partition though

 

The plist is automatically created in the /Extra folder (on the root of the booted drive), it does not touch any other partitions. If you do not have an extra folder, it will not create it for you, and as such, the plist will not be created.

Link to comment
Share on other sites
p.H
p.H
Posted
Posted

The plist is automatically created in the /Extra folder (on the root of the booted drive), it does not touch any other partitions. If you do not have an extra folder, it will not create it for you, and as such, the plist will not be created.

/dev/disk0
  #:					   TYPE NAME				    SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme					    *160.0 GB   disk0
  1:					    EFI						 209.7 MB   disk0s1
  2:				  Apple_HFS Macintosh HD		    80.0 GB    disk0s2
  3:				  Apple_HFS Storage				 79.5 GB    disk0s3

My Extra folder is in EFI partition together with DSDT SSDT etc. The boot drive should be Macintosh HD on which OS X is installed.

I didn't see Extra folder in the root. Here is the info for "/":

pH:~ pH$ cd /
pH:/ pH$ ls -la
total 16493
drwxr-xr-x   34 root  wheel	 1224 Jan 23 08:13 .
drwxr-xr-x   34 root  wheel	 1224 Jan 23 08:13 ..
-rw-rw-r--    1 root  admin	 6148 Jan 23 08:07 .DS_Store
d--x--x--x    8 root  wheel	  272 Jan 12 10:22 .DocumentRevisions-V100
drwx------    5 pH    staff	  170 Oct  9 19:33 .Spotlight-V100
d-wx-wx-wt    2 pH    staff	   68 Dec 26 09:49 .Trashes
-rw-r--r--@   1 pH    staff	    0 Oct  9 19:33 .com.apple.timemachine.donotpresent
----------    1 root  admin	    0 Aug 17 06:07 .file
drwx------  160 pH    staff	 5440 Jan 23 09:36 .fseventsd
-rw-------    1 root  wheel   196608 Nov  6 07:48 .hotfiles.btree
drwxr-xr-x@   2 root  wheel	   68 Jun 21  2012 .vol
drwxrwxr-x+  78 root  admin	 2652 Jan 19 10:44 Applications
drwxr-xr-x+  65 root  wheel	 2210 Nov  7 06:53 Library
drwxr-xr-x@   2 root  wheel	   68 Aug 17 06:07 Network
drwxr-xr-x+   4 root  wheel	  136 Oct 10 04:11 System
drwxr-xr-x    5 root  admin	  170 Oct 10 04:25 Users
drwxrwxrwt@  12 root  admin	  408 Jan 23 08:15 Volumes
drwxr-xr-x@  39 root  wheel	 1326 Jan 18 13:14 bin
-rw-r--r--    1 root  wheel	 9265 Jan 23 08:13 boot-logs.old
-rw-r--r--    1 root  wheel	 9248 Jan 23 08:13 boot.log
drwxrwxr-t@   2 root  admin	   68 Aug 17 06:07 cores
dr-xr-xr-x    3 root  wheel	 4443 Jan 23 08:12 dev
lrwxr-xr-x@   1 root  wheel	   11 Oct 10 04:02 etc -> private/etc
dr-xr-xr-x    2 root  wheel	    1 Jan 23 08:12 home
-rw-r--r--@   1 root  wheel  8191952 Jan  7 14:37 mach_kernel
dr-xr-xr-x    2 root  wheel	    1 Jan 23 08:12 net
-rw-r--r--    1 root  wheel	 1807 Jan 23 08:11 nvram.plist
drwxr-xr-x@   6 root  wheel	  204 Nov 19 16:39 private
drwxr-xr-x@  62 root  wheel	 2108 Jan 18 13:14 sbin
lrwxr-xr-x@   1 root  wheel	   11 Oct 10 04:02 tmp -> private/tmp
drwxr-xr-x@  13 root  wheel	  442 Oct 26 07:53 usr
lrwxr-xr-x@   1 root  wheel	   11 Oct 10 04:02 var -> private/var

Link to comment
Share on other sites
meklort
meklort
Posted
Posted

Yes, since you don't have /Extra, no plist will be generated.

 

Just a few notes about /Extra/nvram.uuid.plist

 

This file is automatically generated on the root of os x partition that is booted. It will only be generated if the /Extra folder exists.

 

You should *never* touch this plist. It's permissions are 400 for a reason (readable only by root). Any changes you make will be lost.

 

The only supported method of modifying this file is by using the nvram command:

Set a value: sudo nvram property=value

Unset a value: sudo nvram -d property

 

If you wish to read teh contents of the file you may use one of the following:

sudo defaults read /Extra/nvram.uuid.plist

nvram -p

nvram -xp

 

If you do decide to manually edit the file, your changes will be lost. You also cannot rename this file, if you do, a new one with the old name will be regenerated for you. If you decided to change the permissions on the file, it will be reset to 400.

 

In other words, don't touch it. The *only* time that you can touch it without loosing changes is when the FileNVRAM.dylib module is not loaded.

  • Like 1
Link to comment
Share on other sites
p.H
p.H
Posted
Posted

Thanks for explanation :D

Just feel a little bit wield that the generated plist are located inside Extra folder. For those who use an EFI partition, we'd rather not use the Extra folder in root. Maybe just a single file located in root?

 

Edit:

I manually created the Extra folder in root directory and I saw the generated plist file with an even strange uuid file name.

The uuid in the file name is not any in the content of this file or hardware uuid or the id I inject with chameleon

Link to comment
Share on other sites
Toonces Katt
Toonces Katt
Posted
Posted

This file is automatically generated on the root of os x partition that is booted. It will only be generated if the /Extra folder exists.

So does the filename in /Extra make a difference? I can't get iMessage working, still getting the same server error though I can boot Clover off a USB stick and get back in just fine. You can see from my nvram -xp above that I have the UUID from ioreg and another one both with MLB and ROM data but the file name is different still.

 

Thanks Again!

Link to comment
Share on other sites
Dil83
Dil83
Posted
Posted

Is there anyway to keep Find My Mac enabled after a reboot?

 

I also would like to know if this is possible? Shouldn't we just be able to add a key & value to the nvram.uuid.plist to enable it upon boot?

 

By the way, iMessage also working great here!

 

Thanks!!!!!

 

Dil83

Link to comment
Share on other sites
froalskiner
froalskiner
Posted
Posted

Modules should be inside Extra. If it's not there, create it. :)

Ok, I created the modules folder, copied the FileNVRAM.dylib file into the folder. Updated Chameleon to 2170. On reboot, the nvram auto-generated with a bunch of zeros. iMessage now gives me a Contact Support message. I logged into iCloud on my MBA (lion)but I'm still getting the contact support message.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...