netkas.org forum
February 20, 2019, 01:08:33 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Information for registering users http://forum.netkas.org/index.php/topic,2246.0.html
 
   Home   Help Search Login Register  
Pages: 1 ... 8 9 [10]
 91 
 on: October 22, 2018, 03:02:57 PM 
Started by MacEFIRom - Last post by Tpluth
I could not get the firmware updater tool to work. Error 5570 then Error 5530.

So I hacked the scripts within the tool and ran them directly. I now have a MacPro 2009 which reports Model Identifier: MacPro5,1

Root problem: you need to have BOTH the 2010 and 2009 EFI upgrader disk images available so this tool can prepare both the upgrade and downgrade paths. And the tool no longer seems to be capable of downloading them (or at least not for me and anyone else getting the 5530 error). Digging into the compiled .scpt file inside the tool, it's pretty clear what is wrong. But the script is run-only compiled and I can't fix it directly.

So I manually downloaded them and then had to hack the subsidiary shell scripts embedded in the Firmware Tool app and run them directly by hand.

Here's what I did:

0/ Reboot in recovery mode and disable SIP (Recovery mode, Terminal,  csrutil disable ). Reboot again.

1/ Download *both* EFI updater packages from Apple
https://support.apple.com/kb/DL989?locale=en_US
https://support.apple.com/kb/DL1321?locale=en_US

2/ Use DiskUtility to convert each disk image to a new read/write image

3/ Mount the first image for the 2009 firmware. Rename the mounted disk to Mac Pro EFI Update 2009

4/ Mount the second image for the 2010 firmware. Rename the mounted disk to Mac Pro EFI Update 2010

5/ Run the netkas forum Mac Pro 2009-2010 Firmware Tool.app
(it will fail, but it will create the RamDisk)

6/ Hack the ExtractAndPatchEFIFiles.sh script buried in my ~/Downloads/Mac Pro 2009-2010 Firmware Tool.app/Contents/Resources/ directory with this new version:
Code:
#!/bin/sh

pushd /Volumes/RamDisk

# we mounted the EFI update disk image manually
# hdiutil attach -nobrowse EFI2010.dmg
pkgutil --expand '/Volumes/Mac Pro EFI Update 2010/MacProEFIUpdate.pkg' Expanded
cp Expanded/MacProEFIUpdate.pkg/Payload Payload
tar -xf Payload
mkdir MacProEFI2010-2009
mkdir MacProEFI2009-2010
cp 'System/Library/CoreServices/Firmware Updates/MacProEFIUpdate15/EFIUpdaterApp2.efi' MacProEFI2010-2009
cp 'System/Library/CoreServices/Firmware Updates/MacProEFIUpdate15/MP51_007F_03B_LOCKED.fd' MacProEFI2009-2010/MP41_0081_07B_LOCKED.fd
rm -R Applications
rm -R Expanded
rm -R System
rm Payload
hdiutil detach '/Volumes/Mac Pro EFI Update/'

# we mounted the EFI update disk image manually
# hdiutil attach -nobrowse EFI2009.dmg
pkgutil --expand '/Volumes/Mac Pro EFI Update 2009/MacProEFIUpdate.pkg' Expanded
cp Expanded/MacProEFIUpdate.pkg/Payload Payload
tar -xf Payload
cp 'Applications/Utilities/Mac Pro EFI Firmware Update.app/Contents/Resources/EfiUpdaterApp2.efi' MacProEFI2009-2010
cp 'Applications/Utilities/Mac Pro EFI Firmware Update.app/Contents/Resources/MP41_0081_07B_LOCKED.fd' MacProEFI2010-2009/MP51_007F_03B_LOCKED.fd
rm -R Applications
rm -R Expanded
rm -R System
rm Payload
hdiutil detach '/Volumes/Mac Pro EFI Update/'

popd

patch /Volumes/RamDisk/MacProEFI2009-2010/EfiUpdaterApp2.efi EfiUpdater2009.patch
patch /Volumes/RamDisk/MacProEFI2010-2009/EfiUpdaterApp2.efi EfiUpdater2010.patch

7/ Then run the script directly. Using terminal:

Code:
cd ~/Downloads/Mac\ Pro\ 2009-2010\ Firmware\ Tool.app/Contents/Resources/
./ExtractAndPatchEFIFile.sh
sudo UpgradeEFI2009-2010.sh

8/ Shutdown then power on and hold down the power button. Don't let it go. You'll hear the beep indicating EFI update, then it will reboot again. Keep the button down. In my case, the CD drive popped out. I waited a while, then pushed the CD drive back in. Eventually, I got bored and let the power button go. A little while later it rebooted again. Maybe even one more time.

