Install the firmware in Recovery mode

 

This article is a stub. Main article: Recovery mode.

See also how to update the firmware in Control Center and how to reset to factory default settings.

Introduction

Installing the player firmware is necessary in case of firmware corruption, but can also be used when wanting to downgrade the firmware or when the firmware update would take too long.

• A firmware corruption can occur when the update process is interrupted or when there is a physical corruption of the internal storage, in which case the player is going to enter into Recovery mode by itself.
• For the other cases, see how to manually boot the HMP into Recovery mode.

The process of installing the player firmware from the Recovery Console works as follows:

1. The internal storage is formatted, so the existing firmware files (including the configuration settings) and the user content are completely removed.
2. The selected firmware version is installed from scratch.

Note:

Before reinstalling the player firmware, you might want to generate a configuration backup and make sure you have a copy of the content.

Reverting to factory default firmware

The factory default firmware is permanently stored on the player, regardless of the current installed firmware. If needed, the player can be reverted to the factory default firmware, by following these steps:

1. Boot the HMP into Recovery mode.
2. On the "Main" page, under "Install new firmware" section, check if the factory installed system firmware is present.
3. If so, click on the "Install Factory Image" button.

Notes:

• The device is restored to the same state as when it left the factory - this could mean that the firmware is not the latest one, therefore you might need to update to / install the latest one afterwards.
• In case the factory firmware got corrupted, then use the installation procedure based on PKG files, as detailed below.
• To restore the factory default settings without reinstalling firmware, see the Reset to factory default settings page.
• This functionality is not available on the HMP100 with serial number below 001d500000d7.

Installing a specific firmware

You can install a specific firmware version (the latest one recommended) using the corresponding PKG file that can be downloaded from SpinetiX server.

Procedure

To install a specific firmware version, follow these steps:

1. Download the relevant PKG file (e.g., fw-spinetix-hmp350-***.pkg, prod-fs-spinetix.hmp200-***.pkg etc.) onto your PC.
2. Boot the HMP into Recovery mode.
3. On the first page of the Recovery Console ("Main" page), click on the "Browse" button (next to the "Firmware image package:" field).
   • The "Browse" button might be translated into your language by the browser.
4. Select the PKG file that you have downloaded from SpinetiX site from your PC.
5. Click on the "Upload and install this image" button.
6. Wait for the installation process to complete.
7. (Optional) If you need to set a static IP or to avoid losing the one previously set, follow the procedure below.
8. Reboot the player into normal operating mode.

Avoid resetting the static IP

If you need the player to use a specific IP address after a firmware installation from the Recovery Console, follow the procedure below:

1. Do not reboot at the end of the installation process.
2. Open the "Diagnostics" page.
3. Go to the "System configuration" / "Change configuration" / "Add configuration change" section.
   • The name of the section is different depending on the hardware revision of your player.
4. Set the IP configuration and click on the "Set change" button.
5. Reboot the device.

Troubleshooting

• "tar: gzip: Cannot write: Broken pipe"

  The PKG file is corrupted. Download the file again after clearing your browser's cache.

• "Could not recover firmware image package file"

  If you receive this error when trying to update from a PKG file, attempt to install the factory default firmware.

  If you receive this error when installing the factory firmware, then contact SpinetiX Support.

• "ERROR: package corrupted or forged"

  That could happen when the package file got corrupted upon download (try downloading it again) or when the system date is not correct (set the date manually on the Diagnostics page).