It *should work in theory. Should have CFUN 1 if successful.
Other possibilities:
CFUN 7 (incomplete/incompatible EFS) which is pretty much the same behavior as CFUN 5.
Unlikely but still a possibility:
Sahara dump mode:
This would mean it really really doesn’t like the state of the EFS (worse than cfun7) and will try to dump logs to the DM/Diagnosis port as soon as it’s opened by QPST then reboot.
In that case you’d need to do another erase all flash (or at least wipe the efs2 to get back to CFUN 5)
My current firmware is RM520NGLAAR03A04M4G.
I purchased this module a month ago and upgraded the firmware from A03 to A04 using Qfirehose before putting it into use.
However, I did not use the -e option during the process.
@silvia Hi Silvia, I am encountering the exact same issue. During a recent firmware flash via QFIL, I mistakenly checked the ‘Erase All Before Download’ option and unfortunately failed to back up my QCN beforehand.
My hardware is the RM520N-GL. Due to the erased NAND , the module is now locked in factory mode (CFUN: 5).
Could you kindly share a clean/default QCN file to help me unbrick this unit? I fully understand and accept the potential RF performance loss and calibration inaccuracies that come with using a generic QCN. > Your assistance would be greatly appreciated. Thank you.