I need RM500U-EN firmware

IoT Modules 5G Module
, ,
1

Hi Quectel team,

I’m currently using an RM500U-EA module that came from my ISP’s CPE device. I believe the firmware is carrier-customized, and some AT commands are not working.

Here are my current firmware details:

AT+GMR
RM500UEAAAR03A06M2G_01.001.01.001
OK

When I try to lock a specific band using:
AT+QCFG=“band”,0,1
It returns: +CME ERROR: 4

Other commands like AT+QNWLOCK and AT+QMBNCFG also return +CME ERROR: 4.

I suspect the current firmware is restricted by the carrier. I would like to request the original or generic Quectel firmware (non-OEM) for RM500U-EA, so I can unlock full AT command support including band locking and NR5G features.

I have already downloaded QFlash and am ready to proceed with flashing once I receive the correct firmware.

Appreciate your assistance. Thank you!

2

Where did you see this command in relation to your modem?
Always start from checking with test syntax, e.g. AT+QCFG=?

3

Thanks for the reply!

I saw AT+QCFG="band" and AT+QNWLOCK being used by other RM500U-EA users on forums and tutorials to lock LTE/NR bands. Since my module is the same model, I expected it to work too, but looks like mine is firmware-restricted.

Yes, I tried AT+QCFG=? just now, and it seems like my module doesn’t list "band" at all under available parameters.

Here is the output I received:

AT+QCFG=?
+CME ERROR: 4
AT+QCFG=?
+QCFG: “usbnet”,(1,2,3,5,11,13,15)
+QCFG: “nat”,(0-2)
+QCFG: “usbcfg”,(1-65535),(1-65535),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
+QCFG: “ims”,(0,1)
+QCFG: “pcie/mode”,(0,1)
+QCFG: “ethernet”,(0,1)
+QCFG: “uartat”,(0,1)
+QCFG: “usbid”,(1-65535),(1-65535)
+QCFG: “multiusbnet”,(1-4),(0-4)
+QCFG: “usbmac”,(sipa_usb0,usb0,usb1,usb2,usb3)
+QCFG: “hostmac”,(usb0,usb1,usb2,usb3),
+QCFG: “staticarp”,(0,usb0,usb1,usb2,usb3),
+QCFG: “lanip”,,,<lease_time>
+QCFG: “lanip_ex”,<lease_time>
+QCFG: “loopback”,(0-15)
+QCFG: “usage/apmem”
+QCFG: “usage/apfs”
+QCFG: “proxyarp”,(0,1)
+QCFG: “5glan”,(1-8),(0,1)
+QCFG: “vlan”,(0,1)
+QCFG: “autoapn”,(0,1)
+QCFG: “usbmode”,(host,device,auto)
+QCFG: “usbreset”
+QCFG: “usbspeed”,(11,20,30,auto)
+QCFG: “rp_filter”,(0-2)
+QCFG: “ipa”,(0-2)
+QCFG: “netmask”,(0,1)
+QCFG: “thermal/modem”,(1,2),(0~110000)
+QCFG: “tts”,(0,1)
+QCFG: “pm/powersave”,(0,1,2,3)
+QCFG: “vonr”,(0,1)
+QCFG: “pcie/direct”,(0,1)
+QCFG: “pack”,(0,1)
+QCFG: “mtu”,(1-4),<lan_mtu>,<wan_mtu>
+QCFG: “eth_at”,(0,1)
+QCFG: “iq_vser”,(0,1)
+QCFG: “clat”,(0,1)
+QCFG: “quecdumptime”,(0~5000000)
+QCFG: “ip6/cfg”,“neigh”
+QCFG: “mmrej_policy”,(0,1)
+QCFG: “pdp/duplicatechk”,(0,1)
+QCFG: “simdet_ctl”,(0,1)
+QCFG: “napt”,(0,1)
+QCFG: “erase_block_maxcount”

OK

As you can see, commands like band, nwlock, or other cellular-related parameters are missing. I suspect this is due to a restricted or carrier-customized firmware.

That’s why I’m requesting the original or generic Quectel firmware (non-OEM), so I can unlock band locking, QNWLOCK, and other standard AT commands for network control.

Appreciate any help or direction for getting the correct firmware.

4

It is not.
Search for “band”, etc. in the AT command guide for your modem.

6

You’re on the wrong way.
You need the right manual, not firmware.

7

I also ran AT+QADBKEY? and got the following response:

AT+QADBKEY
+CME ERROR: 4
AT+QADBKEY?
+QADBKEY: P1AF11_15_29_11

OK
ATI
Quectel
RM500U-EA
Revision: RM500UEAAAR03A06M2G

OK

also -

RDY
ati
Quectel
RM500U-EA
Revision: RM500UEAAAR03A06M2G

