Can you share the device to goodcloud? Can you share the device to Goodcloud?
I want to grab a log remotely and send it to quectel for analysis
I disabled the AT command that I used to enable WiFi calling on R01A08 (2024-02-01) and WiFi calling still worked. So I thought that maybe I too would be able to try R03A03 release. However, when I woke the next morning, I could not make a phone call and WiFi calling was no longer enabled on my phone. So unfortunately, I will have to stick with using R01A08 and the “ROW_Generic_3GPP_PTCRB_GCF” MBN file over the “Commercial-TMO“ one.
I believe that n71 does not allow me to use WiFi calling but n41 does, so it just depends which band my router is on. n71 is the fastest band for me and n41 is extremely slow. The R01A08 firmware has worked extremely well for me and I have not had any reboots like I had previously. I’ll be moved in the RV in a months time and I’m certain that everything will need to be re-tweaked all over again once I connect to a different tower and new location. But for now, I’m happy to not have to reset the router multiple times a day.
In either case, I think we are in agreement that the default modem firmware needs to be upgraded right away for anyone wanting a more stable experience.
This is the version we want to upgrade in the future
I decided to try out RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28) to see if it contains ROW_Generic_3GPP_PTCRB_GCF since I use both TMO and VERIZON. I don’t need it now since both SIM cards seem to connect fine, but just in case.
On RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28), I ran AT+QMBNCFG=“list” and see ROW_Generic_3GPP_PTCRB_GCF was added there.
+QMBNCFG: "List",0,1,1,"Commercial-TMO",0x0A01050F,202402061
+QMBNCFG: "List",1,0,0,"CDMAless-Verizon",0x0A010126,202304251
+QMBNCFG: "List",2,0,0,"ROW_Generic_3GPP_PTCRB_GCF",0x0A01FF09,202203161
+QMBNCFG: "List",3,0,0,"TEF_Spain_Commercial",0x0A010C00,202302071
+QMBNCFG: "List",4,0,0,"FirstNet",0x0A015300,202206171
+QMBNCFG: "List",5,0,0,"Rogers_Canada",0x0A014800,202303141
+QMBNCFG: "List",6,0,0,"Bell_Canada",0x0A014700,202111051
+QMBNCFG: "List",7,0,0,"Telus_Jasper_Canada",0x0A01F900,202304281
+QMBNCFG: "List",8,0,0,"Telus_Consumer_Canada",0x0A01FA00,202304281
+QMBNCFG: "List",9,0,0,"Commercial-Sprint",0x0A010204,202111051
+QMBNCFG: "List",10,0,0,"VoLTE-ATT",0x0A010335,202206171
+QMBNCFG: "List",11,0,0,"CDMAless_Private-Verizon",0x0A01FD28,202304271
+QMBNCFG: "List",12,0,0,"Swiss-Comm",0x0A010411,202304261
+QMBNCFG: "List",13,0,0,"Telia_Sweden",0x0A012400,202111051
+QMBNCFG: "List",14,0,0,"TIM_Italy_Commercial",0x0A012B00,202111051
+QMBNCFG: "List",15,0,0,"France-Commercial-Orange",0x0A010B21,202401081
+QMBNCFG: "List",16,0,0,"Commercial-DT-VOLTE",0x0A011F1F,202212061
+QMBNCFG: "List",17,0,0,"Germany-VoLTE-Vodafone",0x0A010449,202401201
+QMBNCFG: "List",18,0,0,"UK-VoLTE-Vodafone",0x0A010426,202401201
+QMBNCFG: "List",19,0,0,"Commercial-EE",0x0A01220B,202111051
+QMBNCFG: "List",20,0,0,"Optus_Australia_Commercial",0x0A014400,202111051
+QMBNCFG: "List",21,0,0,"Telstra_Australia_Commercial",0x0A010F00,202311071
+QMBNCFG: "List",22,0,0,"Commercial-LGU",0x0A012608,202111051
+QMBNCFG: "List",23,0,0,"Commercial-KT",0x0A01280B,202308031
+QMBNCFG: "List",24,0,0,"Commercial-SKT",0x0A01270A,202111051
+QMBNCFG: "List",25,0,0,"Commercial-Reliance",0x0A011B0C,202210211
+QMBNCFG: "List",26,0,0,"Commercial-SBM",0x0A011C0B,202401231
+QMBNCFG: "List",27,0,0,"Commercial-KDDI",0x0A010709,202401191
+QMBNCFG: "List",28,0,0,"Commercial-DCM",0x0A010D0D,202312201
+QMBNCFG: "List",29,0,0,"VoLTE-CU",0x0A011561,202310181
+QMBNCFG: "List",30,0,0,"VoLTE_OPNMKT_CT",0x0A0113E0,202312141
+QMBNCFG: "List",31,0,0,"Volte_OpenMkt-Commercial-CMCC",0x0A012010,202209221
+QMBNCFG: "List",32,0,0,"ROW_Commercial",0x0A010809,202401151
So far RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28) seems as stable as RM520NGLAAR03A03M4G_01.200.01.200 (2023-07-25) with regards to tower connection on TMO US.
Do you happen to know the difference between the RM520NGLAAR01 and RM520NGLAAR03 firmware? Are there variants of RM520N that differ in hardware specifications?
From what I know so far, the hardware won’t change
R01 and R03 are essentially the same, similar to version iterations
R01 will no longer be maintained and updated, and R01A08 may be the last version
Just installed RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28 ) now. Using Commercial_TMO MBN configuration. Wi-Fi calling is working for now but nice to know that I do have the option to switch to ROW_Generic if need be.
Glad we can all agree on this one release from here on. 
. It will make @ywp job a lot easier!
1 Like
Same here. Fingers crossed (again).
1 Like
I upgraded to RM520NGLAAR03A03M4G_01.201.01.201 (2024-03-28 ) this morning.
I am on Verizon. Will see how it goes.
Previous versions I had to force LTE band 66 and 5G NSA band n5 to get 5G at my house. Will see if it will automatically connect to 5G or it I still have to force.
1 Like
Please check the solution here: Spitz x3000 - potential bug in modem.sh check_ip(). It seems you experience similar issues.
Hey mate, it can be quite confusing for a first time “poweruser” when faced with all of this stuff. Let me know if this makes things a little bit easier. I would download the version people are describing now: RM520NGLAAR03A03M4G_01.201.01.201
Update Firmware on Spitz x3000 Router using Windows
What You Need:
- A Windows computer
- The latest firmware file for the Spitz x3000 router
Instructions:
1. Download the Firmware:
- Visit the official firmware page for the Spitz x3000 router (ensure you have the correct link).
- Download the firmware version RM520NGLAAR03A03M4G_01.201.01.201 and save it to your Downloads folder.
2. Copy the Firmware to the Router:
- Open PowerShell (search for “PowerShell” in the Start menu and run it as administrator).
- Use the following command to copy the file to the router (replace
USERNAMEwith your actual Windows username):
scp C:\Users\USERNAME\Downloads\RM520NGLAAR03A03M4G_01.201.01.201.zip root@192.168.8.1:/RM520NGLAAR03A03M4G_01.201.01.201.zip
3. Log Into Your Router and Prepare the Update:
- In the same PowerShell window, use this command to connect to your router:
ssh root@192.168.8.1
- All the following commands will be made in this window you logged into.
After logging in, unpack the firmware using:
unzip /RM520NGLAAR03A03M4G_01.201.01.201.zip -d /RM520NGLAAR03A03M4G_01.201.01.201
4. Execute the Firmware Upgrade:
- Change to the directory with the upgrade tool:
cd /usr/bin/
- Download and prepare the necessary tool:
wget https://fw.gl-inet.com/tools/quectel_tool/QFirehose-mtk7981a-sha256-c0b944
chmod 775 QFirehose-mtk7981a-sha256-c0b944 && sha256sum QFirehose-mtk7981a-sha256-c0b944
- Start the upgrade process:
./QFirehose-mtk7981a-sha256-c0b944 -f /RM520NGLAAR03A03M4G_01.201.01.201
5. Final Steps:
- Restart parts of the router:
echo 1 > /sys/devices/platform/11280000.pcie/pci0001:00/0001:00:00.0/0001:01:00.0/remove
echo 1 > /sys/devices/platform/11280000.pcie/pci0001:00/0001:00:00.0/rescan
- Verify the new firmware version:
gl_modem AT AT+QGMR
- Remove temporary files:
rm /RM520NGLAAR03A03M4G_01.201.01.201* -rf
Note: Some commands such as scp, ssh, or wget might not be available by default on all Windows systems. You may need to install additional software like PuTTY or use Windows Subsystem for Linux (WSL) to execute these commands.
1 Like
This is basically happening on both of my spitz here is the log
RM520NGLAAR03A03M4G_01.201.01.201 has become the firmware of choice as of April, 2024. I was unaware of this latest version dated 03-28-2024. Has been rock solid for me without reboots, switching bands and even WiFi calling works without having to change MBN profile on the router. Poll Closed
You already updating this, but there is still a problem?
I’m not having any issues with the RM520NGLAAR03A03M4G_01.201.01.201 version. All my problems I was having have been resolved with this version. Including WiFi calling issues. This is the latest version available for the RM520N-GL, I was also informed by Quectel that I should install this firmware version for the RM520N-GL modem. This version should be made available on the gl-inet modem download page. I only posted this because I was still getting people polling and this version was not included in that poll.
1 Like
Step 4 cannot find the file
PS C:\Windows\system32> C:\Users\USER\Desktop\spitz\RM520NGLAAR03A03M4G_01.201.01.201.zip root@192.168.8.1:/RM520NGLAAR03A03M4G_01.201.01.201.zip
PS C:\Windows\system32> ssh root@192.168.8.1
root@192.168.8.1’s password:
BusyBox v1.33.2 (2024-04-19 07:45:03 UTC) built-in shell (ash)
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|_____|| |||||___||| |____|
|| W I R E L E S S F R E E D O M
OpenWrt 21.02-SNAPSHOT, r15812+880-46b6ee7ffc
root@GL-X3000:~# unzip /RM520NGLAAR03A03M4G_01.201.01.201.zip -d /RM520NGLAAR03A03M4G_01.201.01.201
unzip: cannot find or open /RM520NGLAAR03A03M4G_01.201.01.201.zip, /RM520NGLAAR03A03M4G_01.201.01.201.zip.zip or /RM520NGLAAR03A03M4G_01.201.01.201.zip.ZIP.
root@GL-X3000:~#
Also if this matters. Whenever I “copy” the file in power shell with the command you gave me over to the router, it always opens the zip file in Windows, and the contents of the zip file is displayed. Unsure if I was supposed to select something but there’s to many files to select and also contains PDFs as well .
Hey Goggles, try navigating to the router UI now, and use the system upgrade button there. The new version is packed into the latest release, and you shouldn’t have to do any of these commands now that you can simply utilize the standard router upgrade.
Not right! The router ONLY upgrades its firmware (GL Openwrt firmware) NOT the modem module firmware!
It’s important to note that not only GL deices, but all manufacturers do not update the modem module for you; It must be done manually.
1 Like
for those interested, i got tired of fighting the bugs in the stock router firmware and flashed openwrt on it and haven’t had any more issues:
2 Likes