Today, I updated my ALEOS to version 4.13 and went to update the Radio Module Firmware. The version I had downloaded last was MC7354_VZW_55585 and I got a warning that this was not the expected file. So I downloaded MC7354_05.05.58.05_VERIZON_005.032_000 (since my carrier is Verizon) and got a warning that this would change my provider. Since these are operational modems that I am updating in the field, I did not want to change the firmware if this was going to brick my modem and “change” my provider. I need to know what the changes are going to do and how to revert back to a previous version if this does not work.
Hi,
Your current carrier is Verizon, but the previous firmware could be generic.
Could you help to share below information? ( Go to Status -> About):
- Device Model
- Radio Module Type
- Radio Module Identifier
- Radio Firmware Version
- Radio Hardware Version
Thanks,
Device Model RV50
Radio Module Type MC7354
Radio Module Identifier VZW
Radio Firmware Version SWI9X15C_05.05.58.01 r27044 carmd-fwbuild1 2015/03/05 00:02:40
Radio Hardware Version 1.0
Hi,
For your RV50, you can use MC7354_05.05.58.05_VERIZON_005.032.000.iso for Radio FW.
Or you can upgrade through ALMS, it will upgrade device firmware and radio fw in 1 job.
Thanks,
1 Like
Thanks, I tested it today on our shop modem. It worked fine. So I applied the change to the first modem in the field and it is also fine. We’ll continue as normal.
As for ALMS… does that charge airtime for updates? I am running about 50 modems in the field (RV50’s) and at about 60MB per update (33MB for the RF Module, alone), we are talking 3GB of updates. That will hammer our normal usage.
Thanks,
Dave
After testing this on two different devices, the third device is no longer operable. The difference between the two functional devices and the the third non-functional one is the method of application. On the first two devices, I upgraded the ALEOS to v4.13 and then skipped the Radio Module upgrade and came back to the upgrade later. The third unit, I upgraded the ALEOS to v4.13 and then continued to follow the prompt to upgrade the RM consecutively. So, the first two still worked after the ALEOS upgrade, then I did the RM upgrade and all worked. The third unit, I did both upgrades without checking on the ALEOS status. Did the ALEOS fail or did the RM firmware fail? I attempted to salvage the system by putting the modem into RECOVERY mode and attempting to reinstall the ALEOS. No Joy. I tried several times, but to no avail. What should my next steps be?
Hi,
For the pop-up issue on Verizon, it’s known issue on 4.13 Release note.
For the third device, please unplug the power for a few minutes and then power on device. Could you describe the led status?
To enter Recovery mode, please connect Ethernet cable from your PC to RV50 ( set your PC’s IP = 192.168.13.x), and follow the steps in “41113547_ALEOS 4.13.0 Software Configuration User Guide for AirLink RV50_r1” document.
Which step did you fail?
Thanks,
April 15Hi,
For the third device, please unplug the power for a few minutes and then power on device. Could you describe the led status?
To enter Recovery mode, please connect Ethernet cable from your PC to RV50, and follow the steps in “41113547_ALEOS 4.13.0 Software Configuration User Guide for AirLink RV50_r1” document.
Which step did you fail?
Thanks,
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
And the result after attempting to put the modem back into Recovery mode…
Failure occurs after attempted ALEOS update. Even in Recovery Mode. I never see the Reboot screen.
April 15Hi,
For the third device, please unplug the power for a few minutes and then power on device. Could you describe the led status?
To enter Recovery mode, please connect Ethernet cable from your PC to RV50, and follow the steps in “41113547_ALEOS 4.13.0 Software Configuration User Guide for AirLink RV50_r1” document.
Which step did you fail?
Thanks,
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
Hi,
It seems that after selecting ALEOS firmware, you select Radio firmware immediately, so the ALEOS firmware is not uploaded to device, only Radio fw is uploaded. It causes the mismatch between ALEOS and Radio Firmware, so you can not access ACE manager anymore.
From your picture 1, your device is in Recovery mode
Please follow this document to recover device.
To enter Recovery mode.docx (256.9 KB)
And this document to Upgrade the other gateways.
To upgrade FW.docx (487.1 KB)
Hope it can help.
Thanks,
The procedure you have submitted in the two documents is EXACTLY what I have been trying for three days. Is there anything else I should be looking for?
So, I went back, again, and put the unit into Recovery. This time I uploaded the last known working ALEOS, version 4.9.3. That took three tries, but it accepted it as a valid ALEOS. So, then I tried to update the Radio Firmware to the last known RFW, which is SWI9X15C_05.05.58.05 r34350 CARMD-EV-FRMWR3 2017/09/25 01:53:06
So far so good. Now the question is, can I get the unit to take 4.13? And will it take the latest RFW? Latest screenshots below:
So, I went back, again, and put the unit into Recovery. This time I uploaded the last known working ALEOS, version 4.9.3. That took three tries, but it accepted it as a valid ALEOS. So, then I tried to update the Radio Firmware to the last known RFW, which is SWI9X15C_05.05.58.05 r34350 CARMD-EV-FRMWR3 2017/09/25 01:53:06
So far so good. Now the question is, can I get the unit to take 4.13? And will it take the latest RFW? Latest screenshots below:
The procedure you have submitted in the two documents is EXACTLY what I have been trying for three days. Is there anything else I should be looking for?
April 16Hi,
It seems that after selecting ALEOS firmware, you select Radio firmware immediately, so the ALEOS firmware is not uploaded to device, only Radio fw is uploaded. It causes the mismatch between ALEOS and Radio Firmware, so you can not access ACE manager anymore.
From your picture 1, your device is in Recovery mode
Please follow this document to recover device.
To enter Recovery mode.docx (256.9 KB)
And this document to Upgrade the other gateways.
To upgrade FW.docx (487.1 KB)
Hope it can help.
Thanks,
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
Hi,
When Radio firmware version is RMNode, It seems that the Radio firmware could not be loaded successfully before, that causes your issue.
Now you can upgrade from 4.9.3 to 4.13 normally. We didn’t meet any issues when upgrading from 4.9 to 4.13.
Furthermore, please check you cable, make sure that it is not slack.
Please check “Solution”, so that the community can find the solution for their problems easily.
Thanks,