Thanks, yep I’m going to wait another week or so and if there’s no firmware fix released or official way to downgrade, I’ll do that. Works at acceptable speeds in my current location on 4G.
Hi Vilius,
It has been exactly one month since I submitted the requested troubleshoot files and information for ticket 18624-1.
I have not received any feedback, hotfix, or progress update since then. In the meantime, my RUTC50 remains unusable for its primary purpose (5G connectivity) because the A05 modem firmware still triggers the “UE identity” and “N1 mode” failures.
Could you please provide a status update on this?
-
Is there an ETA for a modem firmware patch?
-
If a patch is not imminent, are you finally providing a supported method to downgrade the modem firmware to A04?
The current workaround of forcing the router to 4G mode is not a sustainable solution for a expensive 5G product. I look forward to your concrete update.
As this is a widespread issue, one that can maybe considered ‘critical’, and that has been identified for over a month now; can I suggest that Teltonika ‘pin’ a read only update to appear at the top of the list.
Given the length of time this has been running, its severity and the number of devices affected; it would not be unreasonable for this to be updated on a daily basis. I assume this is possible because this should be being reviewed on a daily basis internally.
A little bit of context would be helpful on the first update, showing cause, effect, previous actions, constraints and third party involvement.
Updating the firmware to 7.22.1 enabled the router to work on 5G for about two weeks, but this morning I’m getting the same disconnecting and ‘modem unreachable’ as I did before the upgrade. Changing back to 4G only makes it functional.
No changes have been made prior to it breaking again.
Was about to push the button on a purchase of a number of RUT951s at work but I think I’m going to look to another brand now. Can’t believe there hasn’t been a fix!
Hi Vilius and the Teltonika Team,
I am writing this with great urgency as my RUTC50 has now become completely unusable. After weeks of struggling with 5G instability on the RG520NEBDCR03A05M4G modem firmware, the system has now spontaneously degraded to a point of total failure.
Current State of the Device:
-
Total Connectivity Loss: Even 4G (LTE) connectivity has now failed. The modem is stuck in an endless boot-loop.
-
WebUI Breakdown: The Status Overview, System, and Services pages no longer load any data. The interface is unresponsive or shows empty fields.
-
Filesystem/RPC Errors: My logs are flooded with
Permission deniederrors andubusfailures. Basic commands likeubus call network.interface notify_protoare failing, likely because the/tmppartition is full due torpcdcore dumps. -
Critical Log Snippets:
-
daemon.err mobifd: Unable to get l3_device for 'mob1s3a1' -
daemon.notice netifd: Command failed: ubus call network.interface notify_proto (...) (Permission denied) -
daemon.err mobifd: Attribute "l3_device" was not found in 'status' response -
user.emerg rpcd[...]: corrupted size vs. prev_size
-
This degradation happened spontaneously while the router was forced to 4G. It appears the ongoing modem errors caused by the A05 firmware eventually lead to a memory leak or a complete lock-up of the system’s RPC bus, bricking the device’s functional stability.
I can no longer generate a Troubleshoot file because the system service responsible for it has crashed.
I have already waited a month for a solution (Ticket 18624-1). I need an immediate solution:
-
How do I recover this device when the WebUI is broken and the filesystem is read-only/full?
-
When will a modem firmware patch (A06) or an official downgrade tool be available?
This is a flagship 5G product that is currently performing worse than a paperweight. Please advise immediately.
It looks like they’ve stopped replying to these threads unfortunately - shame, I quite liked their products. I’m going to wait another month and then buy another brand with hopefully better support.
Look in the RutX50 thread, there seems to be a modem update available, hopefully for the RutC50 also.
Yes, there is. I have RUTC50 with A05 and it says update available.
As the last one was dud, I will wait few days myself with this. 
Sad this mess, I decided to return my unit… Just unacceptable
Hello,
We want to sincerely apologize for the experience you’ve had with your device and for the delays in getting back to you. We completely understand your frustration and would like to thank you for your patience.
With the help of the information provided in this thread, our R&D team analyzed the situation and identified the issue, which was escalated to the modem manufacturer with critical priority. Now we’ve received a new firmware, which passed internal tests, therefore please test whenever possible.
If you are currently on modem firmware A05, please update using the WebUI DFOTA method:
1. Navigate to System → Firmware → Update Firmware → Modem update.
2. Proceed with the update from the server.
You should be able to run on 5G again without the instability after this is applied.
We understand this took longer than expected, that the communication clarity was less than desired and we apologize for the delay in providing a resolution. If you encounter any issues after applying the update, please reply here and we’ll ensure it receives prompt attention.
Thank you for sticking with us this long, and we hope this puts things right.
Best regards,
Justas
As an owner of a RUTM30 i have been following this problem across the RUTX50, RUTC50 and RUTM30 with much interest. Reading back to the various threads, it strikes me that the trigger (firmware update) and the workaround (set the connection to 4G/3g only) was already staring us in the face 1-2 weeks after the first messages mentioning the problems (setting to ‘4G/3G only’ first mentioned around 5th of april) but wasn’t recognized as such. What may have complicated things is that the 5G problems weren’t consistent across providers and locations (i experienced that when traveling through Europe in the first weeks of April).
What keeps my mind busy is not putting blame on Teltonika (i’m sure they are trying hard), but the question how Teltonika and we as a community can prevent such repeated lenghty periods of problems.
- Can we as a community improve in details provided or improve in reporting work-arounds?
- or should we back-off as soon as we see that cases are taken in by Teltonika to prevent burdening the staff more?
- Will Teltonika examine easier firmware downgrades to remedy such problems for the time being?
It goes without saying that we all would like to see such problems being prevented by extensive testing, but where people work people make mistakes, i am glad Teltonika is actively participating in this community.
I think Teltonika needs to do the same thing for modem firmware as they do for device firmware. Provide two branches for modem firmware update. Stable and latest (beta). This way, users can test the latest firmware and report issues if they find any. We also need the ability to roll back to previous (stable) modem firmware from the web gui in case there is a serious stability issue. This way, Teltonika can work quitely with modem vendor and iron out all the issues users reported. Once all issues are resolved, push another test firmware for users to test. If no issues are found, push the firmware as stable. Everyone is happy.
I am on RUTC50 with firmware: RUTC_R_00.07.23.4 and modem version RG520NEBDCR03A06M4G and I still experience this issue all of a sudden. Randomly dropping 5G.
Tried switching to 4G but that’s really slow at current location. When switching back to 5G Auto I saw “n1 mode not allowed” error.