Jump to content
cosmo1t

FileNVRAM 1.1.3 Released

80 posts in this topic

Recommended Posts

One thing, I boot from a stick where is chameleon, Extra etc. but nvram,,,.plist wants to be saved into Extra on working partition.

Wouldn't be better to save it into boot partition's Extra?

No. Doing that could cause issues on a PC with multiple versions of OS X installed. It's better to use /Extra on the partition you're actually booting.

Share this post


Link to post
Share on other sites
Advertisement

No. Doing that could cause issues on a PC with multiple versions of OS X installed. It's better to use /Extra on the partition you're actually booting.

I meant different plists for different installations located all in Extra on boot partition (a stick in my case).

Share this post


Link to post
Share on other sites

Bungo,

 

FileNVRAM will probe all devices that chameleon has read access to for the latest nvram plist file, so it shouldn't matter where it gets saved. The plist is saved on the active system partition due to technical limitations of the module that make this the easiest solution to implement.

 

If you feel that there are drawbacks to this solution, let me know and it can be revisited.

Share this post


Link to post
Share on other sites

Bungo,

 

FileNVRAM will probe all devices that chameleon has read access to for the latest nvram plist file, so it shouldn't matter where it gets saved. The plist is saved on the active system partition due to technical limitations of the module that make this the easiest solution to implement.

 

If you feel that there are drawbacks to this solution, let me know and it can be revisited.

Ok. I thought about it and agree with you. If I would make a plist hidden in root  (I mean outside Extra) I 'd be glad.

 

BTW, In SL 10.6.8 there isn't backlight-level key, do you know how does it save that value?

Share this post


Link to post
Share on other sites

Internally there is a way to change the nvram plist path, however it's not expose as a boot argument / configurable (there are certain cases where it'll change however).

 

If you file a bug report, I can add it to the next version (but.... that might take a while to release)

Share this post


Link to post
Share on other sites

Internally there is a way to change the nvram plist path, however it's not expose as a boot argument / configurable (there are certain cases where it'll change however).

 

If you file a bug report, I can add it to the next version (but.... that might take a while to release)

Filed (in Pre-boot section). Thanks

Share this post


Link to post
Share on other sites

No. Doing that could cause issues on a PC with multiple versions of OS X installed. It's better to use /Extra on the partition you're actually booting.

I got KP on MV 10.9 and SL 10.6.8 hangs on boot when I placed Extra on both partitions.

 

 

Please report any bugs at https://public.xzenue.com/bugzilla/

Does somebody reads bug reports?

Share this post


Link to post
Share on other sites

Bungo,

 

FileNVRAM will probe all devices that chameleon has read access to for the latest nvram plist file, so it shouldn't matter where it gets saved. The plist is saved on the active system partition due to technical limitations of the module that make this the easiest solution to implement.

 

If you feel that there are drawbacks to this solution, let me know and it can be revisited.

 

Hi,

 

Many thanks to the Developers of FileNVRAM,

 

Its a great solution, works well and It's allowed me to get iMessage (and other features) running on all my OSX systems, however there is one situation that constantly causes FileNVRAM to fail to initialise and load properly and that is when booting OSX from a software Raid (either 0 or 1)

 

In my case I have two 128GB SSD configured as a Raid 0 (stripe). Each Raid member drive has its own Raid Helper Partition (in my case Disk0s3 & Disk1s3) . Because the boot loader has to be accessible outside of OSX (software raid can only work once kernel is up and running) the /Extra folder must reside on the Raid Helper Partition, unfortunately the raid helper partition(s) are unmounted once OSX starts up, thus FileNVRAM is unable to access the /Extra folder as such it fails to load correctly. 

 