9/ Login, check all is well with System Info.

10/ Reboot into Recovery mode again, enable SIP (Terminal, csrutil enable). Reboot


I'm pretty sure I captured all of that correctly. Hope this helps others.

(If anyone knows how to contact the original author of the update tool or can get the source, I'd happily fix it)


I was getting 5570 error code but finally was able to upgrade by upgrading 4,1 firmware to latest version and by then using above procedure.  System now reboots to white screen for Mavericks drive or to Apple and progress bar which does not move for High Sierra SSD.

Help!

 92 
 on: October 20, 2018, 05:29:44 PM 
Started by Rominator - Last post by vidkidd
FWIW..  It sounds like your backplane has a different version of the SMC firmware from what's on your cpu tray.   If you had a 4,1, it sounds like you received a 5,1 backplane.  Downgrading the firmware on the logic board will have no effect on the speed of the fans. 

 93 
 on: October 19, 2018, 11:55:57 AM 
Started by Rominator - Last post by ammoune78
If you really want this, I can recreate the intermediate files for you and you can use it to recreate any MP5,1 firmware. Read my post on MacRumors: https://forums.macrumors.com/threads/mp5-1-bootrom-reconstruction-with-intermediate-files.2147538/

Reply there, I'll help you.

Alexandre

Thanks dude, i'll do it today or tomorrow!
I have a Mac Pro 2009 that had faulty Backplane, after i replaced it and upgraded it's  Firmware to 5.1, CPU BoosterA fan is running at 0 RPM, but both BoosterA and BoosterB fans are running at full speed. Even if i downgrade to 4.1 Firmware same thing. The thing that i have seen is, the new Backplane have older revision than the original faulty one. Can it be the problem?
Thanks

 94 
 on: October 18, 2018, 05:56:15 PM 
Started by Rominator - Last post by LightBulbFun
is that code snippet from the RTXs EFI or the MP5,1 138.0.0.0.0 EFI?

its all pretty interesting, because im guessing you need more then JUST UGA/GOP to get a EFI Boot screen on a MP5,1? (but I cant claim to know the exact details sadly)

 95 
 on: October 18, 2018, 05:35:30 PM 
Started by Rominator - Last post by netkas
seems true, snippet of code from ida of this new nvidia efi

// write access to const memory has been detected, the output may be wrong!
EFI_STATUS ModuleEntryPoint(EFI_HANDLE ImageHandle, EFI_SYSTEM_TABLE *SystemTable)
{

  if ( SystemTable->Hdr.Revision < 0x1000A )
    return EFI_INCOMPATIBLE_VERSION;
...

Let me guess - boot screen only works in one holds option key at startup, hence nobody figured this earlier

 96 
 on: October 18, 2018, 12:00:41 PM 
Started by Rominator - Last post by Fl0r!an
is this a full Apple EFI setup, enumerating all the NVDA properties in the device tree like a proper Mac card
The Nvidia UEFI shows no sign of any IOReg properties, just the definition of EFI_UGA_DRAW_PROTOCOL is there, as I postet @ MR. So in macOS it's most likely behaving like a normal PC card (which shouldn't be a problem, since the Mac drivers can init PC cards for almost 10 years now). So we just need to wait for RTX drivers...

 97 
 on: October 18, 2018, 05:44:07 AM 
Started by Rominator - Last post by BillyBobBongo
Man I hope this is also in the 2070, out of all the new cards that really seems the one to buy.

 98 
 on: October 18, 2018, 02:55:54 AM 
Started by Rominator - Last post by lowrider
So Dave

You're confirming the video from CreatePro.  Everyone was skeptical, including me.  You, I believe.  Now all we need is Mojave Drivers.  Oh, and it's RTX 2080.

Lou

 99 
 on: October 18, 2018, 02:30:07 AM 
Started by Rominator - Last post by crjackson2134
Great news, I can’t afford one, but greatnews none the less. I guess all the naysayers (including myself) can rest easy now   Wink

What a good year for the cMP this has been.

 100 
 on: October 18, 2018, 01:36:25 AM 
Started by Rominator - Last post by LightBulbFun
very interesting Smiley

is this a full Apple EFI setup, enumerating all the NVDA properties in the device tree like a proper Mac card

or is it just enumerating the card just enough to work with the Apple graphics protocol and display a boot screen?

id be very interested to see what the card says in system profiler SANS drivers actually...

(In both Graphics/Displays and PCI Cards)

BTW is this from the create.pro thing or do you have someone else in europe confirming it? I know create pro has a less then clean track record so I am a bit skeptical of their reports

Pages: 1 ... 8 9 [10]
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!