RUTx14 mobile modem in the EDL - how to recover

Networking Solutions
1

Hello,

I am having problems with my mobile modem in a RUTX14 router.

It all started when the modem could no longer establish a data connection. SMS messages were still sent and received correctly, but mobile data did not work. Running:

gsmctl -A AT+CGPADDR=1

returned the correct public IP:

+CGPADDR: 1, (correct Public IP)

I then tried to upgrade the modem firmware from EG12EAPAR01A09M4G to EG12EAPAR01A14M4G using modem_updater. Unfortunately, the upgrade process got stuck at around 6% for ~30 minutes. After resetting the router, the modem appears to be in EDL (Emergency Download) mode.

Current USB devices:

lsusb
Bus 003 Device 001: ID 1d6b:0002
Bus 001 Device 001: ID 1d6b:0002
Bus 003 Device 003: ID 0a12:0001
Bus 001 Device 024: ID 05c6:9008
Bus 002 Device 001: ID 1d6b:0003
Bus 003 Device 002: ID 05e3:0610

I cannot access the modem using:

/dev/ttyUSB*
gsmctl
modem_updater

It seems completely unresponsive.

Question:
Is there any way to reanimate or recover the EG12-EA modem in this state without physically removing it from the RUTX14? If not, what is the recommended procedure to restore the modem via EDL mode?

Thank you in advance for any guidance!

3

Greetings, torto,

For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 16179.

Thank you,
V.

4

This topic was automatically closed after 60 days. New replies are no longer allowed.

5

Hello,

I hope this message finds you well.

Below is a brief summary of our remote session for your reference:

During the session, we attempted to update the modem firmware; however, the modem was not reachable and was not detected by the router itself. Based on these observations, the issue appears to be hardware-related rather than configuration- or firmware-related.

I have checked the warranty status using the device’s serial number, and it is still covered under warranty. Therefore, I would recommend contacting your reseller to initiate the RMA process for further investigation and replacement if necessary.

Warm regards,
V.