The only way around this as far as I know is to clone the raid onto a single HDD, modify the chameleon plist and install the boot loader so that the drive can boot on its own. Then it is possible to install FileNVRAM in the /Extra folder. Once the standalone drive is booted FileNVRAM works and creates its plist in /Extra. Once working you then have to re-clone the standalone drive back to the raid and copy the FileNVRAM plist to each of the /Extra folders on the helper partitions, simply copying the files will not work, you have to clone the whole drive so i'm guessing there are some configuration plists within OSX or the user folder that somehow are linked to the contents of FileNVRAM. Once the cloned SSD is working FileNVRAM works in that it can read the plist from the helper partition, but once loaded it is unable to refresh the contents as the raid helper partitions are no longer accessible so  If you ever get logged out of iMessage you have to do the whole process again.

 

As you can imagine, this is a bit of a pain and I know I am not alone in seeing this problem as users on this and other forums have reported similar issues when using a Raid as the OSX boot drive.

 

I'm guessing that the issue is that FileNVRAM needs to create/access its plist at initialisation, which cant be on the raid as its not active yet and for some reason it cant create it on the OSX Raid Helper partition (file/disk access permissions ?) but even if it could, the Helper Partition is unmounted once the raid is live so its not available to FileNVRAM once OSX is up and running ?

 

