thanks for getting back to me. According to Quectel’s release note file V0305_A0.300.A0.300, which I am unfortunately not allowed to upload here, A01M4G is a pre-mass production firmware release for engineering samples.
I do appreciate that Teltonika is getting a brand new modem like the RG520N to market quickly, and the whole TRB501 package has the perfect combination of specs for me. That said, I do expect updates to mass production firmware releases after some time.
In addition, the changelog from A01M4G to A05M4G is massive and includes many useful features. A05M4G is the first firmware version that supports Regulation (EU) 2022/30, and will therefore be mandatory to operate this equipment in the EU.
Again, if you cannot provide a firmware file yet, I am happy to flash the Quectel package myself through the CLI with the right instructions.
A modem firmware upgrade is typically performed only when it is mandatory specifically, when we know that updating the firmware will resolve a confirmed issue.
In most cases firmware upgrades are carried out only after the underlying problem has been identified. The commands required for this process are not publicly available, as incorrect use could damage the device.
If you believe a firmware upgrade is required for certain features, please let us know which features you are referring to.
I believe I did make myself clear why I consider an upgrade to be mandatory in my previous post.
If you believe that shipping pre-production firmware which does not support 2022/30 is acceptable, fine. I’ll go ahead and figure the flashing procedure out myself. If it works, I’ll keep the device. If not, I’ll return it anyway, either working or broken.
@NojuHD I had ChatGPT come up with a step-by-step guide, and it makes sense. Essentially running QFirehose - you can obtain the latest version from Quectel - after putting the modem into USB mode. The latter seems to be the greatest risk, as the way Teltonika configured the modem this wasn’t meant to happen. I haven’t decided yet whether to spend some hours of my life devoting to that, yet the upcoming days might provide an opportunity. The other option would be to simply send this thing back to Teltonika, which has become even more attractive since I found out the 2nd batch will feature eSIM functionality with no way to enable this on a 1st batch device.
Thank you for the clarification. In this case, let’s continue the communication privately so we can assist you with your matter. I have sent a form to the email address you used to register on the community forum. Once you complete the form, we will contact you privately with further details.
When filling out the form please use ticked ID “16393”.
thanks for reaching out via e-mail and offering a remote session. Unfortunately, while I have local access to the device, it is my single point of connection to the internet so this might be hard to do. Would access via RMS help? If not, I am confident I’d be able to follow instructions even if the process is not straightforward - I’ll figure it out.