From b9c5e49791fabe1443360c4e1acb5b63a628d223 Mon Sep 17 00:00:00 2001 From: Jan Wachsmuth Date: Sat, 13 Jan 2024 17:07:53 +0100 Subject: [PATCH] updated content --- Downgrade.md | 2 +- cgi-bin.md | 2 +- download-firmware.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Downgrade.md b/Downgrade.md index 0f07a6a..1f0d33c 100644 --- a/Downgrade.md +++ b/Downgrade.md @@ -433,7 +433,7 @@ curl -s 'http://10.1.1.58/httpapi.asp?command=getStatusEx' | jq > I recommend to rename the ***products.xml*** file on your server after an up- or downgrade to something else and block or redirect any upgrade requests on the Internet. If a ***products.xml*** is found on that server in the proper directory (the default URL is pointing to http://silenceota.linkplay.com/wifi_audio_image) then an automatic upgrade may be triggered. ## Problem with Upgrade after downgrade -In v4.6 Arylic has added a command to play a notification URL from my home automation system while music is playing. The music is faded out before the notification message is played, so this is quite nice. After I had installed a permanent hook that even survives a reboot I wanted to upgrade afterwards. See [Install Persistant Hook](/persistant-hook.md) for details. +In v4.6 Arylic has added a command to play a notification URL from my home automation system while music is playing. The music is faded out before the notification message is played, so this is quite nice. After I had installed a permanent hook that even survives a reboot I wanted to upgrade afterwards. See [Install Persistent Hook](/persistent-hook.md) for details. I don't know why, but an upgrade with cli commands always got stuck after the device has fetched the ***MVver_20220427*** file. The three files ***products.xml***, ***product.xml***, and ***MVver_new*** were downloaded properly and temporarily stored in ***/tmp*** directory on the device. For some reason the device believes that an upgrade is not required, so the upgrade process is stopped. diff --git a/cgi-bin.md b/cgi-bin.md index 535a536..779fe06 100644 --- a/cgi-bin.md +++ b/cgi-bin.md @@ -40,7 +40,7 @@ export WIIMU_play='http://10.1.1.22/linkplay/scripts/Modification_installed.mp3' /etc_ro/web/cgi-bin/notice.sh unset WIIMU_play ``` -You may add these commands to a persistant hook, see [Install Persistant Hook](/persistant-hook.md) for details. +You may add these commands to a persistent hook, see [Install Persistent Hook](/persistent-hook.md) for details. Now you can play a notice message on the device by calling your script: ``` diff --git a/download-firmware.md b/download-firmware.md index 2dd530f..0e45326 100644 --- a/download-firmware.md +++ b/download-firmware.md @@ -157,7 +157,7 @@ curl --create-dirs http://silenceota.linkplay.com/wifi_audio_image/drPb6dKCSrFvP > NOTE: > There are no product.xml files for new products like UP2STREAM_PRO_V3, UP2STREAM_AMP_V3, or UP2STREAM_AMP_V4, but that's no problem, because of the conclusion from above and the fact that there IS a product in the list that has the same UUID / 'cryptic' ID (in the latest version). -It may not be important to have the MCU files for an older version. You can just copy the part from the latest version. Even if the device will not work with that MCU, the main reason to do a downgrade is to install a persistent hook in flashfs that survives a reboot and even an upgrade, see [Install Persistant Hook](/persistant-hook.md) After the hook is installed, you may upgrade again to the version that was used before. +It may not be important to have the MCU files for an older version. You can just copy the part from the latest version. Even if the device will not work with that MCU, the main reason to do a downgrade is to install a persistent hook in flashfs that survives a reboot and even an upgrade, see [Install Persistent Hook](/persistent-hook.md) After the hook is installed, you may upgrade again to the version that was used before. If there is no product with the same UUID available, but your product is based on the Linkplay A31 module, then it might be possible (although more risky) to install the files for a different product from the same or even another vendor by manipulating the product ID. At the end it's your risk - don't blame me if it is not working and you've bricked your device!