## Technical Finding: RF Calibration NV Data is Placeholder/Empty in XQCN Backup **Module:** Quectel EG18-EA (MikroTik LHG LTE18) **Firmware:** EG18EAPAR01A13M4G_01.001.01.001 **Status:** AT+CFUN? returns +CFUN: 5 (stuck in FTM); AT+CFUN=1 and AT+QRFTEST="mode",0 both return +CME ERROR **Backup file:** XQCN export via QPST, taken *after* the module entered CFUN:5 (not a pre-failure backup) ### Method The XQCN (XML QCN) backup was parsed and inspected directly. Under `Storage/NV_Items`, the backup contains 53 RF calibration item files referenced by path, e.g.: ``` /nv/item_files/rfnv/00028883 /nv/item_files/rfnv/00028884 ... /nv/item_files/rfnv/00029635 ``` Each entry's `EFS_Data` stream is zlib-compressed (`78 9C` header). All 53 streams were decompressed individually. ### Finding All 53 rfnv calibration items — despite covering distinct NV item IDs that would normally hold different band/parameter-specific calibration values — decompress to **byte-for-byte identical content**: ``` 00 00 01 00 D8 00 00 FF E6 00 DC 00 D2 00 C8 00 BE 00 B4 00 AA 00 A0 00 E6 00 DC 00 D2 00 C8 00 BE 00 B4 00 AA 00 A0 00 ``` Real per-band RF calibration data varies across items. Identical content across all 53 distinct calibration files indicates these are default/placeholder values rather than genuine factory calibration data, and is consistent with the module lacking valid RF NV data — which explains why AT+CFUN=1 and AT+QRFTEST="mode",0 both fail with a generic phone-failure/CME error instead of returning the module to normal functionality. ### Conclusion / Request This backup was taken after the module was already in the CFUN:5 state, so it reflects the corrupted/empty calibration state rather than a usable restore point. No pre-failure backup exists. Given that the RF NV/QCN data appears to be genuinely missing or defaulted (not just a stuck mode flag), requesting either: 1. A donor/reference XQCN or QCN for the exact same hardware/firmware combination (EG18EAPAR01A13M4G_01.001.01.001) that can at least restore basic RF functionality, understanding that per-device calibration precision (IMEI-specific trims) would not be exact, or 2. Guidance on the official recovery procedure for this state (e.g., EDL/9008 recovery with a matching NV template), or 3. RMA/repair path for the module given this occurred after using Quectel's own QFlash tool for an intended firmware version change. IMEI: [insert IMEI]