Maybe it would be possible to add a config switch to the chameleon plist (or FileNVRAM's own config file) that holds a full drive/path to the FileNVRAM plist, that way the module could stay with the current default behaviour, but if the path it set via plist string then it overrides the default behaviour and forces it the specified drive/path (in my case this could be one of my non raid, OSX data drives which is accessible at all times.

 

Seems this would be the easiest solution to the problem ?

 

Will be happy to provide debug info and beta test if required.

 

Cheers

Jay

Share this post


Link to post
Share on other sites

When I reboot, a new nvram.xxx.plist is not being created.

 

The module loads, I can use nvram -x -p at the command line. 

 

Any ideas on how to generate a new one?

Share this post


Link to post
Share on other sites

ML 10.8.5 with Chimera 3.0.1

 

My value of ROM changes randomly on every reboot.

 

Which stops me accessing iMessage & Facetime.

 

I apply:

 

sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=xxxxxxxxxxxx

 

and on reboot this value changes to something else completely, and same on each reboot

 

Also the bug (reported) https://public.xzenue.com/bugzilla/show_bug.cgi?id=19

 

definitely exists. Facetime works with empty ROM, but iMessage does not

 

sebus

Share this post


Link to post
Share on other sites

Not sure if this will help anyone but FWIW:

 

I boot using a USB thumbdrive. In trying to track down Messages and Facetime issues I realized that FileNVRAM was not writing the nvram.xx.plist to the /Extra folder on the USB thumbdrive. I had to manually create the /Extra folder on the root of my hard drive, reboot, copy the plist that was created in that folder to the /Extra folder on the USB thumbdrive. After rebootintg the MLB and ROM values stayed constant. That allowed me to call Apple and get the block removed. Now Messages and Facetime  work perfectly. I was able to delete the /Extra folder on the root of my hard drive and everything continues to work.

 

Thanks to all the hard work these developer do!

Share this post


Link to post
Share on other sites

Installed the FileNVRAM.dylib to /Extra/modules/ but nvram.uuid.plist doesn't auto create,why?

Share this post


Link to post
Share on other sites

This is good.Your NVRAM.dylb now work.

I think I need I use nvram.uuid.plist to save nvram settings.sudo nvram to set variable,after restart it doesn't save.I think it doesn't work.

Share this post


Link to post
Share on other sites

It won't work with Yosemite, that's old news: why people still insist? Unless meklort or cosmo1t say otherwise, FileNVRAM development is stalled. Chameleon based systems won't be supporting iMessage for now. Most important, uni-multi-tools based systems won't do it too: because I really think the growing demand for a Chameleon based solution these past couple of days is because now Voldemort support Yosemite, and since they don't really develop anything, their smarter users end up finding their way here and simply cannot accept their beast-configured machines won't be the Mac clones Voldemort's horcruxes let them think they would.

Share this post


Link to post
Share on other sites

It won't work with Yosemite, that's old news: why people still insist? Unless meklort or cosmo1t say otherwise, FileNVRAM development is stalled. Chameleon based systems won't be supporting iMessage for now. Most important, uni-multi-tools based systems won't do it too: because I really think the growing demand for a Chameleon based solution these past couple of days is because now Voldemort support Yosemite, and since they don't really develop anything, their smarter users end up finding their way here and simply cannot accept their beast-configured machines won't be the Mac clones Voldemort's horcruxes let them think they would.

 

Doesn't seem to be totally stalled...

https://public.xzenue.com/websvn/filedetails.php?repname=FileNVRAM&path=%2Ftrunk%2Fdocs%2FNEWS&rev=3&peg=3

Share this post


Link to post
Share on other sites

I hope for chameleon users you're right.  However looking at the date of that news, it was from January 2014 and nothing publically announced since then.  Remember Yosemite DPs were released in June....

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





    • By JRevenge
      Buon pomeriggio!
      Sto avendo problemi di NVRam con qualsiasi combinazione possibile, ho provato AptioMemoryFix + Emuvariable + RC-Script, ho provato con solo Aptio, insomma le ho provate tutte, ma riscontro dei problemi cno la NVRam non da poco.
       
      In poche parole, se imposto uno sfondo, al riavvio o banalmente ad uno spegnimento serale per poi una accensione al giorno successivo, mi ritrovo con lo sfondo vecchio, mi capita di trovarmi col terminale con i vecchi comandi registrati o banalmente qualche cartella aperta. Mi sapreste aiutare?
       
      Vi lascio la mia EFI in descrizione.
      Grazie mille!
      CLOVER.zip
    • By Cyberdevs
      This is a tool for cleaning the NVRAM and Kext Caches and rebuilding the PrelinkedKernel.
      Please do not post/upload or redistribute this app to other sites or forums.
    • By ErmaC
      Enoch
      Latest revision of my Chameleon bootloader branch.
       
      Not able to boot AFPS yet....
       
      Please don't upload it on other servers and don't repack it, thank you.
      - Installer PKG
      - Binaries format (Manual install)
      Please don't upload it on other servers and don't repack it, thank you.
       
      Chameleon bootloader credits goes to Chameleon Team http://forum.voodooprojects.org
       
      Changelog: http://forge.voodoop...e/changes/HEAD/
       
      This revision of Enoch contain the upcoming FileNVRAM revision 1.1.5 (RC8)
      Credits to Micky1979
       
       
      Language Translation:

      For on-line Chameleon language package resource edit
      >> Pootle
       
       
      Pls translate/complete it.
       
      Link here on InsanelyMac (Italian only): Enoch Bootloader
       
      Enjoy
       
      ErmaC
    • By blackosx
      Do you want to quickly find your boot log, or ever wanted to know which version of bootloader is installed on your disk(s), had the need to dump your BIOS from OS X, just curious about your own system setup or been asked to provide your setup information to others when asking for assistance?
       
      DarwinDumper is a useful collection of readily available tools, and scripts wrapped in an application framework giving you a convenient method to quickly gather a system overview of your hack or Mac. And rest assured that enabling the privacy option will mask sensitive data like the IOPlatformSerialNumber, IOPlatformUUID, IOMACAddress(s), USB Serial Number(s), SystemSerialNumber, serial-number, fmm-mobileme-token-FMM, MLB and ROM efi vars and CustomUUID in the dumped files and report.
       
      Current Version: 3.0.4


      The system dumps are saved to a folder or your choice, but defaulting to the same directory as the main application. You can choose to setup a symlink to make it simple to run DarwinDumper from the Terminal.
       
      There is an option to create an html report showing a complete overview of the dumps. This report will mostly just contain the text dumps as you'll find in the main dump directory, but for some dumps there is extra processing to try to present the information in a better way. For example, the Disk Partitions and Unique ID's dump will show a visual map of the disk layout, and the DMI Tables (SMBIOS) dump will show the data split by table type.
       

       
      Note: The html report does not contain all files from a complete dump so if seeking assistance for a problem and you wish to send someone a DarwinDump then you will want to send the complete dump directory and not just the .html report file.
       
      The following can be read and dumped by DarwinDumper:
      - ACPI tables.
      - Audio codec and further info.
      - Boot loaders and configuration files.
      - CPU info.
      - Device-properties.
      - Disk partition structure / info.
      - Disk sectors (hex).
      - DMI (SMBIOS).
      - EDID.
      - I/O Kit Registry.
      - EFI Memory Map.
      - EFI vars (some).
      - Kernel information
      - Kexts - (list of currently loaded kexts).
      - Memory.
      - NVRAM (both Apple specific and UEFI firmware variables).
      - SMC Keys.
      - LSPCI (PCI vendor & device codes) dumps.
      - Power (Sleep/Hibernate) settings.
      - RTC.
      - System Profiler.
      - System BIOS.
      - System Log(s).
      - Video BIOS.
       
      License:
      DarwinDumper is licensed under GNU General Public License, version 3.0 (GPLv3).
       
      Tools included:
      AnalyseVBIOS
      Copyright: Not Known. License: Not known Source: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/   AppleIntelInfo Copyright: © 2012-2017 Pike R. Alpha. All rights reserved. License: Creative Commons Attribution-NonCommercial https://github.com/Piker-Alpha/AppleIntelInfo   atomdis Copyright: Michael Larabel @ Phoronix.com License: GPL Version 2 Source: http://www.phoronix.com/scan.php?page=article&item=amd_atombios_dumper   bgrep Copyright 2009 Felix Domke <tmbinc@elitedvb.net>. All rights reserved.   Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:      1. Redistributions of source code must retain the above copyright notice, this list of       conditions and the following disclaimer.      2. Redistributions in binary form must reproduce the above copyright notice, this list       of conditions and the following disclaimer in the documentation and/or other materials       provided with the distribution.   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.   The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the copyright holder.   Source: https://github.com/tmbinc/bgrep   bdmesg Copyright 2010 by Islam M. Ahmed Zaid. All rights reserved. License: GPL Version 2 Source: http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/util/bdmesg.c   cmosDumperForOsx Created by rafirafi, revised extensively by STLVNUB License: Information not available Source: http://www.projectosx.com/forum/index.php?showtopic=2432&st=0&p=21522&&do=findComment&comment=21522   csrstat Created by Piker-Alpha Copyright: © 2015-2017) by Pike R. Alpha License: Information not available Source: https://github.com/Piker-Alpha/csrstat   dmidecode http://www.nongnu.org/dmidecode/ License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2488   dumpACPI Created by blackosx. Idea taken from PHPdev32's MacIASL. Source: https://bitbucket.org/blackosx/dumpacpi   edid-decode Created by Adam Jackson, revised by Andy Vandijck License: Information not available Original Source: http://cgit.freedesktop.org/xorg/app/edid-decode Revised Source: http://bit.ly/1qAzqxb   fdisk440 Apple Computer, Inc. License: APSL v2.0 Source: http://forge.voodooprojects.org/p/chameleonApplications/source/tree/HEAD/trunk/fdisk.tproj   FirmwareMemoryMap script Amit Singh (showbootermemorymap) License: Information not available Source: http://www.projectosx.com/forum/index.php?showtopic=2447&st=120&p=19329&&do=findComment&comment=19329   flashrom http://flashrom.org/Flashrom License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2485&view=findpost&p=40285   getcodecid Copyright © 2012 AnV Software. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/285277-getcodecid-command-line-tool-to-detect-codec-id/   getdump Created by fassl?, modifications by Slice and AutumnRain? License: Information not available Source: https://svn.code.sf.net/p/voodoohda/code/tranc/getdump.c   gfxutil Copyright 2008 mcmatrix. All rights reserved. License: Information not available http://forum.netkas.org/index.php?PHPSESSID=q2isd338ihjjpcgbng7tne08pdv7tr4f&topic=64.0 Source: https://dl.dropbox.com/u/222155/gfxutil_source.zip   iasl Copyright © 2000 – 2014 Intel Corporation. License: Information not available Source: https://github.com/acpica/acpica   ioregwv Apple Computer, Inc. License: APSL v2.0 Source: https://bitbucket.org/blackosx/ioregwv   lzma Copyright © 2013 Igor Pavlov. License: GNU Lesser General Public License Source: http://www.7-zip.org/sdk.html   lzvn Copyright: © 2014 Apple Computer, Inc. All rights reserved. License: APSL Credit: Piker-Alpha, Andy Vandijck, MinusZwei. https://github.com/Piker-Alpha/LZVN   MacGap2 Created by Tim Debo. All rights reserved. License: MIT Source: https://github.com/MacGapProject/MacGap2   nvram Apple Computer, Inc. License: APSL v2.0 Source: https://bitbucket.org/blackosx/nvram   oclinfo Copyright © 2009 cmf License: GPL Version 2 Source: http://www.insanelymac.com/forum/topic/170796-opencl-info/   pciutils driver (DirectHW.kext) DirectHW is Copyright © 2008-2010 coresystems GmbH License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2480   pciutils lspci Copyright © 1997--2008 Martin Mares License: GPL Version 2 Source Code: https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils.git/+/master   Macpmem driver (Macpmem.kext) Copyright © 2007-2011 Volatile Systems. Copyright 2013-2014 Google Inc. All Rights Reserved. License: GPL Version 2 Source Code: https://github.com/google/rekall/tree/master/tools/osx/MacPmem]https://github.com/google/rekall/tree/master/tools/osx/MacPmem   RadeonDump Created by Dong Luo. Copyright 2008. All rights reserved. Modified by Andy Vandijck License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068   radeon_bios_decode Created by Dong Luo. Copyright 2008. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068   smbios-reader http://www.nongnu.org/dmidecode/ License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2208   SMC_util3 Copyright © 2006 devnull  License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=23230   VoodooHDA.kext Created by fassl?, modifications by Slice and AutumnRain? License: https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h]https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h Source: https://sourceforge.net/p/voodoohda/code/HEAD/tree/]https://sourceforge.net/p/voodoohda/code/HEAD/tree/   x86info Written to succeed CPUID by Phil Karn (KA9Q). Contributed to by various people. OS X compatability by Slice License: GPL Version 2 Original Source: https://github.com/kernelslacker/x86info Revised Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=41134  
       
      Running DarwinDumper from the command line:
      From Terminal, you can initiate DarwinDumper by running the following script directly.


      /DarwinDumper.app/Contents/Resources/public/bash/script.sh To help with this, the UI has a Symlink option which you can click to create a symbolic link which points to the above script. DarwinDumper can then be subsequently run from the command-line by loading a new Terminal window and typing darwindumper followed by return.

      Credits (in alphabetical order):
      Adam Jackson, Amit Singh, Andy Vandijck, Apple Inc., arsradu, bcc9, blackosx, cmf, DieBuche, dmazar, Dong Luo, droplets, ErmaC, Felix Domke, Google Inc., Intel Corporation, InsanelyDeepak, JrCs, Kabyl, Kynnder, Martin Mareš, mcmatrix, Michael Larabel, Mickey1979, phcoder, Phil Karn, Piker-Alpha, rafirafi, гык-sse2, Slice ,sonotone, STLVNUB, THe KiNG, Trauma, Volatile Systems, xsmile, !Xabbu.
       
      DarwinDumper was originally inspired as an open project by Trauma, it has remained an open project and please keep it an open project, so if you make any changes or additions to it then please share your work here.
       
      Please report any feedback, requests or bugs.
       
      Please note:
      DarwinDumper v3 requires OS X 10.9 and newer to run in the Finder, though it should work from the command line okay on older OS versions.

      The following link retains the download for v2.9.9.2 for older OS versions.

      DarwinDumper Download
×