@Barton :
what exactly is this command? Even I didn’t hear about this command earlier…
@fs1: Yes… I tried the mentioned steps when my module was in Low power mode with ‘W_DISABLE’. If you succeeded in recovering the module, let me know the steps 
-Alex
Hot to change the PRI?
The working device has this:
Current Firmware info
---------------------
Model ID: EM7455
BOOT Version: SWI9X30C_02.08.02.00
AMSS Version: SWI9X30C_02.08.02.00
SKU ID: 1102527
Package ID:
Carrier: 1
PRI version: 001.000
Current Carrier Name: GENERIC
Current Cairier Version: 002.007_000
Build ID: 02.08.02.00_GENERIC
CWE Image Fields
----------------
BOOT Version: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
AMSS Version: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
PRI Version: 9904802 001.000 Generic-LaptopThe FCC one has this:
Current Firmware info
---------------------
Model ID: EM7455
BOOT Version: SWI9X30C_02.08.02.00
AMSS Version: SWI9X30C_02.08.02.00
SKU ID: 1102662
Package ID:
Carrier: 1
PRI version: 001.003
Current Carrier Name: GENERIC
Current Cairier Version: 002.007_000
Build ID: 02.08.02.00_GENERIC
CWE Image Fields
----------------
BOOT Version: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
AMSS Version: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
PRI Version: 9905046 001.003 Lenovo-LaptopEdit: changing does nothing. How to change NV settings?
Yes, the PRI is irrelevant. The NV setting you are looking for is written as part of the OEM vendor config. If you download the firmware package from whatever OEM vendor you got this modem from and unpack it, then you will find 3 different firmware parts (multiplied by the number of supported operators):
The latter will contain the FCC auth related setting. I have not tried, so I cannot tell you whether the variable can be changed. But I believe it is likely if you know how to create or modify .nvu files. It might also be possible using other NVRAM modification methods. I don’t know…
Note that all three file types mentioned above are containers with an aribtratry number of different files and/or images. The firmware is responsible for unpacking them and interpreting the files within, and e.g. apply specific files as NVRAM variable updates given some condition. Exactly how this is done, the restrictions that apply and other necessary info, is probably only documented internally. Or possibly to OEM vendors as well? Regular end users like us don’t have access to it. But we can always guess 
Thanks, the problem is that even if I flash the regular NVU from source.sierrawireless the FCC setting still applies.
Yes, I believe that is by design. It is Non-Volatile…
You have to actively disable the setting. The regular NVU files won’t do that. And you might also have to replace the OEM NVUP file? That might also be persistent if written to flash before. I don’t know.
Unfortunateley I have no idea on how to do that, I flashed all available files from the source.
You might wonder why I want this, with the FCC I can’t use the modem in MBIM mode. I can’t send the FCC authentication.
Switching from MBIM to QMI, then load the GobiNet driver helps, but I can’t change back to MBIM without resetting the device, which in turn will reactivate the FCC.
Hi,
Can you try below steps and see if it’s working or not…
To set Set at!pcfccauth=1:
Step 1.
at!unlock=“A710”
at!pcfccauth=1
at!pcfccauth?
Step 2. Reset device
To set Set at!pcfccauth=0:
at!unlock=“A710”
at!pcfccauth=0
Step 2. Reset device
Let me know whether this is helpful
-Alex
It would be great to know whether the tip from Rex_alex works.
But just FYI in case it doesn’t: You can send the QMI FCC auth request in MBIM mode. Look at how it is implemented in ModemManager/libqmi/libmbim. This Just Works with the recently released ModemManager 1.6.
Privileges have a password “A710” not enough.
For solutions need used engenering mode, by AT!OPENLOCK…
Example, for my Sierra EM7305:
=== activate FCC_AUTH ===
at!entercnd="A710"
OK
AT!PCFCCAUTH?
NV setting: 0
Auth enabled: 0
Lock state: 0
OK
AT!PCFCCAUTH=1
ERROR
AT!OPENLOCK?
8101A18AB3C3E66A
OK
AT!OPENLOCK="D1E128FCA8A963ED"
OK
AT!PCFCCAUTH=1
OK
AT!PCFCCAUTH?
NV setting: 1
Auth enabled: 0
Lock state: 0
OK
AT!RESET
OK
-- after reset---
at!entercnd="A710"
OK
AT!PCFCCAUTH?
NV setting: 1
Auth enabled: 1
Lock state: 0
OK=== deactivate FCC_AUTH ===
at!entercnd="A710"
OK
AT!PCFCCAUTH?
NV setting: 1
Auth enabled: 1
Lock state: 0
OK
AT!PCFCCAUTH=0
ERROR
AT!OPENLOCK?
9F618EF3F0FCE7CE
OK
AT!OPENLOCK="CFE6B46892423A75"
OK
AT!PCFCCAUTH=0
OK
AT!PCFCCAUTH?
NV setting: 0
Auth enabled: 1
Lock state: 0
OK
AT!RESET
OK
-- after reset---
at!entercnd="A710"
OK
AT!PCFCCAUTH?
NV setting: 0
Auth enabled: 0
Lock state: 0
OKOn my intended device there is no ModemManager available, which makes it a bit complicated. (umbim does not do this afair)
Does not work unfortunateley.
at!unlock="A710"
ERROR
at!pcfccauth?
ERROR
AT!ENTERCND="A710"
OK
at!pcfccauth?
NV Setting: 1
FCC Auth Enabled: 1
FCC Lock State: 1
OK
at!pcfccauth=0
ERRORThank you for this post, I can’t get into the “engenering” mode with at!unlock, I think this may be a challegene-response sequence. As it changes with every at!unlock? command.
AT!OPENLOCK?
6FF19EEBB325DB2D
OK
AT!OPENLOCK="CFE6B46892423A75"
ERRORFor EM7305, I use a Response Generator to AT!OPENLOCK by this link:
github.com/bkerler/SierraWirelessGen
For EM7455 he can not work … The algorithm has changed …
Yeah I tried that too, but it didn’t work.
Hi Guys,
I was trying this engineering mode for my EM7355 and it worked. My aim is to write the SAR BACKOFF settings permanently into the modem. Unfortunately even when I did the settings in eng. mode they were reverted to initial condition after changing the SIM and having the FW autoswitched to the carrier specific version.
Can you please help me how to do it steadily?
I also tried to apply the SARBACKOFF settings via the configuration.ini file, but that way they were not even set just once.
B4316 driver pack and windows 10 is used. Generic FW is 05.05.58.00. In the driver pack there is Verizon, ATT, Rogers, Sprint, Bell, Telus defined with their FW/nvu.
Thanks
Several years later this undocumented anti-feature is now fixed:
Repo: GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Readme: edl/sierrakeygen_README.md at master · bkerler/edl · GitHub
AT!OPENLOCK?
81F2B4F0A9E06DF2
OK
AT!OPENLOCK="21A68A014A39E0E8"
OK
AT!PCFCCAUTH=0
OK
AT!PCFCCAUTH?
NV Setting: 0
FCC Auth Enabled: 1
FCC Lock State: 1
OK
AT!PCFCCAUTH=0
OK
AT!RESET
OK
at!entercnd="A710"
OK
AT!PCFCCAUTH?
NV Setting: 0
FCC Auth Enabled: 0
FCC Lock State: 0
Why not? qmicli can run the very same command on the cdc-wdm port while in MBIM mode, it will run “QMI over MBIM” transparently.
Could you please tell me if that FCC locked device had the generic Sierra USB vid:pid (1199:9079) or a different laptop-vendor-branded one? E.g. HP, Dell?
That was some years ago, OpenWrt had no umbim with QMI support (or uqmi was not able to send FCC, something of the two). FCC in umbim/uqmi was available some time later, so while still annoying, it worked. The original post was not in the OpenWrt environment obviously. Don’t know if ModemManager would have worked back then, haven’t tried it mainly because the device I was using had little flash memory - I think.
Not sure, it’s 1199:9079 now. It was in use on a OpenWrt device for some years (not any longer) and since I had it around without any use I inserted it into a Thinkpad T460 (Win 8.1). Although automatic driver installation went fine the device was still in LPM.
I got the device as a gift, my guess is that it was originally for a Thinkpad.
I believe 9079 is a Lenovo specific PID with FCCAUTH enabled by default. The generic MC7455/EM7455 PID is 9071.
Heads up for anyone with this FCC locked modems also using ModemManager: FCC unlock procedure | ModemManager