OK
AT+CSQ
+CSQ: 19,99

OK
AT+CPIN?
+CPIN: READY

OK
AT+COPS?
+COPS: 0,0,“U Mobile”,16

OK
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=“band”
+CME ERROR: 4
AT+QCFG=?
+QCFG: “usbnet”,(1,2,3,5,11,13,15)
+QCFG: “nat”,(0-2)
+QCFG: “usbcfg”,(1-65535),(1-65535),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
+QCFG: “ims”,(0,1)
+QCFG: “pcie/mode”,(0,1)
+QCFG: “ethernet”,(0,1)
+QCFG: “uartat”,(0,1)
+QCFG: “usbid”,(1-65535),(1-65535)
+QCFG: “multiusbnet”,(1-4),(0-4)
+QCFG: “usbmac”,(sipa_usb0,usb0,usb1,usb2,usb3)
+QCFG: “hostmac”,(usb0,usb1,usb2,usb3),
+QCFG: “staticarp”,(0,usb0,usb1,usb2,usb3),
+QCFG: “lanip”,,,<lease_time>
+QCFG: “lanip_ex”,<lease_time>
+QCFG: “loopback”,(0-15)
+QCFG: “usage/apmem”
+QCFG: “usage/apfs”
+QCFG: “proxyarp”,(0,1)
+QCFG: “5glan”,(1-8),(0,1)
+QCFG: “vlan”,(0,1)
+QCFG: “autoapn”,(0,1)
+QCFG: “usbmode”,(host,device,auto)
+QCFG: “usbreset”
+QCFG: “usbspeed”,(11,20,30,auto)
+QCFG: “rp_filter”,(0-2)
+QCFG: “ipa”,(0-2)
+QCFG: “netmask”,(0,1)
+QCFG: “thermal/modem”,(1,2),(0~110000)
+QCFG: “tts”,(0,1)
+QCFG: “pm/powersave”,(0,1,2,3)
+QCFG: “vonr”,(0,1)
+QCFG: “pcie/direct”,(0,1)
+QCFG: “pack”,(0,1)
+QCFG: “mtu”,(1-4),<lan_mtu>,<wan_mtu>
+QCFG: “eth_at”,(0,1)
+QCFG: “iq_vser”,(0,1)
+QCFG: “clat”,(0,1)
+QCFG: “quecdumptime”,(0~5000000)
+QCFG: “ip6/cfg”,“neigh”
+QCFG: “mmrej_policy”,(0,1)
+QCFG: “pdp/duplicatechk”,(0,1)
+QCFG: “simdet_ctl”,(0,1)
+QCFG: “napt”,(0,1)
+QCFG: “erase_block_maxcount”

OK
AT+QENG=“neighbourcell”
+CME ERROR: 4
AT+QENG=“neighbourcell”
+QENG: “neighbourcell intra”,“LTE”,1650,135,-16,-16,34,1,-1,-,-,-,-
+QENG: “neighbourcell intra”,“LTE”,1650,59,-88,-14,0,-3,255,-1,-1,16

OK
AT+CPIN?
+CME ERROR: 4
AT+CPIN?
+CPIN: READY

OK
AT+QENG=“servingcell”
+QENG: “servingcell”,“CONNECT”,“LTE”,“FDD”,502,18,6928B0B,135,1650,3,5,5,2485,-93,-18,-64,-1,5,0,33

OK
AT+QENG=“neighbourcell NR5G”
+CME ERROR: 4
AT+QENG=“neighbourcell NR5G”
+CME ERROR: 4
AT+QENG=“neighbourcell NR5G”
+CME ERROR: 4
AT+CGDCONT?
+CGDCONT: 1,“IPV4V6”,“my3g”,“0.0.0.0”,0,0,0,0,0,0,0,0,0,0
+CGDCONT: 11,“IPV4V6”,“ims”,“0.0.0.0”,0,0,0,2,0,0,0,0,0,0

OK
AT+CGATT?
+CGATT: 1

OK
AT+QIACT?
OK
AT+CGPADDR=1
+CGPADDR: 1,“21.14.67.75”,“2405:3800:080a:f5d2:0000:0000:0000:0001”

OK
AT+QPING=1,“8.8.8.8”
+CME ERROR: 514
AT+QPING=1,“8.8.8.8”
+CME ERROR: 514
AT+QNWPREFCFG=“mode_pref”
+QNWPREFCFG: “mode_pref”,LTE

