406 replies to this topic

[Regi Yassin]

replace uuid with your systemid, or just ignore it, install 2170 with the module, and restarte, nvram will automatically generated in extra.
MBL and ROM will be automatically generated either

this is the easiest way i think,

[dmazar]

cosmo1t, on 22 January 2013 - 03:38 AM, said:

messages fixed. Please enjoy
From Cosmo1t & Meklort

Wow! Great work. Persistent vars without messing with additional scripts?

How does it work?

[ShoGinn]

Whats weird is, it created a /nvram.plist file as well as an /Extra/nvram.uuid.plist file

I also get a boot error now:

Added 3 SSDT table(s) into XSDT
Unable to handle key MLB
Unable to handle key ROM
Unable to handle key EFIBluetoothDelay
Unable to handle key bluetoothActiveControllerInfo
Unable to handle key SystemAudioVolume
Unable to handle key LocationServicesEnabled
Unable to handle key fmm-computer-name
Unable to handle key boot-gamma
Starting Darwin x86_64

[cosmo1t]

you didn't create it correctly
just delete both nvram.plists, and reboot, it'll autogenerate one for you
then you can set teh values using nvram

[meklort]

Regi Yassin, on 22 January 2013 - 07:55 AM, said:

confirmed!

r2170 fixed this issue
edit: everytime I tried to edit nvram.UUID.plist, to change the MLB, after restart it goes back into before edited, i cant change the plist.

If you need to edit the plist, please use the nvram key=value command in os x.

[C.44]

Regi Yassin, on 22 January 2013 - 09:49 AM, said:

just download my attachment "sym.zip"
extract it and install using chameleon wizard,

Just did that and have 2 problems now, haven't even tried to use the nvram fix yet. Chameleon Wizard updated my older version to r2170, but in the process all my internal drives show as external and sleep stopped working (probably because external drives get ejected when sleep is initiated?)

Edit: Just recreated my kextcaches and repaired the permissions on my bootvolume. There was some wonky stuff going on with the permissions. I installed the nvram fix, rebooted and everything is back to normal, including a working Messages.app. Thanks loads people =)

[Regi Yassin]

meklort, on 22 January 2013 - 01:57 PM, said:

If you need to edit the plist, please use the nvram key=value command in os x.

in order to change MLB & ROM Data use this commands from terminal

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=SERIAL17DIGITS
nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=YOURDATA

fill the MLB & ROM data with ASCII Text
it will automatically encoded to Base64

Edited by Regi Yassin, 22 January 2013 - 04:00 PM.

[Toonces Katt]

I know I must be doing something wrong. I installed 2170 and rebooted to auto generate the nvram.plist. I copied it to /Extra/nvram.371A61AF-D774-58C5-870D-82C4D7054ED8.plist and rebooted again. Every time I try to add using the nvram command, I get an error "Error setting variable - '371A61AF-D774-58C5-870D-82C4D7054ED8:MLB': (iokit/common) general error" and a new nvram plist file is created witht he UUID with the name nvram.44454c4c-5400-1037-8058-b1c04f544631.plist

What am I missing to set??

Thanks and GREAT JOB!

[cosmo1t]

use sudo?

[rcork]

cosmo1t, on 22 January 2013 - 03:38 AM, said:

http://forge.voodoop...ce/commit/2169/

messages fixed. Please enjoy
From Cosmo1t & Meklort


USAGE:
Install FileNVRAM.dylib to /Extra/modules (if you have ACPICodec.dylib, you have to get rid of it)

if you do not create a nvram.plist ROM and MLB will be auto generated.

put the plist as /Extra/nvram.uuid.plist if you make one. (your uuid -- PlatformUUId from IOREg, or uuid from smbios)\

ioreg -lw0 | grep PlatformUUID

use the value found from the above command to create your plist.

<?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>NVRAM</key>
<dict>
<key>test-var</key>
<data>AAAAAQ==</data>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<dict>
<key>MLB</key>
<string>BLargh</string>
<key>ROM</key>
<string>ROMVER</string>
</dict>
</dict>
</dict>
</plist>

ENjoy a FULLY FUNCTIONAL NVRAM.
you can use nvram key=val.

everything will be persistent between reboots.

Is the source code for this module available?

[Regi Yassin]

cosmo1t, on 22 January 2013 - 04:12 PM, said:

use sudo?

its better with sudo,

[cosmo1t]

the module source will be available in 2-4 weeks after thorough testing/etc in teh field

[C.44]

Found something strange, though iMessage is working i have a lot of warnings in my Console:

[Warning] Updating typing guid on IMMessage from 11111111-1111-1111-111111111111 to 11111111-1111-1111-111111111111

obviously i edited the guid numbers but still. Any ideas?

[ShoGinn]

Mine were auto generated, the fix still works for imessage; it just gives those errors... i'll leave it for now

[cosmo1t]

can u pm the real guid's so we can see what is going on. a bunch of 1's doens't help
adn a

deafults read /Extra/Nvram.xx.plist > nvDefaults.log
bdmesg > bdmesg.log
sudo nvram -px > nvram.log

[Regi Yassin]

cosmo1t, on 22 January 2013 - 04:19 PM, said:

can u pm the real guid's so we can see what is going on. a bunch of 1's doens't help
adn a

deafults read /Extra/Nvram.xx.plist > nvDefaults.log
bdmesg > bdmesg.log
sudo nvram -px > nvram.log

i have sent you my log, and my guid is not only a bunch of 1's

[ShoGinn]

Disregard my errors, I updated to 2170 and all is well..

[Adam1203]

After the install and first reboot, it worked great. Second reboot KP'd. Not sure what the message is, as I am not in front of my hack (did the steps remotely via LMI)

[mendietinha]

here is asking to call apple suport. but its a progress.

ok, working nice with one apple id, but with the main, no. asks for me to contact support.

[theconnactic]

Mendietinha, you must access your account on a legit iOS/Mac hardware to solve this issue.