Does the new firmware (07.22.1) that was released today solve the modem issue with the 5G connections? I don’t see a modem firmware update.
Hello,
I hope you are doing well.
Our R&D team has developed a beta version of the modem firmware, and we are currently looking for users who are still experiencing this issue to test the firmware and verify whether it resolves the problem.
If you are willing to participate, we can arrange a remote session with our R&D team to install the firmware and investigate the issue further.
Please let me know if you would be available for such a session.
Kind regards,
V.
It would be even greater to release this beta version (including a clear path back to the previous firmware) officially which would allow the ordinary user to try it out without any remote session. That would for sure get much more people trying it out I guess. 
2 Likes
Don’t have timeslots for remote sessions, but have more than few problem devices at customers now in 4G so that they work.
What is the timeline for releasing this?
Hello,
At the moment, there is no exact ETA for the new release, as the beta version is still undergoing testing.
1 Like
Hallo again,
what is the state? One more week has been passed…
Hello Leigh,
thank you very much for your post and for sharing the downgrade procedure.
I can confirm that the same modem firmware problem also affected my Teltonika RUTC50 eSIM version with the Quectel RG520N-EBDC modem.
The modem firmware was already RG520NEBDCR03A05M4G_A0.300.A0.300 before I sent the device in for repair. After almost one month I received it back, but the same problems were still there. So in my case, it was very likely not a hardware issue, but related to the modem firmware.
With A05 installed, normal operation in 5G/Auto mode was not really possible. The modem became unstable, the connection sometimes dropped, and the router behaved unpredictably. In some cases, when using 5G/Auto, the WebUI froze for up to around two minutes. Sometimes the internal modem disappeared completely and was no longer visible/usable in the router until a restart or recovery action.
The only way to get a somewhat usable connection was to manually select specific bands instead of using full auto mode.
I followed your idea and downgraded the modem firmware to:
RG520NEBDCR03A04M4G_01.200.01.200
I did it via SSH on my RUTC50, using a stable WAN connection and not the mobile connection for the download. In my case, I first had to install sshfs, otherwise the downgrade failed before flashing.
The successful commands were:
sh opkg update && opkg install sshfs modem_updater modem_updater -v RG520NEBDCR03A04M4G_01.200.01.200
After the downgrade, I checked it with:
sh modem_updater -g gsmctl -A ATI
The modem now reports:
Revision: RG520NEBDCR03A04M4G_01.200.01.200
Interestingly, after the downgrade, A05 is no longer offered to me by modem_updater -g. The RUT WebUI also does not offer an update back to A05 anymore and shows the current modem firmware as the newest installed version.
Since the downgrade, 5G/Auto mode looks much more stable on my RUTC50. The modem connects again to Vodafone Germany with 5G NSA and does not crash immediately like before.
So this issue is not only affecting the RUTX50. It also affects at least my RUTC50 eSIM version with RG520N-EBDC.
Thanks again for pointing us in the right direction.
Kind regards,
Stefan
3 Likes
Thank you so much sharing this detailed information.
Any update about progress with new firmware for modem? At the moment I can only use 4G.
I finally had to deploy the downgrade following Leigh’s instructions, too.
The steps were successfully finished and I have 5G connections again.
I can confirm Stefan’s notice, that A05 is no longer offered.
I can confirm my RUTM30 suffers from the same 5G problems with the A.05 firmware. A 5G connection is maintained and working sometimes, but especially in sub-optimal conditions 5G connections are very flaky, it seems the A.05 moden isn’t falling back to 4G connections soon enough to prevent connection problems.
1 Like
I don’t understand this. It worked fine before the update of the modem but is now unusable in 5G. Until you have sorted this out can’t you simply make an ”update” to the previous version which worked and then when a new functioning version is available make a new real update?
2 Likes
Yes, the downgrade is the only thing that works.
Remember to update the firmware for the device first (RUTC50 in my case, RUTC_R_00.07.23.1 | 2026.05.05) using the Web UI, and only after it’s complete, update the modem firmware using the terminal app (PuTTY or other).
Now it´s working on 5G (SA).
I have 2 RUTM30’s in the same area same firmware. 100m apart. One is an EE e-sim working without issue. One is on O2 networks with physical sim causing issues.
Hands up who is having issues on O2?
I have 30+ more spread around the country on different networks in different territories having no issues but mostly Three networks.