Hi, I have an RV50X that has been unable to establish cellular communications since being powered on following a two month period without power. After a lot of troubleshooting I think I’ve narrowed down the problem to the radio module. This is based on the elimination of other causes and the following log messages:
Radio Enumeration Failed... The only available port(s) is/are ttyUSB0 cannot open /dev/ttyUSB2 to issue AT /dev/ttyUSB2 is BUSY while checking for Radio Radio module is operating in boot-and-hold mode Radio module is disconnected RecoverRadioModuleFirmware: failed to start SDK QCWWAN2kEnumerateDevices - Return Code [6]
The logs also show ALEOS attempting automatic radio recovery using MC7455_02.33.03.00_GENERIC_002.072_001.iso but the recovery never completes and the radio returns to boot-and-hold mode.
I have factory reset the modem and am still getting this issue. The modem is running ALEOS 4.18.2 and radio firmware 02.33.03.00 (generic). I have a SIM to install and configuration file to upload (both of which were working prior to the two months without power), but have not attempted this since the factory reset as I understand the radio issue to be more fundamental.
Has anyone encountered a situation where an MC7455 repeatedly enters boot-and-hold mode and only enumerates ttyUSB0 after an extended power-off period? Is there a supported method to force a radio firmware recovery/reflash outside of the standard ALEOS recovery process? Any guidance or thoughts would be appreciated!
I understand the problem. I have not had this before with an RV50X but I had this issue with a standalone radio module. With the standalone radio module, we had to use an application to fix it.
In another case here at this forum, we had a similar but not exactly the same issue.
In the other case, none of the ttyUSB ports could enumerate.
The Semtech support contact suggested the following,
Thank you for the info. I went through recovery mode successfully and the modem is now at factory defaults with no SIM installed. However, the radio still fails enumeration. The log shows:
IMEI = NOTSET
Radio SN = NOTSET
Radio FW Version blank
only ttyUSB0 enumerates
/dev/ttyUSB2 unavailable
recurring “Radio module is operating in boot-and-hold mode”
QCWWAN2kEnumerateDevices - Return Code [6]
Recovery Mode reports “No Radio Module Firmware Update pending” but the radio never leaves boot-and-hold state. Previously ALEOS could at least retrieve the Radio SN, IMEI, and radio firmware version. Recovery mode was not a fix but did change things are provide more information. I’m optimistic that if you were able to fix your standalone radio module then there is a solution to this as well.
Based on log you provided, I noticed that logs describe failures during detection and hardware/firmware status-checking process between the ALEOS operating system and the radio module inside the RV50X router.
The radio module appears to have entered a boot-and-hold state.
In order to have the full view about these behaviors, could you please provide the template file and full log file covering the period from two months before the power down until the device was powered back on?
You can upload the files to Google Drive and then share link with me.
***Here are the instructions for obtaining log file and template file:
The configuration template file can be found in ACEmanager → Template. Provide any desired name for the Template Name, and then press Download to retrieve the template file.
Obtain the log file:
a. Go to AceManager > Admin > Log > Configure Logging.
Set all log levels to DEFAULT (NOTICE).
Set Linux Syslog to DISPLAY.
Then select Apply.
b. Reboot the gateway.
c. Go to Admin → View log → Download Logs.
I have uploaded to Google Drive the current log file and template file (dated 2026-08-19) as well as the template file that was active when the issue was first encountered (dated 2026-04-23). Please let me know if there is anything else I can provide.
From the logs you provided, I can see a series of “Radio Enumeration Failed” errors.
*Line 135: Sep 9 00:00:11 notice ALEOS_CELL: Radio Enumeration Failed...The only available port(s) is/are ttyUSB0*
*Line 193: Sep 9 00:00:31 notice ALEOS_CELL: Radio Enumeration Failed...The only available port(s) is/are ttyUSB0*
*Line 194: Sep 9 00:00:31 alert ALEOS_CELL: Radio Enumeration Failed...Retried 20 time(s)*
*Line 195: Sep 9 00:00:52 notice ALEOS_CELL: Radio Enumeration Failed...The only available port(s) is/are ttyUSB0*
*Line 310: Sep 9 00:02:21 notice ALEOS_CELL: Radio Enumeration Failed...No Serial Ports Available*
*Line 328: Sep 9 00:02:40 notice ALEOS_CELL: Radio Enumeration Failed...The only available port(s) is/are ttyUSB0*
*Line 329: Sep 9 00:02:41 alert ALEOS_CELL: Radio Enumeration Failed...Retried 20 time(s)*
*Line 334: Sep 9 00:03:01 notice ALEOS_CELL: Radio Enumeration Failed...The only available port(s) is/are ttyUSB0*
*Line 335: Sep 9 00:03:01 alert ALEOS_CELL: Radio Enumeration Failed...Retried 40 time(s)*
*....*
qmisdkhelper indicates that the module is currently running in boot-and-hold mode.
Sep 9 00:01:38 notice ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Waiting for the Radio Module to be ready*
Sep 9 00:01:38 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) Radio module is operating in boot-and-hold mode*
Since no firmware is found stored on the device, the module cannot be recovered.
Line 2535: Sep 9 00:02:11 err ALEOS_FIRMWARE_RmUpdater: Could not find any firmware in the radio store - radio store empty*
Line 3043: Sep 9 00:02:12 err ALEOS_FIRMWARE_RmUpdater: Could not find any firmware in the radio store - radio store empty*
Therefore, please try reinstalling the firmware to see if this improves the situation:
Go to Admin > Radio Module Firmware and check the Firmware section to see whether any firmware information is displayed.
If not, install the firmware as follows:
1. Download the appropriate Radio Module Firmware for your RV50X from source page at the following link: source.sierrawireless.com/resources/airlink/software_downloads/rv50/rv50x-firmware-list/
2. Click Install button under Admin > Radio Module Firmware > Firmware.
3. Select the firmware file you downloaded in Step 1, then click Install.
4. Wait for the module firmware installation to complete successfully.
I reinstalled the firmware and it does not appear to have resolved the situation. That said, I am unsure if the firmware is active based on this screenshot. I did click the Activate button after uploading the firmware, but it did not change the Active? status in the table.
I went ahead and uploaded a log post-software install to the Google Drive link shared previously. The log does have some differences from the previous ones and seems to indicate the MC7455 recovery process starts, but the radio fails to enter firmware download mode and generates SDK crashes/core dumps during recovery. What are your thoughts?
I reviewed the new log and I see some new error messages to review with @jerdung
Messages like these,
Sep 9 00:02:05 err ALEOS_FIRMWARE_rmswitchingcheck: (qmisdkhelper) QCWWAN2kEnumerateDevices - Return Code [6]
Sep 9 00:02:05 err ALEOS_FIRMWARE_rmswitchingcheck: ERROR: 3. SDK not ready.
Sep 9 00:02:10 warning ALEOS_FIRMWARE_rmswitchingcheck: <–‘11227’: failed to set
and these messages,
Sep 9 00:02:12 notice ALEOS_SYSTEM_UpdateRebootMgr: Applying Radio Module firmware
Sep 9 00:02:12 alert ALEOS_FIRMWARE_RmUpdater: Radio boot-and-hold value is [3] update pending
Sep 9 00:02:12 alert ALEOS_FIRMWARE_RmUpdater: Found firmware MC7455_02.33.03.00_GENERIC_002.072_001.iso^M to recover Radio Module, not matching preferred carrier
Sep 9 00:02:12 alert ALEOS_FIRMWARE_RmUpdater: Radio Module Firmware Update
Sep 9 00:02:13 notice ALEOS_FIRMWARE_RmUpdater: RadioInfo and radioMemoryType do not exist, running RadioInfo again.
.
conclusion - ALEOS is still stuck in trying to recover the module from boot and hold mode.
Based on the log file from the radio firmware installation, I found the following information:
The firmware installation was initiated from UI:
Sep 9 00:04:47 notice ALEOS_CELL_RMFWHeaderUtil: Add/Update GENERIC firmware issued from UI
Sep 9 00:05:10 notice ALEOS_FIRMWARE: Image Switching issued from UI
Sep 9 00:05:10 notice ALEOS_FIRMWARE: Radio Module Firmware (GENERIC) is ready for activation
The firmware installation process was then executed.
Sep 9 00:05:10 notice ALEOS_SYSTEM_UpdateReboot: Processing request from to applyradio
Sep 9 00:05:10 notice ALEOS_SYSTEM_UpdateRebootMgr: Applying Radio Module firmware
Sep 9 00:05:10 alert ALEOS_FIRMWARE_RmUpdater: Radio boot-and-hold value is \[7\] update pending
Sep 9 00:05:10 alert ALEOS_FIRMWARE_RmUpdater: Found firmware MC7455_02.33.03.00_GENERIC_002.072_001.iso to recover Radio Module, not matching preferred carrier
Sep 9 00:05:10 alert ALEOS_FIRMWARE_RmUpdater: Radio Module Firmware Update
Sep 9 00:05:13 alert ALEOS_CELL_RMFWHeaderUtil: Starting radio module recovery...
Then the module still failed to enter firmware download mode, so the firmware could not be updated.
Sep 9 00:05:50 alert ALEOS_CELL_RMFWHeaderUtil: RecoverRadioModuleFirmware: failed to start SDK \[5\], continuing recovery
Sep 9 00:05:50 alert ALEOS_CELL_RMFWHeaderUtil: SetImagePath - Starting radio module firmware recovery \[0\]
Sep 9 00:05:50 notice ALEOS_CELL_RMFWHeaderUtil: Waiting for radio to enter firmware download mode
Sep 9 00:05:53 debug SWI0 SDK Process: erAbort: SDK Fatal error -> fhtaskinit:1750 Invalid Product ID
...
Sep 9 00:08:50 err ALEOS_CELL_RMFWHeaderUtil: Radio failed to enter firmware download mode
Sep 9 00:08:50 err ALEOS_CELL_RMFWHeaderUtil: Radio module firmware recovery failed
Sep 9 00:08:50 alert ALEOS_CELL_RMFWHeaderUtil: Rebooting after failed radio firmware recovery
After checking the internal system, I also found description indicating that this behavior is considered unusual.
Therefore, I think the best next step for you would be to proceed with RMA.
Hi @jerdung, thank you for reviewing. I have submitted an RMA form and will proceed with that route. Thanks again to you and @blackbow7 for the support with this.