OK
AT+QNWPREFCFG?
+CME ERROR: 4
AT+QNWPREFCFG?
+CME ERROR: 4
AT+QNWPREFCFG?
+CME ERROR: 4
AT+QCFG=“nwscanmode”
+CME ERROR: 4
AT+QCFG=“nwscanmode”
+CME ERROR: 4
AT+QCFG=“nwscanmode”
+CME ERROR: 4
AT+QCFG=“nwscanmode”
+CME ERROR: 4
AT+QCFG=“band”,0
+CME ERROR: 4
AT+QCFG=“band”,0
+CME ERROR: 4
AT+QCFG=“band”,0
+CME ERROR: 4
AT+QNWLOCK=“common/lte”,1,3
+CME ERROR: 4
AT+QNWLOCK=“common/lte”,1,3
+CME ERROR: 4
AT+QNWLOCK=“common/lte”,1,3
+CME ERROR: 4
AT+QNWLOCK?
+CME ERROR: 4
AT+QNWLOCK?
+CME ERROR: 4
AT+QNWLOCK?
+CME ERROR: 4
AT+QNWLOCK?
+CME ERROR: 4
AT+QNWLOCK?
+CME ERROR: 4
AT+QMBNCFG=“list”
+CME ERROR: 4
AT+QMBNCFG=“list”
+CME ERROR: 4
AT+QMBNCFG=“list”
+CME ERROR: 4
AT+QMBNCFG=“Deactivate”
+CME ERROR: 4
AT+QMBNCFG=“Deactivate”
+CME ERROR: 4
AT+QCFG=“usbnet”
+QCFG: “usbnet”,1

OK
AT+QCFG=?
+QCFG: “usbnet”,(1,2,3,5,11,13,15)
+QCFG: “nat”,(0-2)
+QCFG: “usbcfg”,(1-65535),(1-65535),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1),(0,1)
+QCFG: “ims”,(0,1)
+QCFG: “pcie/mode”,(0,1)
+QCFG: “ethernet”,(0,1)
+QCFG: “uartat”,(0,1)
+QCFG: “usbid”,(1-65535),(1-65535)
+QCFG: “multiusbnet”,(1-4),(0-4)
+QCFG: “usbmac”,(sipa_usb0,usb0,usb1,usb2,usb3)
+QCFG: “hostmac”,(usb0,usb1,usb2,usb3),
+QCFG: “staticarp”,(0,usb0,usb1,usb2,usb3),
+QCFG: “lanip”,,,<lease_time>
+QCFG: “lanip_ex”,<lease_time>
+QCFG: “loopback”,(0-15)
+QCFG: “usage/apmem”
+QCFG: “usage/apfs”
+QCFG: “proxyarp”,(0,1)
+QCFG: “5glan”,(1-8),(0,1)
+QCFG: “vlan”,(0,1)
+QCFG: “autoapn”,(0,1)
+QCFG: “usbmode”,(host,device,auto)
+QCFG: “usbreset”
+QCFG: “usbspeed”,(11,20,30,auto)
+QCFG: “rp_filter”,(0-2)
+QCFG: “ipa”,(0-2)
+QCFG: “netmask”,(0,1)
+QCFG: “thermal/modem”,(1,2),(0~110000)
+QCFG: “tts”,(0,1)
+QCFG: “pm/powersave”,(0,1,2,3)
+QCFG: “vonr”,(0,1)
+QCFG: “pcie/direct”,(0,1)
+QCFG: “pack”,(0,1)
+QCFG: “mtu”,(1-4),<lan_mtu>,<wan_mtu>
+QCFG: “eth_at”,(0,1)
+QCFG: “iq_vser”,(0,1)
+QCFG: “clat”,(0,1)
+QCFG: “quecdumptime”,(0~5000000)
+QCFG: “ip6/cfg”,“neigh”
+QCFG: “mmrej_policy”,(0,1)
+QCFG: “pdp/duplicatechk”,(0,1)
+QCFG: “simdet_ctl”,(0,1)
+QCFG: “napt”,(0,1)
+QCFG: “erase_block_maxcount”

OK

From what I understand, this key indicates the firmware is a custom/private carrier build. This would explain why several AT commands are not available, including QCFG=“band”, QNWLOCK, and NR5G-related queries.

Just sharing this in case it helps confirm the firmware restriction.

I appreciate your feedback.

However, I’ve gone through official AT command documentation, and I’ve also compared outputs from other users with generic firmware. On my current module, several standard AT commands are unavailable, and the QADBKEY value suggests it’s a custom firmware build.

If you have a better suggestion or another way to access band locking and NR5G features, I’m open to trying it. Otherwise, flashing to a generic Quectel firmware still seems like the most logical path to restore full command support.

Thanks again for your time.

1 Like
8

Could you please share the title of the document?

9

Dear @max22
I have sent the firmware and AT command to your email, please check.

11

RM500UEAAAR03A12M2G_01.001.01.001. pls send latest firmware