do you mean you have entered wrong PID before?
Do you have a normal EM7565 to make sure your windows PC is working fine?
yes, thats correct. I entered the wrong PID through router via AT command. Now, it will not accept any commands. It is in “BOOT mode” 1199 9090. No, I do not have another Sierra Wireless modem.
then did you follow the procedure above in ubuntu
No, I dont have a Linex machine or Ubuntu. I’m using Putty program connecting to my router using ROOTER firmware.
I was able to send these commands: “modprobe option
echo 1199 9090 > /sys/bus/usb-serial/drivers/option1/new_id”
But I dont know what to do after that.
Sending AT!entercnd=“A710” does not give a response, so I don’t think any “AT” commands can be sent.
This is where I’m stuck…
then do you have new /dev/ttyUSB* serial port after
echo 1199 9090 > /sys/bus/usb-serial/drivers/option1/new_id”
Well, thats the thing, I’m not sure where to look for new ports. I only have ttyUSB0 show up on my Router, and it does not respond to AT commands. Where do I look for new ports? I’ve run dmesg | grep usb…is that correct to find the new ports?
Am I supposed to receive some kind of response after entering "echo 1199 9090 > /sys/bus/usb-serial/drivers/option1/new_id” ???
Nothing happens when I enter that command. the curser just goes to the next line…
Did you check dmesg for the real pid
I just ran that command, but it listed an extremely long list of info…I’ll see if PID is listed anywhere…
you should see something like this:
[ 113.370448] usb 4-1: New USB device found, idVendor=1199, idProduct=9091
[ 113.370451] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 113.370453] usb 4-1: Product: Sierra Wireless EM7511 Qualcomm® Snapdragon™ X16 LTE-A
[ 113.370455] usb 4-1: Manufacturer: Sierra Wireless, Incorporated
[ 113.370456] usb 4-1: SerialNumber: YT22174335123456
[ 114.508557] usbcore: registered new interface driver cdc_wdm
[ 114.517879] qmi_wwan: loading out-of-tree module taints kernel.
[ 114.517988] qmi_wwan: module verification failed: signature and/or required key missing - tainting kernel
[ 114.540391] qmi_wwan 4-1:1.8: cdc-wdm0: USB WDM device
[ 114.541590] qmi_wwan 4-1:1.8 wwan0: register 'qmi_wwan' at usb-0000:03:00.0-1, WWAN/QMI device, e2:22:3a:72:ef:f5
[ 114.547482] usbcore: registered new interface driver qmi_wwan
[ 114.703384] usbcore: registered new interface driver usbserial
[ 114.705161] usbcore: registered new interface driver usbserial_generic
[ 114.706868] usbserial: USB Serial support registered for generic
[ 114.762078] usbcore: registered new interface driver qcserial
[ 114.762163] usbserial: USB Serial support registered for Qualcomm USB modem
[ 114.762178] usbserial: USB Serial support registered for Qualcomm USB modem
[ 114.790530] qcserial 4-1:1.0: Qualcomm USB modem converter detected
[ 114.792633] usb 4-1: Qualcomm USB modem converter now attached to ttyUSB0
[ 114.801093] qcserial 4-1:1.2: Qualcomm USB modem converter detected
[ 114.801226] usb 4-1: Qualcomm USB modem converter now attached to ttyUSB1
[ 114.811976] qcserial 4-1:1.3: Qualcomm USB modem converter detected
[ 114.812111] usb 4-1: Qualcomm USB modem converter now attached to ttyUSB2
Sorry for late reply, I got kicked off of here for too many replies…lol. I was able to resolve my problem by using mincom to connect to dev/ttyUSB2 and sending the command to change back the PID. The reason my commands weren’t working at first was because I didn’t have “echo” turned on in minicom settings. I thank you for trying so hard to help me. It was much appreciated.
I’m back to my original issue of being stuck in Low Power Mode because of IMSWITCH=1 flag. I believe it’s caused by this:
carrier name mismatch
config name mismatch
There seems to be some sort of an issues when updating firmware…
You need to use at!impref to switch the pri
I think I may have done that already, but I’ll try again when I get home. Stuck at work right now. Thanks for replying. I’ll give it a try in a little while.
Just giving an update that I was able to resolve my issue by using openlock and than issuing an impref command to clear the mismatch errors. That deactivated the Low Power Mode. Thanks for your all of help. Very appreciated.