Although we have not seen the "bmclibinitialized returned failed" error, because of the steps you have tried out, we recommend the following alternative ones:
1. Updated the complete [BIOS and firmware, which includes BMC, ME, FRU and SDR] package to 02.02.0005:
1.2. Unzip the contents of the update package and copy all files to a folder on a bootable USB flash drive.
1.2. Insert the USB flash drive to any available USB port on the server system.
1.3. Boot the Server to the EFI shell. This can be accessed via the <F2> BIOS setup utility during POST.
1.4. Run the command "fs0:" to change folders to the USB flash drive.
- The USB flash drive may also mount to fs1: depending on other installed devices.
- Run the command "map -r" in the EFI shell, if needed, to mount the USB flash drive. The number of "fs#" is dependent on the result of command "map -r".
1.5. Run the command "Startup.nsh" to start updating all the firmware and BIOS updates. Follow the on-screen instructions. When you are presented with the 5 options introduced by "Select the function you desire to perform", see to it that you choose 3 ("Update both..."). Again, follow the on-screen instructions.
1.6. Reboot the system into BIOS by pressing F2 during POST and ensure BIOS/firmware was successfully done:
BIOS : R02.02.0005
ME : R03.00.05.128
BMC : 1.12.6784
FRUSDR : 1.07
2. Once the BIOS/firmware is updated, please, re-attempt to update to the latest 01.12.7499 BMC once more should you consider your server really needs it:
The Release Notes for this most current BMC version is found here:
Thanks for the reply.
I had already performed the updates to 02.02.0005 before I did the update to BMC version 01.12.7499. Now *after* the update to BMC version 01.12.7499 (which was successful), I cannot run any of the updaters that you mention (referenced as  in my first post), including "updFRUSDR.nsh". They all fail with the "bmclibinitialized returned failed" error.
It seems that the BMC update to 01.12.7499 irreversibly changed something such that the updaters to version 02.02.0005 contained in  now all produce this error. The BMC is still operational though: it responds to requests from ipmitool under Linux, and I could successfully repeat writing the BMC firmware 01.12.7499.