EG912U-GL eSIM EID not returned with AT+QESIM="eid"

EMPROTEK · October 16, 2025, 11:02am

Hi,
I am using a Quectel EG912U-GL module with an ST4SIM_200M_VFDFPN8 eSIM. The module works normally with ICCID, IMEI, IMSI, etc., but when I try to query the EID with:

AT+QESIM="eid"

I get the following response:

+QESIM: "eid",8500000A,""
OK

The EID field is empty. Other AT commands for ICCID and network info work fine.

Module Info:

Firmware: EG912UGLAAR03A13M08
SIM: ST4SIM_200M_VFDFPN8
ICCID: 8944477200003118032F

Questions:

Does this module/firmware version support reading EID from this eSIM?
Are there any additional commands or configuration needed to enable EID reading?
Could this be a limitation of the eSIM profile (ST4SIM_200M_VFDFPN8) or firmware?

Any guidance would be appreciated.

FULL
i have module eg912u-gl with eSIM ST4SIM_200M_VFDFPN8 only it show iccid
NOT EID
/* Start AT SYNC: Send AT every 500ms, if receive OK, SYNC success, if no OK return after sending AT 10 times, SYNC fail */
AT
AT
OK
ATI
ATI
Quectel
EG912U
Revision: EG912UGLAAR03A13M08

OK
ATI
ATI
Quectel
EG912U
Revision: EG912UGLAAR03A13M08

OK

/* Use ATV1 to set the response format */
ATV1
ATV1
OK

/* Use ATE1 to enable echo mode */
ATE1
ATE1
OK

/* Use AT+CMEE=2 to enable result code and use verbose values */
AT+CMEE=2
AT+CMEE=2
OK

/* Get the baudrate, if the value is 0 (auto baudrate), then it will be set to 115200 (fixed baudrate) to assure reliable communication and avoid any problems caused by undetermined baudrate between DCE and DTE, value of IPR should be saved with AT&W */
AT+IPR?
AT+IPR?
+IPR: 115200

OK

/* Use ATI to get module information of Manufacturer ID, Device module and Firmware version */
ATI
ATI
Quectel
EG912U
Revision: EG912UGLAAR03A13M08

OK

/* Use AT+GSN to query the IMEI of module */
AT+GSN
AT+GSN
869487067875525

OK
AT+QURCCFG=“URCPORT”,“uart1”
AT+QURCCFG=“URCPORT”,“uart1”
OK

/* Use AT+CPIN? to query the SIM card status : SIM card inserted or not, locked or unlocked */
AT+CPIN?
AT+CPIN?
+CPIN: READY

OK

/* Use AT+CIMI to query the IMSI of SIM card */
AT+CIMI
AT+CIMI
204047651359097

OK

/* Use AT+QCCID to query ICCID number of SIM card */
AT+QCCID
AT+QCCID
+QCCID: 8944477200003118032F

OK

/* Use AT+CSQ to query current signal quality */
AT+CSQ
AT+CSQ
+CSQ: 19,99

OK

/* Use AT+CREG? /AT+CGREG? to query the network registration status. */
AT+CREG?
AT+CREG?
+CREG: 0,2

OK
AT+CGREG?
AT+CGREG?
+CGREG: 0,2

OK

/* Make sure the Antenna is connected and the network is normal */
AT+QESIM=“eid”
AT+QESIM=“eid”
+QESIM: “eid”,8500000A,“”

OK

EMPROTEK · October 17, 2025, 10:41am

i have update the file but it send different data

/* Use ATI to get module information of Manufacturer ID, Device modle and Firmware version */
ATI
ATI
Quectel
EG912U
Revision: EG912UGLAAR03A20M08

OK
/* Use AT+QCCID to query ICCID number of SIM card */
AT+QCCID
AT+QCCID
+QCCID: 8944477200003118032F

OK

/* Use AT+CIMI to query the IMSI of SIM card */
AT+CIMI
AT+CIMI
204047651359097

OK
AT+QESIM=“eid”
AT+QESIM=“eid”
+QESIM: “eid”,1,“2”,“6F00”

OK

dansw · October 17, 2025, 2:11pm

That is an SGP.02 eUICC, the LPA should not be able to query it. 6F00 is a generic “reject” command.

EMPROTEK · October 18, 2025, 6:09am

What can I do? I urgently need eSIM for my project—can you help me with it?

dansw · October 20, 2025, 9:11am

That is an eSIM (eUICC SGP.02) however it’s tied to some operator so you need to sign a contract with them specifically. Reach out to where you bought the eSIM and ask them which operator it is tied to, then reach out to them to sign a contract, get setup on their platform etc.

If you’re looking for the same eSIM that you have in your phone, that is an SGP.22 eUICC. (Google SGP.22 eUICC and you should find it)

Alvin295337 · January 16, 2026, 8:35am

Dear @EMPROTEK ,

Good Day,

Thank You for reaching out to us.

Based on the issue it seems the result code 8500000A in your response indicates an “APDU status error” . This means that while the module attempted to communicate with your eSIM to retrieve the EID, the low-level command (Application Protocol Data Unit) failed or returned an error status from the eSIM chip itself.

1.Does this module/firmware support reading EID?
For Esim, EG912U ,probably requires a specilized firmware for the LPA.

Are additional commands or configurations needed?
Not realy.But you may check the follwing first.
SIM Slot Selection: If your hardware uses dual SIM interfaces, ensure the correct slot is selected using AT+QDSIM before querying the EID.

Initialization Status: The error may occur if the module’s kernel hasn’t finished initializing the eSIM stack. You can query the initialization status with AT+QINISTA

Is this a limitation of the eSIM profile or firmware?
This could be the potential issue, need speciliazed firmware.Could you query your current full version for us, kindly use AT+QGMR command

Thank You!

usamamughal8345 · September 2, 2026, 6:41am

Hi, following a related but distinct SIM issue on the same module (EG912U-GL) that may share underlying cause with what’s reported here, posting in case it’s useful context, or please redirect me to a more appropriate thread if this isn’t the right place.

Module: EG912U-GL, firmware EG912UGLAAR03A18M08

Symptom: AT+CPIN? returns +CPIN: READY with one specific SIM (Zong, Pakistan), but returns +CME ERROR: 10 (“SIM not inserted”) with every other physical nano-SIM we’ve tested, two other Pakistani carriers and two UK IoT SIM providers — reproduced identically across two separate assembled boards.

Diagnostics completed:

AT+QSIMDET=1,0 / 1,1 - both accepted (OK), no change in outcome
AT+QSIMVOLT=0/1/2 - returns CME ERROR: 58 on all values, appears unsupported on this firmware
Oscilloscope capture of SIM_RST/SIM_DATA during power-up: the working SIM shows initial toggling settling into a stable high state (~3.3V, successful ATR); the failing SIM shows similar initial activity but drops to ~240–320mV and stays low, consistent with the module attempting one voltage-class recognition, failing, and powering down the interface (matches the behavior described in Quectel’s own “SIM card cannot be recognized” troubleshooting guide)
Cross-checked the same “failing” SIM on a different modem chipset (SIMCom A7670E) which registers and initializes normally there, confirming the SIM card itself isn’t defective

Question: Is there a known ATR/voltage-class negotiation limitation on this firmware build, and is there an alternate way to force SIM voltage class given AT+QSIMVOLT isn’t accepted? Does the issue is with Sim-lock for specific regions/companies?