zukota.com

EM7455 Control Center

2017-10-18T11:56:00+08:00

EM7455 Control Center is a software for monitoring and configuring Sierra Wireless EM7455 / MC7455 4G device installed in many modern laptops and tablets. It works with generic Sierra Wireless EM7455, MC7455, Lenovo branded EM7455, Dell branded DW5811e devices.

It provides functions absent in standard Windows settings, such as:

Main window

Signal strength indication in bars and in dBm
Signal quality indication for 3G and LTE in bars and in dBm
Cellular radio power off and on to save battery
Connect and disconnect from the Internet
Access technology indication (LTE, 3G, 2G)
Frequency band indication
Access technology and frequency bands selection
Current temperature and voltage
Reboot device
…and more

It provides a very convenient tray icon with the current cellular network and Internet connection status – which is especially useful with Windows 10, that has no access technology indication:

Tray icon

Tray menu

You can check your APN details and IP address assigned by the cellular carrier:

EM7455 Control Center also has some brief diagnostic feature – to show your mobile number, device IMEI, SIM card data, and device lock status, including SIM lock, Network lock, other locks and calibration information:

Requirements

EM7455 Control Center requires enabled COM ports.
Refer to this post to enable COM ports.

Supported OS: Windows 7, Windows 8, Windows 10.

Updates

Oct 18 2017: Version 1.01

Now MC7455 devices are supported.
Small improvements.

Download and Purchase

EM7455 Control Center is shareware. After downloading it on your computer you can use it for unlimited time with some restrictions. In order to unlock all features of the program, you need to purchase a license using the button below. The registration price is just $15.

Use the following button to purchase EM7455 Control Center. All the payments are handled by PayPro Global processing service, transactions are SSL encrypted and secure. After successful payment you will receive an email with your personal EM7455 Control Center registration key.

EM7345 Control Center

2016-05-25T11:56:00+08:00

EM7345 Control Center is a software for monitoring and configuring Sierra Wireless EM7345 4G device installed in many Lenovo laptops and tablets.

It provides functions absent in standard Windows settings, such as:

Main window

Signal strength indication in bars and in dBm
Signal quality indication for 3G and LTE in bars and in dBm
Cellular radio power off and on to save battery
Connect and disconnect from the Internet
Access technology indication (LTE, 3G, 2G)
Frequency band indication
Access technology and frequency bands selection
Reboot device
…and more

You can monitor how much data went through the EM7345 for the current session or total: aaa

It provides a very convenient tray icon with the current cellular network and Internet connection status – which is especially useful with Windows 10, that has no access technology indication:

Tray icon

Tray menu

You can check your APN details and IP address assigned by the cellular carrier:

EM7345 Control Center also has some brief diagnostic feature – to show your mobile number, device IMEI, SIM card data, and device lock status, including SIM lock, Network lock, and other locks:

Requirements

EM7345 Control Center requires enabled COM ports.
Refer to this post to enable COM ports.

Supported OS: Windows 7, Windows 8, Windows 10.

Updates

Feb 5 2016: Version 1.01

Carrier IQ spyware disable feature. For safety, works only with firmware version 1529.05 and higher as lower versions
could brick EM7345 when attempting to disable Carrier IQ. Read more about Carrier IQ here.
Cell ID indication feature. Lets you know which exactly cellular tower you are using at any moment.

Update 1.01

May 25 2016: Version 1.2

Accurate connection status feature. It shows the current Windows Internet connection status instead of the modem PDP connection status.
Radio power on and off feature. You can now turn EM7345 radio power off when not using it, and that can greatly increase the battery life.
Internet connect and disconnect feature. Now you can connect and disconnect the Internet with just one click.
Tray icon now is green color when Internet is connected and gray when not connected. Tray tool tip is more informational now.
You can Connect/Disconnect the Internet and set the Radio Power from the tray menu as well.

Main window

Download and Purchase

EM7345 Control Center is shareware. After downloading it on your computer you can use it for unlimited time with some restrictions. In order to unlock all features of the program, you need to purchase a license using the button below. The registration price is just $15.

Use the following button to purchase EM7345 Control Center. All the payments are handled by PayPro Global processing service, transactions are SSL encrypted and secure. After successful payment you will receive an email with your personal EM7345 Control Center registration key.

Sierra Wireless EM7455: how to make it work with an older Lenovo laptop

2017-03-19T11:56:00+08:00

Lenovo and other manufacturers, namely Dell are starting to use the newest Quallcomm 9×30 based cellular modems. The only modem manufacturer so far is Sierra Wireless and the model is XX7455, where XX is the form factor code. We’ll be using an m.2 modem, so our model number is EM7455. For the older generation laptops that only have a mini-PCI slot there’s the MC7455 model. Currently, the EM7455 is available as Sierra Wireless generic version (the model is EM7455), Lenovo version (the model is EM7455 as well), and Dell version (the model is DW5811e). All three versions are the same hardware, the only difference is the firmware and there are no restrictions for cross-flashing too.

EM7455 is not intended for use with the previous generation Lenovo laptops, such as X240, X1 Carbon Gen2, etc, but we’re going to fix that!

But if we check the price online we can see that the Dell variant is the cheapest, it can be bought for about $90, while Lenovo costing about $160. So I bought a Dell DW5811e from Aliexpress, the only thing to care about here is the part number, which should be 1102424. The part number is printed on the device sticker.

There are other part numbers around, one of which is known to be a 3G only model, so it’s not recommended to buy any other part number.

So when I got the module, there is the following to be realized:

My laptop’s BIOS whitelist will accept only EM7345 and EM7355 modules. If any other device is installed, the laptop won’t boot with “1802 Unauthorized network card is installed” message. So in order to make it work, I need to change the ID to mimic the EM7355.
I’m using Windows 7, and it lacks the generic MBIM driver, so the EM7455 won’t work out from the box. It will require the drivers, but the problem is, that the drivers from Sierra Wireless, Lenovo and Dell will work only for the device with the stock ID, and I cannot use those ID because of the #1. The solution here is to use the MBIM driver for the EM7355. If you’re using Windows 8 or 10, then you don’t need to worry about the MBIM drivers, as the Windows will use its built in drivers for that.

Put your laptop to sleep, open the case and install the EM7455. Secure the screw and connect the antennas properly. Then wake up the laptop. You’ll see the following unrecognized devices in the Device Manager:

In this case there are 4 devices total: MBIM interfaces, AT command port, NMEA GPS port and diagnostics port, the last 3 all being COM ports. If you see less than 4 devices, that can be because some of them disabled, refer to this post to enable missing COM ports and change the compostion to MBIM.

As for now, we cannot use the device as it is, because on next reboot we will see the 1802 error from BIOS. We need to change the IDs of the device to those whitelisted in our Lenovo BIOS. For the X240, we change the IDs to those mimicking EM7355.

Download and unpack the following file to the following path for example: “D:\DRV”

Open the properties window of the device that has the following ID: USB\VID_413C&PID_81B6&REV_0006&MI_03. Note the “MI_03” at the end, in case of a different ID, MI_03 always corresponds to the AT command COM port.

Then click “Update Driver”:

Click “Browse my computer for driver software”:

Select “Show All Devices” and click “Next”:

Click “Have Disk”:

Enter the path you extracted the drivers into: “D:\DRV\Driver\Driver\X64“. Use “D:\DRV\Driver\Driver\X86” if your Windows is 32 bit:

Click “OK”. You will see the following window. In the left list, select “Huawei Incorporated“, then in the right list, select “HUAWEI Mobile Broadband – Modem” and click “Next”:

You will see the following warning from Windows. Just click “Yes”:

The driver will be installed:

Click “Close” and check the device in the Device Manager:

Check the assigned COM port number in the “Modem” tab:

In our case, it is COM59. Now open that port COM59 in Putty or any terminal program. Type “ATI” and press Enter:

That means the device is working and we can change the device IDs now.

Enter the following commands and note the responses:

ate1
OK
at!entercnd="A710"
OK

Let’s check the current device VID/PIDs:

at!usbvid?
!USBVID:
413C
 
OK
at!usbpid?
!USBPID:
APP : 81B6
BOOT: 81B5
 
OK

Exactly the same IDs we see in the Device Manager. Let’s change the VID to Sierra Wireless:

at!usbvid=1199
OK

And PIDs to those mimicking EM7355:

at!usbpid=901F,9078
OK

Note that we set the boot ID to be 9078, that’s the standard ID for Lenovo PID. We need this PID to be Lenovo in order to be able to install drivers necessary when you need to flash your EM7455.

Let’s check if our changes are successful:

at!usbvid?
!USBVID:
1199
 
OK
at!usbpid?
!USBPID:
APP : 901F
BOOT: 9078
 
OK

All seems ok, let’s reboot the EM7455:

at!reset
OK

Your EM7455 will reboot and after a couple of minutes you’ll see it in the Device Manager. Note that device IDs will be changed now:

Download and unpack the following file (vanilla EM7355 drivers) into the following path: “D:\DRV\EM7355”

Now, if you have Windows 8 or later, the EM7455 MBIM device will be automatically recognized and drivers will be installed for it automatically. Proceed with the following step only if you have Windows 7.

Only for Windows 7: Open the device properties for “USB\VID_1199&PID_901F&REV_0006&MI_0c” and click “Update Driver”:

Click “Browse my computer for driver software”:

Navigate to “D:\DRV\EM7355\Uncompressed_Drivers_Only\Drivers” and click “Next”:

The driver will be installed:

Click “Close” and proceed with the following step no matter what Windows version you have.

Now for each of the remaining 3 devices without drivers repeat the above procedure, open the device properties, click “Update Driver” and point Windows to “D:\DRV\EM7355\Uncompressed_Drivers_Only\Drivers” if you have Windows 7 or 8, or to “D:\DRV\EM7355\Uncompressed_Win10Drivers_Only” if you have Windows 10:

You’ll end up with all device drivers correctly installed:

Now you can safely reboot your laptop without worrying about the 1802 error. Unfortunately, with my X240 I see the following message every time I reboot the laptop:

For some odd reason, the X240 BIOS recognizes the EM7455 as an SSD disk. This can potentially be fixed by isolating some m.2 contacts on the EM7455 that are used for SSD signals by the X240 motherboard, but I didn’t investigate that. I press ESC every time I reboot to skip that error. I reboot rarely and use sleep all the time, anyways. With the newer Lenovo laptops, you won’t see this error as their motherboard is already aware of the EM7455.

Congratulations, your EM7455 is ready to use with your older Lenovo laptop!

Sierra Wireless EM7455: How to enable COM ports

2017-02-01T11:56:00+08:00

Various EM7455 devices coming from different brands and sale channels are often configured differently. They come with different firmware versions installed, different settings, and some ports can be switched on or off. Sometimes COM ports are off when you get the device, but it is useful to have a COM port enabled in order to do extended diagnostics and alter some settings that are normally not possible.

So what do you need to enable the COM ports for your EM7455?

The instructions below are for Windows users. If you can easily find your way in Linux, just skip it and note that you only basically need to run ./swi_setusbcomp.pl –-usbcomp=8 to enable COM ports. Follow this link for more info: https://www.mork.no/~bjorn/MC7455-fix-orig.txt

Method 1. Recommended and safe.

Download and unpack the following image file: UbuntuLive.7z

Then, download and install UltraISO software. Trial mode is enough for our purposes. UltraISO download link.

Insert a spare empty USB Flash Drive into your laptop. Make sure it’s 8GB or more. Smaller drive won’t work because this image was prepared on a 8GB USB Flash drive.

Launch UltraISO and open the image file “UbuntuLive.ima” you downloaded previously. Use File -> Open menu to do that. Then, navigate to Bootable -> Write Disk Image. You will see the following window:

Make sure that the correct USB Flash drive is selected in Disk Drive field. Make sure it’s not your disk C: or any of your hard drives. Don’t change any other options. Then click “Write” to write the image to the USB Flash drive. After it’s done, close UltraISO.

Now you need to reboot your laptop and enter the BIOS. Make sure that the boot settings in your BIOS is set to “Legacy mode” and not to “UEFI mode”. Also make sure that booting from USB Flash drive is enabled in your BIOS. Then save your BIOS settings and exit from the BIOS. If all is correct, you will see Ubuntu Live boot menu. Select “Try Ubuntu without installing” in the menu and press ENTER. Ubuntu will boot and you should see the Ubuntu desktop:

Now, right-click on the desktop and select “Open Terminal”. Enter the following commands:

sudo -i

and then

./swi_usbcomp.pl

The sample output is shown below:

ubuntu@ubuntu:~$ sudo -i
root@ubuntu:~# ./swi_usbcomp.pl 
Running in MBIM mode (driver=cdc_mbim)
MBIM OPEN succeeded
QMI msg '0x0021' returned status = 1
MBIM QMI support verified
supports 33 QMI subsystems:
  0x00 (1.5)    'QMI_CTL'    - Control service
  0x01 (1.67)    'QMI_WDS'    - Wireless data service
  0x02 (1.14)    'QMI_DMS'    - Device management service
  0x03 (1.25)    'QMI_NAS'    - Network access service
  0x04 (1.6)    'QMI_QOS'    - Quality of service, err, service 
  0x05 (1.10)    'QMI_WMS'    - Wireless messaging service
  0x07 (1.3)    'QMI_AUTH'    - Authentication service
  0x08 (1.2)    'QMI_AT'    - AT command processor service
  0x09 (2.1)    'QMI_VOICE'    - Voice service
  0x0a (2.24)    'QMI_CAT2'    - Card application toolkit service (new)
  0x0b (1.45)    'QMI_UIM'    - UIM service
  0x0c (1.4)    'QMI_PBM'    - Phonebook service
  0x0f (1.0)    'QMI_TEST'    - Test service
  0x10 (2.0)    'QMI_LOC'    - Location service 
  0x11 (1.0)    'QMI_SAR'    - Specific absorption rate service
  0x17 (1.0)    'QMI_TS'    - Thermal sensors service
  0x18 (1.0)    'QMI_TMD'    - Thermal mitigation device service
  0x1a (1.16)    'QMI_WDA'    - Wireless data administrative service
  0x1d (1.1)    'QMI_CSVT'    - Circuit switched videotelephony service
  0x22 (1.0)    'QMI_COEX'    - Coexistence service
  0x24 (1.0)    'QMI_PDC'    - Persistent device configuration service
  0x29 (1.0)    'QMI_RFRPE'    - RF radiated performance enhancement service
  0x2a (1.0)    'QMI_DSD'    - Data system determination service
  0x2b (1.0)    'QMI_SSCTL'    - Subsystem control service
  0x2e (1.0)    'unknown'    - 
  0x30 (1.0)    'unknown'    - 
  0x31 (1.0)    'unknown'    - 
  0x36 (1.0)    'unknown'    - 
  0xe1 (1.0)    'QMI_RMS'    - Remote management service
  0xf0 (1.0)    'unknown'    - 
  0xf3 (1.0)    'unknown'    - 
  0xf5 (1.0)    'unknown'    - 
  0xf6 (1.0)    'unknown'    - 
QMI msg '0x0022' returned status = 1
Got QMI DMS client ID '3'
QMI msg '0x555b' returned status = 1
Current USB composition: 9
USB compositions:
   0 - HIP  DM    NMEA  AT    MDM1  MDM2  MDM3  MS      NOT SUPPORTED
   1 - HIP  DM    NMEA  AT    MDM1  MS                  NOT SUPPORTED
   2 - HIP  DM    NMEA  AT    NIC1  MS                  NOT SUPPORTED
   3 - HIP  DM    NMEA  AT    MDM1  NIC1  MS            NOT SUPPORTED
   4 - HIP  DM    NMEA  AT    NIC1  NIC2  NIC3  MS      NOT SUPPORTED
   5 - HIP  DM    NMEA  AT    ECM1  MS                  NOT SUPPORTED
   6 - DM   NMEA  AT    QMI                             SUPPORTED
   7 - DM   NMEA  AT    RMNET1 RMNET2 RMNET3            NOT SUPPORTED
   8 - DM   NMEA  AT    MBIM                            SUPPORTED
*  9 - MBIM                                             SUPPORTED
  10 - NMEA MBIM                                        NOT SUPPORTED
  11 - DM   MBIM                                        NOT SUPPORTED
  12 - DM   NMEA  MBIM                                  NOT SUPPORTED
  13 - Config1: comp6    Config2: comp8                 NOT SUPPORTED
  14 - Config1: comp6    Config2: comp9                 NOT SUPPORTED
  15 - Config1: comp6    Config2: comp10                NOT SUPPORTED
  16 - Config1: comp6    Config2: comp11                NOT SUPPORTED
  17 - Config1: comp6    Config2: comp12                NOT SUPPORTED
  18 - Config1: comp7    Config2: comp8                 NOT SUPPORTED
  19 - Config1: comp7    Config2: comp9                 NOT SUPPORTED
  20 - Config1: comp7    Config2: comp10                NOT SUPPORTED
  21 - Config1: comp7    Config2: comp11                NOT SUPPORTED
  22 - Config1: comp7    Config2: comp12                NOT SUPPORTED
QMI msg '0x0023' returned status = 1
root@ubuntu:~#

We can see that the current USB composition for the EM7455 is set to 9, which is MBIM only. We need to have MBIM and also COM ports for the AT commands and NMEA GPS data. So we need the USB composition 8.

Just enter the following command to set the USB composition to 8:

./swi_usbcomp.pl –-usbcomp=8

The output is shown below:

root@ubuntu:~# ./swi_usbcomp.pl --usbcomp=8
Running in MBIM mode (driver=cdc_mbim)
MBIM OPEN succeeded
QMI msg '0x0021' returned status = 1
MBIM QMI support verified
supports 33 QMI subsystems:
  0x00 (1.5)    'QMI_CTL'    - Control service
  0x01 (1.67)    'QMI_WDS'    - Wireless data service
  0x02 (1.14)    'QMI_DMS'    - Device management service
  0x03 (1.25)    'QMI_NAS'    - Network access service
  0x04 (1.6)    'QMI_QOS'    - Quality of service, err, service 
  0x05 (1.10)    'QMI_WMS'    - Wireless messaging service
  0x07 (1.3)    'QMI_AUTH'    - Authentication service
  0x08 (1.2)    'QMI_AT'    - AT command processor service
  0x09 (2.1)    'QMI_VOICE'    - Voice service
  0x0a (2.24)    'QMI_CAT2'    - Card application toolkit service (new)
  0x0b (1.45)    'QMI_UIM'    - UIM service
  0x0c (1.4)    'QMI_PBM'    - Phonebook service
  0x0f (1.0)    'QMI_TEST'    - Test service
  0x10 (2.0)    'QMI_LOC'    - Location service 
  0x11 (1.0)    'QMI_SAR'    - Specific absorption rate service
  0x17 (1.0)    'QMI_TS'    - Thermal sensors service
  0x18 (1.0)    'QMI_TMD'    - Thermal mitigation device service
  0x1a (1.16)    'QMI_WDA'    - Wireless data administrative service
  0x1d (1.1)    'QMI_CSVT'    - Circuit switched videotelephony service
  0x22 (1.0)    'QMI_COEX'    - Coexistence service
  0x24 (1.0)    'QMI_PDC'    - Persistent device configuration service
  0x29 (1.0)    'QMI_RFRPE'    - RF radiated performance enhancement service
  0x2a (1.0)    'QMI_DSD'    - Data system determination service
  0x2b (1.0)    'QMI_SSCTL'    - Subsystem control service
  0x2e (1.0)    'unknown'    - 
  0x30 (1.0)    'unknown'    - 
  0x31 (1.0)    'unknown'    - 
  0x36 (1.0)    'unknown'    - 
  0xe1 (1.0)    'QMI_RMS'    - Remote management service
  0xf0 (1.0)    'unknown'    - 
  0xf3 (1.0)    'unknown'    - 
  0xf5 (1.0)    'unknown'    - 
  0xf6 (1.0)    'unknown'    - 
QMI msg '0x0022' returned status = 1
Got QMI DMS client ID '3'
QMI msg '0x555b' returned status = 1
Current USB composition: 9
USB compositions:
   0 - HIP  DM    NMEA  AT    MDM1  MDM2  MDM3  MS      NOT SUPPORTED
   1 - HIP  DM    NMEA  AT    MDM1  MS                  NOT SUPPORTED
   2 - HIP  DM    NMEA  AT    NIC1  MS                  NOT SUPPORTED
   3 - HIP  DM    NMEA  AT    MDM1  NIC1  MS            NOT SUPPORTED
   4 - HIP  DM    NMEA  AT    NIC1  NIC2  NIC3  MS      NOT SUPPORTED
   5 - HIP  DM    NMEA  AT    ECM1  MS                  NOT SUPPORTED
   6 - DM   NMEA  AT    QMI                             SUPPORTED
   7 - DM   NMEA  AT    RMNET1 RMNET2 RMNET3            NOT SUPPORTED
   8 - DM   NMEA  AT    MBIM                            SUPPORTED
*  9 - MBIM                                             SUPPORTED
  10 - NMEA MBIM                                        NOT SUPPORTED
  11 - DM   MBIM                                        NOT SUPPORTED
  12 - DM   NMEA  MBIM                                  NOT SUPPORTED
  13 - Config1: comp6    Config2: comp8                 NOT SUPPORTED
  14 - Config1: comp6    Config2: comp9                 NOT SUPPORTED
  15 - Config1: comp6    Config2: comp10                NOT SUPPORTED
  16 - Config1: comp6    Config2: comp11                NOT SUPPORTED
  17 - Config1: comp6    Config2: comp12                NOT SUPPORTED
  18 - Config1: comp7    Config2: comp8                 NOT SUPPORTED
  19 - Config1: comp7    Config2: comp9                 NOT SUPPORTED
  20 - Config1: comp7    Config2: comp10                NOT SUPPORTED
  21 - Config1: comp7    Config2: comp11                NOT SUPPORTED
  22 - Config1: comp7    Config2: comp12                NOT SUPPORTED
QMI msg '0x555c' returned status = 1
QMI msg '0x0023' returned status = 1
root@ubuntu:~#

Check again if the USB composition switch was successful:

root@ubuntu:~# ./swi_usbcomp.pl 
Running in MBIM mode (driver=cdc_mbim)
MBIM OPEN succeeded
QMI msg '0x0021' returned status = 1
MBIM QMI support verified
supports 33 QMI subsystems:
  0x00 (1.5)    'QMI_CTL'    - Control service
  0x01 (1.67)    'QMI_WDS'    - Wireless data service
  0x02 (1.14)    'QMI_DMS'    - Device management service
  0x03 (1.25)    'QMI_NAS'    - Network access service
  0x04 (1.6)    'QMI_QOS'    - Quality of service, err, service 
  0x05 (1.10)    'QMI_WMS'    - Wireless messaging service
  0x07 (1.3)    'QMI_AUTH'    - Authentication service
  0x08 (1.2)    'QMI_AT'    - AT command processor service
  0x09 (2.1)    'QMI_VOICE'    - Voice service
  0x0a (2.24)    'QMI_CAT2'    - Card application toolkit service (new)
  0x0b (1.45)    'QMI_UIM'    - UIM service
  0x0c (1.4)    'QMI_PBM'    - Phonebook service
  0x0f (1.0)    'QMI_TEST'    - Test service
  0x10 (2.0)    'QMI_LOC'    - Location service 
  0x11 (1.0)    'QMI_SAR'    - Specific absorption rate service
  0x17 (1.0)    'QMI_TS'    - Thermal sensors service
  0x18 (1.0)    'QMI_TMD'    - Thermal mitigation device service
  0x1a (1.16)    'QMI_WDA'    - Wireless data administrative service
  0x1d (1.1)    'QMI_CSVT'    - Circuit switched videotelephony service
  0x22 (1.0)    'QMI_COEX'    - Coexistence service
  0x24 (1.0)    'QMI_PDC'    - Persistent device configuration service
  0x29 (1.0)    'QMI_RFRPE'    - RF radiated performance enhancement service
  0x2a (1.0)    'QMI_DSD'    - Data system determination service
  0x2b (1.0)    'QMI_SSCTL'    - Subsystem control service
  0x2e (1.0)    'unknown'    - 
  0x30 (1.0)    'unknown'    - 
  0x31 (1.0)    'unknown'    - 
  0x36 (1.0)    'unknown'    - 
  0xe1 (1.0)    'QMI_RMS'    - Remote management service
  0xf0 (1.0)    'unknown'    - 
  0xf3 (1.0)    'unknown'    - 
  0xf5 (1.0)    'unknown'    - 
  0xf6 (1.0)    'unknown'    - 
QMI msg '0x0022' returned status = 1
Got QMI DMS client ID '3'
QMI msg '0x555b' returned status = 1
Current USB composition: 8
USB compositions:
   0 - HIP  DM    NMEA  AT    MDM1  MDM2  MDM3  MS      NOT SUPPORTED
   1 - HIP  DM    NMEA  AT    MDM1  MS                  NOT SUPPORTED
   2 - HIP  DM    NMEA  AT    NIC1  MS                  NOT SUPPORTED
   3 - HIP  DM    NMEA  AT    MDM1  NIC1  MS            NOT SUPPORTED
   4 - HIP  DM    NMEA  AT    NIC1  NIC2  NIC3  MS      NOT SUPPORTED
   5 - HIP  DM    NMEA  AT    ECM1  MS                  NOT SUPPORTED
   6 - DM   NMEA  AT    QMI                             SUPPORTED
   7 - DM   NMEA  AT    RMNET1 RMNET2 RMNET3            NOT SUPPORTED
*  8 - DM   NMEA  AT    MBIM                            SUPPORTED
   9 - MBIM                                             SUPPORTED
  10 - NMEA MBIM                                        NOT SUPPORTED
  11 - DM   MBIM                                        NOT SUPPORTED
  12 - DM   NMEA  MBIM                                  NOT SUPPORTED
  13 - Config1: comp6    Config2: comp8                 NOT SUPPORTED
  14 - Config1: comp6    Config2: comp9                 NOT SUPPORTED
  15 - Config1: comp6    Config2: comp10                NOT SUPPORTED
  16 - Config1: comp6    Config2: comp11                NOT SUPPORTED
  17 - Config1: comp6    Config2: comp12                NOT SUPPORTED
  18 - Config1: comp7    Config2: comp8                 NOT SUPPORTED
  19 - Config1: comp7    Config2: comp9                 NOT SUPPORTED
  20 - Config1: comp7    Config2: comp10                NOT SUPPORTED
  21 - Config1: comp7    Config2: comp11                NOT SUPPORTED
  22 - Config1: comp7    Config2: comp12                NOT SUPPORTED
QMI msg '0x0023' returned status = 1

Nice, it worked! All we need now is to reset the EM7455 in order for the new USB composition to take effect. Enter the following command:

./swi_usbcomp.pl –-reset

root@ubuntu:~# ./swi_usbcomp.pl --reset
Running in MBIM mode (driver=cdc_mbim)
MBIM OPEN succeeded
QMI msg '0x0021' returned status = 1
MBIM QMI support verified
supports 33 QMI subsystems:
  0x00 (1.5)    'QMI_CTL'    - Control service
  0x01 (1.67)    'QMI_WDS'    - Wireless data service
  0x02 (1.14)    'QMI_DMS'    - Device management service
  0x03 (1.25)    'QMI_NAS'    - Network access service
  0x04 (1.6)    'QMI_QOS'    - Quality of service, err, service 
  0x05 (1.10)    'QMI_WMS'    - Wireless messaging service
  0x07 (1.3)    'QMI_AUTH'    - Authentication service
  0x08 (1.2)    'QMI_AT'    - AT command processor service
  0x09 (2.1)    'QMI_VOICE'    - Voice service
  0x0a (2.24)    'QMI_CAT2'    - Card application toolkit service (new)
  0x0b (1.45)    'QMI_UIM'    - UIM service
  0x0c (1.4)    'QMI_PBM'    - Phonebook service
  0x0f (1.0)    'QMI_TEST'    - Test service
  0x10 (2.0)    'QMI_LOC'    - Location service 
  0x11 (1.0)    'QMI_SAR'    - Specific absorption rate service
  0x17 (1.0)    'QMI_TS'    - Thermal sensors service
  0x18 (1.0)    'QMI_TMD'    - Thermal mitigation device service
  0x1a (1.16)    'QMI_WDA'    - Wireless data administrative service
  0x1d (1.1)    'QMI_CSVT'    - Circuit switched videotelephony service
  0x22 (1.0)    'QMI_COEX'    - Coexistence service
  0x24 (1.0)    'QMI_PDC'    - Persistent device configuration service
  0x29 (1.0)    'QMI_RFRPE'    - RF radiated performance enhancement service
  0x2a (1.0)    'QMI_DSD'    - Data system determination service
  0x2b (1.0)    'QMI_SSCTL'    - Subsystem control service
  0x2e (1.0)    'unknown'    - 
  0x30 (1.0)    'unknown'    - 
  0x31 (1.0)    'unknown'    - 
  0x36 (1.0)    'unknown'    - 
  0xe1 (1.0)    'QMI_RMS'    - Remote management service
  0xf0 (1.0)    'unknown'    - 
  0xf3 (1.0)    'unknown'    - 
  0xf5 (1.0)    'unknown'    - 
  0xf6 (1.0)    'unknown'    - 
QMI msg '0x0022' returned status = 1
Got QMI DMS client ID '3'
QMI msg '0x555b' returned status = 1
Current USB composition: 8
USB compositions:
   0 - HIP  DM    NMEA  AT    MDM1  MDM2  MDM3  MS      NOT SUPPORTED
   1 - HIP  DM    NMEA  AT    MDM1  MS                  NOT SUPPORTED
   2 - HIP  DM    NMEA  AT    NIC1  MS                  NOT SUPPORTED
   3 - HIP  DM    NMEA  AT    MDM1  NIC1  MS            NOT SUPPORTED
   4 - HIP  DM    NMEA  AT    NIC1  NIC2  NIC3  MS      NOT SUPPORTED
   5 - HIP  DM    NMEA  AT    ECM1  MS                  NOT SUPPORTED
   6 - DM   NMEA  AT    QMI                             SUPPORTED
   7 - DM   NMEA  AT    RMNET1 RMNET2 RMNET3            NOT SUPPORTED
*  8 - DM   NMEA  AT    MBIM                            SUPPORTED
   9 - MBIM                                             SUPPORTED
  10 - NMEA MBIM                                        NOT SUPPORTED
  11 - DM   MBIM                                        NOT SUPPORTED
  12 - DM   NMEA  MBIM                                  NOT SUPPORTED
  13 - Config1: comp6    Config2: comp8                 NOT SUPPORTED
  14 - Config1: comp6    Config2: comp9                 NOT SUPPORTED
  15 - Config1: comp6    Config2: comp10                NOT SUPPORTED
  16 - Config1: comp6    Config2: comp11                NOT SUPPORTED
  17 - Config1: comp6    Config2: comp12                NOT SUPPORTED
  18 - Config1: comp7    Config2: comp8                 NOT SUPPORTED
  19 - Config1: comp7    Config2: comp9                 NOT SUPPORTED
  20 - Config1: comp7    Config2: comp10                NOT SUPPORTED
  21 - Config1: comp7    Config2: comp11                NOT SUPPORTED
  22 - Config1: comp7    Config2: comp12                NOT SUPPORTED
QMI msg '0x002e' returned status = 1
eof
    ...propagated at ./swi_usbcomp.pl line 251.
root@ubuntu:~#

Now you can close the terminal and reboot the Ubuntu. Remove the USB Flash drive from your laptop and restore the boot settings in your BIOS if you altered it. Now boot back to Windows and you’ll see 3 COM ports appear in the Device Manager: AT port for commands, NMEA port for GPS data and Quallcomm diagnostic port. All of these ports can be very useful and I will describe working with them in one of my next posts.

That was the preferred method of enabling COM ports and you should try it first. There is also another way, which is not recommended, because it requires to install some Windows drivers that potentially can flash your EM7455 automatically without asking any permission. If you still need to do that, proceed with caution!

Method 2. Not really recommended.

First, note what brand your device is (look at the sticker) and check the device ID in the Windows Device Manager. There can be the following ID for the EM7455 module:

VID  : PID
413C : 81B6 - Dell DW5811e LTE version
413C : 81B8 - Dell DW5811e HSPA only version (do not get this)
1199 : 9071 - EM7455 Generic Sierra Wireless
1199 : 9079 - EM7455 Lenovo version

Then you’ll need to download your device’s corresponding driver:

Download Lenovo drivers Download Dell drivers Sierra Wireless Generic drivers

After downloading, unpack the driver by using 7Zip so you get the following files:

Dell driver:

Sierra Wireless driver:

For the Lenovo driver, it’s a little more complicated as 7Zip won’t recognize the file format to unpack it. To unpack it, first run the downloaded file:

Follow all the steps, including the path where you want the driver to be extracted. After extracting the drivers you will see the following dialog, make sure to untick “Install Sierra Wireless EM7455 Software now”:

After that, you will find the extracted driver at the location you specified:

Now, you need to run the extracted driver EXE file with USBCOMP=8 command line. For example:

Complete the driver installation, then wait for 20 minutes. The driver will install all corresponding files and change the USB composition, and COM ports will appear in your Device Manager. The EM7455 will restart several times during that process, do not reboot Windows before it’s finished. Just wait for 20 minutes after the driver is installed. It’s possible that the drivers will flash your EM7455 automatically with some newer software version during installation. Just allow it to do its work and DO NOT INTERRUPT the process. After the COM ports are enabled, you can uninstall the drivers, because they include a lot of unneeded bloatware, like some Windows services to change the firmware, etc. Well, the latter is up to you, I personally prefer not to have any extra program or service running in my laptop besides vanilla device drivers.

If you prefer to have just vanilla drivers, just run the extracted driver EXE file with EXTRACTDRIVERS=1 command line:

It will extract the drivers to some folder next to the driver EXE file:

Sierra Wireless EM7345 Firmware version 1612. Carrier IQ is gone?

2016-09-16T11:56:00+08:00

In one of my previous posts I’ve showed that Sierra Wireless EM7345 firmware contained spyware called Carrier IQ that made a lot of controversy when it was first discovered in some Android phones.

Recently updated driver package for EM7345 on Lenovo website contains the new firmware version FIH7160_V1.2_WW_01.1612.00. I’ve taken my time and checked it out.

The first thing I’ve noticed about this version of firmware is that it doesn’t contain Carrier IQ modules no more. For example, the previous firmware version FIH7160_V1.2_WW_01.1548.00 contained the following strings: metrics_client_ciq.lib. That means the Carrier IQ module was compiled into firmware.

Firmware version FIH7160_V1.2_WW_01.1612 does not include the module metrics_client_ciq.lib and the above strings. Also, the AT command AT+XCIQ doesn’t seem to work anymore, it returns an error if you try to use it:

There are, however, some strings still present in firmware FIH7160_V1.2_WW_01.1612 that mention “CIQ“:

What does that mean? Either Intel, or Sierra, or Lenovo have been taking measures and changing their firmware regarding Carrier IQ. They removed something for sure, they removed AT+XCIQ command and some Carrier IQ functionality, but we still can see traces of Carrier IQ in the firmware. Does that mean that Carrier IQ is not active anymore or it’s still there, changed, recompiled and operating more covertly than before?

Personally I’ve updated to firmware version FIH7160_V1.2_WW_01.1612 as I see less mentions about Carrier IQ in the firmware. Yes, there are still something left, but at least it’s less than before. Also firmware version FIH7160_V1.2_WW_01.1612 seems to be stable enough and I didn’t have any problem with it so far.

We can appreciate this nice move of removing Carrier IQ from the EM7345 device firmware, but it would be the best when they remove it completely and we see no single trace of Carrier IQ in any cellular broadband device.

Sierra Wireless EM7445: A dead-born king

2016-04-17T11:56:00+08:00

As a natural development of their previous XMM7160 LTE chipset, Intel presented a new generation, named XMM7260. It was announced about 2 years ago and only now some first real devices made it to customers. XMM7260 supports more LTE bands than XM7160 and also supports LTE carrier aggregation. It conforms to LTE Cat.6.

The following LTE bands supported: 1, 2, 3, 4, 5, 7, 8, 13, 17, 18, 19, 20, 25, 26, 29, 30, 38, 41.

Wow, that’s 18 LTE bands supported!

The following LTE bands supported with carrier aggregation: 1+5, 8, 18, 19, 26; 2+4, 5, 13, 17, 29; 3+5, 8, 19, 20, 26; 4+5, 13, 17, 29; 7+20; 4+4.

That technical details look very good and I was desperate to test the new Sierra Wireless EM7445. Below is my review.

I’m still using a previous generation Lenovo laptop, X240. It includes an m.2 slot for WWAN devices. All WWAN devices are currently using an USB interface, and none are using PCI-E, so only USB connectors are required to function in laptop’s m.2 slot. USB version in X240 and X250 is 2.0 only. And Sierra Wireless EM7445 supports USB 3.0 already, so even if the device is capable of receiving LTE data very fast, using carrier aggregation, there still can be a real bottleneck in data throughput, because the device will need to fallback to the older USB 2.0 protocol when coupled with a previous generation laptop, like X240 or X250.

Also every time I turn my laptop on or wake up it from sleep, I’m getting a Windows notification “This device can perform faster. Please connect it to a USB 3.0 port”.

While this notification is harmless and doesn’t affect the device workings, it’s pretty annoying to see it every time. X240 already includes USB 3.0 in the chipset and has two USB 3.0 external ports, so the question is why they used USB 2.0 for the m.2 slot connectivity?

Sierra Wireless EM7445 doesn’t have a driver package available on the Lenovo website or anywhere else. Supported laptops Lenovo P50 and Lenovo P70 don’t list EM7445 drivers for download on their corresponding pages. There is a reason for that and I will explain it below. For drivers, EM7345 drivers for previous generation laptops include EM7445 support, according to INF files:

So I used the latest driver package for EM7345 from Lenovo website and EM7445 was detected and recognized:

em7445-drivers-settings If you have Windows 8 and up, proceed to the driver installation from Lenovo website as well to have drivers for GNSS and COM ports, as those won’t be recognized by standard Windows 8/10 drivers.

The Vendor and Product ID for EM7445 is 1199 and A004 respectively.

Unfortunately, Sierra Wireless EM7445 is intended for the newest Lenovo laptops, such as P50 and P70, so older laptops don’t include EM7445 in their white list. If you just install EM7445, then turn it on, your laptop will abort booting with the following message: An unauthorized network card is detected:

To get over it, it is possible to change the Vendor and Product ID to those which are accepted by Lenovo BIOS. For X240 and X250, we will use the IDs from EM7345, which are 1199 and A001 respectively. So basically we just need to change the Product ID from A004 to A001 to make the laptop boot normally.

So remove EM7445 from the laptop, boot up Windows, put your laptop to sleep, then install EM7445 and connect the antennas. Then wake up the laptop.

Sierra Wireless EM7445 is using the same method of changing IDs, device/manufacturer name strings and also the device “composition” and enable COM and GNSS ports. To achieve that, we will use the following script for the Intel MBIM tool:

dtc
EXT USBPROFILE s USBPROFILE at@usbmwtestfw:usb_profile_set_nvm_configuration(USBPOW_ID_DEFAULT,"MBIM;3ACM","INTERFACES_NAME=L\"Sierra Wireless EM7445 4G LTE\"",0x1199,"530069006500720072006100200057006900720065006C00650073007300200049006E0063002E00",  0xA001,"530069006500720072006100200057006900720065006C00650073007300200045004D00370034003400350020003400470020004C0054004500")
EXT FWUSVC s MODEM_REBOOT
EXIT

You also can download and run the following file. After a couple of minutes, check the device in Device Manager. It will be shown there as Sierra Wireless EM7345 4G LTE, because we changed IDs to ones belonging to EM7345. But now we can successfully reboot the laptop and it won’t complain about an unauthorized device plugged in. To fix the incorrect device name in Device Manager we can use the following:

Open EM7345 device in Device Manager and select “Uninstall Device”. When uninstalling, also tick “Delete device software”. After that, press F5 to refresh the device list. Then open Unknown device, and press “Update driver” in the device properties in the Driver tab. Select “Browse my computer for driver software” and then “Let me pick from a list of device drivers on my computer” and then “Have Disk”. Press “Browse” and navigate to unpacked drivers files and open file “SWMBIM01_ss.INF”. Then untick “Show compatible hardware”. Then select “Sierra Wireless EM7445 4G LTE” from the list and press “Next”. Drivers for EM7345 and EM7445 are exactly the same, and you can omit this step completely, even if it shows as EM7345, it won’t affect the device functioning. What we doing here is just to have EM7445 with changed Product ID to be shown as EM7445 in Device Manager.

You can repeat the above procedure for COM and GNSS port devices: “Sierra Wireless EM7345 AT Port”, “Sierra Wireless EM7345 Trace Port”, “Sierra Wireless GNSS Sensor EM7345 4G LTE” and “Sierra Wireless EM7345”.

After drivers are installed, we can start using EM7445 for internet access and use COM port to control it. All commands are basically the same with some new ones. I haven’t been able to test carrier aggregation with EM7445, I also don’t know any of AT commands that might control carrier aggregation. My tests were brief and EM7445 was able to connect to a LTE carrier and Internet was working, that’s all what I can say. Carrier aggregation is not supported by carriers here, otherwise the device is working identically to the old EM7345, but the overall stability is worse, there are crashes, some AT commands not working, etc.

The firmware version is XMM7260_V2_REV_3.0_M2_BDREV_3_NAND_ROW_GNSSS and M27260_V2.3_WW_01.1530.102 dated July 22 2015:

I couldn’t find any newer firmware version for EM7445. The latest driver package from Lenovo website contains only firmware for EM7345, there is no firmware for EM7445. Also, the firmware is buggy. I have had several device crashes, device is crashing to “1 CDC” many times. Also it’s showing some crash logs with AT+XLOG=0 command:

The crash was in module “metrics_engine”. What metrics? Are we talking about Carrier IQ here? What other metrics can we think of? Not only device manufacturers haven’t removed Carrier IQ from the device firmware, they even made it worse so now it crashes when processing those spying “metrics” functions.

Also the device always hangs when I enter AT+CNUM command to display the phone number of the inserted SIM. Also it ALWAYS crashes to “1 CDC” when the reboot command AT+CFUN=16 is entered with crash logs saying it was another error in “metrics_engine” module.

And the last thing, the EM7445 module I’ve got is most likely an engineering sample for internal Lenovo testing. The IMEI number of my EM7445 device is: 01440500000XXXX. It doesn’t look as a genuine IMEI number, because it contains too many zeroes. Five zeroes in a row, I’ve never seen a genuine IMEI containing so much zeroes. For test and engineering sample devices, however, IMEI can contain zeroes and most engineering samples I’ve seen contained a lot of zeroes for the IMEI number.

FRU list for P70 dated October 29 2015 contained EM7445 as an WWAN option:

https://download.lenovo.com/parts/ThinkPad/p70_frubom_20151029.pdf

Let’s check the white list in P70 BIOS:

It doesn’t contain EM7445! The only allowed WWAN device for Lenovo P70 is EM7455 (1199/9079 and 1199/9078). The white list is the same for the oldest BIOS version 1.06 and the latest available version 1.40. We can say that despite the FRU document, the actual BIOS for Lenovo P70 never listed EM7445 as an allowed WWAN card!

I’ve also checked the Lenovo P50 white list for BIOS version 1.10 and 1.23:

It also contains only EM7455 in both BIOS version 1.10 and 1.23. No trace of EM7445 for Lenovo P50.

The only actual BIOS that contained EM7445 for a WWAN device is Lenovo Yoga 260. The first available BIOS version 1.06 contained EM7445 in the white list (1199/A004), but the latest BIOS version 1.40 DOESN’T INCLUDE IT ANYMORE, but includes EM7455 as the only allowed WWAN device (1199/9078). Below is the comparison of two BIOS white list:

For now, I haven’t been able to find any Lenovo device that is supposed to have Sierra Wireless EM7445 as the WWAN option! The only mention about EM7445 is in the FRU list for P70, but that’s a 100% outdated document.

So what happened at Lenovo so they changed their mind about EM7445? I guess they’re disappointed of the module performance, numerous bugs and problems using it in newer laptops. If we remember the story about EM7345, we can see that it was a big unsuccess for Lenovo and they surely don’t want to step into the same water again.

Intel WWAN XMM platform is pretty much dead and Lenovo effectively abandoned it. All new laptops will be using EM7455, which is based on QUALCOMM MDM9230 chipset that supports LTE Cat.6 carrier aggregation. And it is much more stable and already has firmware and drivers available for download on Sierra Wireless website. No doubt there will be new firmware versions released soon for EM7455.

EM7435 and EM7445 never had any drivers or documentation available on Sierra Wireless website, moreover, recently Sierra Wireless removed any mention about EM7445 from their website.

All EM7445 modules available for sale now are most likely engineering test samples intended for Lenovo internal testing and are not recommended to buy.

All Sierra Wireless EM7345 firmware

2015-09-27T11:56:00+08:00

This is the page with all Sierra Wireless EM7345 firmware released so far.

All firmware on this page is in FLZ format. To flash it, use Intel M.2 Firmware Updater Tool from the LATEST EM7345 driver package on Lenovo Support Site.

If you need to flash using Infineon Flash Tool E2 (i.e. for unbrick or emergency recovery), extract FLS file from the corresponding FLZ file. FLZ file is just a renamed ordinary ZIP file, so you can use whatever ZIP compatible software to extract it.

There is no changelog available for any EM7345 firmware version, we only have version numbers as reference, where higher versions usually mean more recent release date and more new features/less bugs.

Generic firmware (Worldwide)

These are generic worldwide versions. Can be flashed in any country and should work with any cellular carrier. These are the recommended versions, as they should contain less custom “improvements” introduced by carriers.

FIH7160_V1.1_01.1349.12_MBIM_GNSS_NAND_4.5_REL.flz

FIH7160_V1.2_WW_01.1415.07_NAND.flz

FIH7160_V1.2_WW_01.1415.09_NAND.flz

FIH7160_V1.2_WW_01.1442.07_NAND_Generic.flz

FIH7160_V1.2_WW_01.1522.02_NAND_Generic.flz

AT&T firmware (USA)

These are customized versions for AT&T carrier. Handle with care. These versions can be SIM locked to AT&T. I never tried to flash it into my unlocked generic EM7345.

FIH7160_V1.1_WW_01.1410.13_AT_NAND.flz

FIH7160_V1.1_WW_01.1446.03_AT_NAND.flz

Verizon firmware (USA)

These are customized versions for Verizon carrier. Handle with care. These versions can be SIM locked to Verizon. I never tried to flash it into my unlocked generic EM7345.

FIH7160_V1.2_WW_01.1442.04_VZ_NAND.flz

Telstra firmware (Australia)

These are customized versions for Telstra carrier. Handle with care. These versions can be SIM locked to Telstra. I never tried to flash it into my unlocked generic EM7345.

FIH7160_V1.2_WW_01.1426.16_TS.flz

FIH7160_V1.2_WW_01.1426.18_TS_NAND.flz

Orange firmware (Europe)

These are customized versions for Orange carrier. Applicable for Orange in UK, France, Luxembourg, Poland, Slovakia, etc. Handle with care. These versions can be SIM locked to Orange. I never tried to flash it into my unlocked generic EM7345.

FIH7160_V1.2_WW_01.1442.11_Orange.flz

Sierra Wireless EM7345: Who’s spying on us?

2015-09-25T11:56:00+08:00

Quite a long time ago, I found an interesting AT command for Sierra Wireless EM7345. The command is “AT+XCIQ”. There’s the following text string in EM7345 firmware file (it is present in any version so far): +XCIQ CIQ: Carrier IQ enable/disable.

Let’s try to get “help” about this command:

AT+XCIQ=?
+XCIQ: (0-1)
 
OK

So, we can suppose that 0 disables this Carrier IQ feature, and 1 enables it.

Let’s read the current setting of this feature:

AT+XCIQ?
+XCIQ: 1
 
OK

Looks like it’s on by default. Let’s try to switch it off?

If you’re running firmware earlier than 1522.02, don’t enter the following command!

If we try to enter:

AT+XCIQ=0

i.e try to disable Carrier IQ, EM7345 will have a fatal crash and reboot into boot flashing mode and it will be stuck there for good. Symptoms will be exactly as I described in my previous post, and you would need to unbrick it using the method I described in the same post: https://zukota.com/how-to-revive-your-bricked-sierra-wireless-em7345/

So, Carrier IQ is always on and if you try to turn it off using the above AT command, that will kill the device!

With firmware version 1522.02, AT+XCIQ=0 returns OK and there’s no fatal crash like in previous firmware versions. Also AT+XCIQ now accepts 3 possible values with 1522.02 firmware:

AT+XCIQ=?
+XCIQ: (0-2)

OK

So, 0 must be disable, 1 enable, and what is 2? Any value gets OK response and there’s no any error. Can Carrier IQ be really disabled or enabled using the above values? Who knows… If you don’t know what Carrier IQ is, fear and read:

Carrier IQ and Your Phone: Everything You Need to Know

Carrier IQ Tracking Scandal Spirals Out of Control

There’s not much in the news now, all seems quiet, but they definitely are looking for more stealthie ways to do their dirty business. At first, it used to be just an app in your Android phone, though using some stealth techniques, but still an ordinary app. You could block, patch, firewall, sniff, analyze it to any of your like.

But now, it is not in your phone, now it is sitting at the very firmware of your LTE device, it can analyze your internet traffic, extract your passwords and private data, do man in the middle attacks, report back home and whatever they want. Looking at the firmware dump file and the strings, one can say that there’s a complete TCP/IP stack implemeted and it is functioning on its own, independently from your OS and firewall.

And it’s perfectly undetectable, if, for example, they put someting like this in your Ethernet card or router, it can be detected on the next router where the traffic is going thru. But in our case, where are you gonna sniff packets generated by EM7345? That can be done only on a cellular carrier’s network equipment, and no one has access to that… except cellular carriers themselves.

If we take a look in a HEX editor at the EM7345 firmware file, version 1522 (and all previous versions as well) we can find the following:

We can see that firmware was compiled with “metrics_client_ciq.lib”, “metrics_engine.lib”, “metrics_client_em.lib” libraries. And I wonder what “metrics” are being sent to Carrier IQ from my Lenovo laptop? If you do just a trivial text search for “Carrier IQ” or “ciq” in the EM7345 firmware file, you will find a plenty of strings that speak of itself: we can definitely say that Carrier IQ functionalty is active and working in all EM7345 devices.

So who’s spying on us when we go online using an ultra-fast LTE network? Whose decision was it to embed this dreaded Carrier IQ into EM7345 firmware? The truth is out there. Use your brain and take care.

How to revive your bricked Sierra Wireless EM7345

2015-04-07T11:56:00+08:00

When playing with some EM7345 AT commands I was able to permanently bring the device down. Yes, THERE IS at least one AT command that can brick your EM7345 beyond repair! But not anymore, I found a way to revive a bricked EM7345 back to normal.

I’m going to publish some interesting information about that AT command in one of my following posts, as it’s really worth it, since it’s related to the infamous Carrier IQ scandal. Hey Intel, are you spying on us too?

But first things first, now I’m going to explain how to get your bricked EM7345 back to normal.

The method described in this post is only applicable to EM7345 devices installed in Lenovo laptops! Lenovo tablets have another hardware subtype of EM7345 and the firmwares for laptop and tablet are not mutually compatible! Don’t ever try to crossflash!

This method is only applicable for the symptoms described below. If your circumstances are different, don’t try this method!

Sometimes your EM7345 can die with the following symptoms:

The device “Sierra Wireless EM7345 4G LTE” is not shown in Device Manager.
AT COM ports and GNSS sensor device are not shown in Device Manager.
Instead, a new USB device, named “Intel(R) USB Flash Loader Utility” is shown in Device Manager.

The above device is constantly disappearing and reappearing again, and Device Manager is “refreshing” on its own every 2-3 seconds.
Intel Firmware Updater doesn’t recognize the device at all and you can’t flash it.
Rebooting, detaching the battery, removing the EM7345 from the laptop, enabling or disabling that Intel USB device.
in Device Manager doesn’t help. The device is not recognized by Windows, you cannot use it anymore.

Bricked for good, you say?. But, there’s a way now.

Download and unzip the following file: FlashTool

Go to the unzipped folder and run “FlashTool_E2.exe”.

Press “Add” button and find a correct firmware file for your EM7345. On the picture above, I’m using 1415.07 firmware, you can also use 1415.09 or any other firmware. The firmware must be in FLS format! You can find EM7345 FLS firmwares in the folder “c:\ProgramData\Intel\MBIM Toolkit\FirmwareDatabase\PreInstalled” if you have Lenovo drivers installed.

Set everything as shown on the picture. All ticks, baud rate, channels, communication driver, especially erase settings!

Then notice the VID and PID of that Intel USB device in Device Manager.

The VID is 8087 and PID is 0716 here.

Open Flash Tool E2 File-> USB Map Wizard:

Make sure USB Detection String has the same numerical IDs as your Intel Flash Loader USB device in Device Manager! Correct it if necessary, and press Next button. The next time Device Manager “refreshes” itself, the device will be shown in the list as Detected. Press Done button.

Now, you’re ready. Double check all the settings in the Flash Tool and press Next button. It will show the following window:

All you have to do now is just press “Start USB1” button. In a few seconds your Em7345 will be recognized, erased and then reflashed. After it’s done you should see a message that all went well and completed 100% without errors. Then you can check again in Device Manager and make sure that Intel USB Flash Loader Utility is shown steadily and is not disappearing like before. Device Manager should not also constantly “refresh” itself. If it’s so, just turn off your Lenovo laptop now and disconnect the power cord. The idea here is to power off EM7345 completely.

Next, power on the laptop again and your EM7345 should be back up and running as before. It will be shown in Device Manager, AT ports will be back, so will be the GNSS sensor.

Congrats, you just revived your bricked EM7345!

And sometimes, it’s necessary to reflash your newly restored EM7345 again, using Intel Firmware Updater this time. This is needed when you get odd connection errors or AT+XLOG showing lots of errors. Intel Firmware Updater accepts only FLZ files, not FLS, so make sure you do it accordingly. Refer to this post for instructions. After I reflashed my EM7345 the second time, I saw no more errors added to AT+XLOG error log.

Sierra Wireless EM7345 – an easier method to update firmware

2015-02-15T11:56:00+08:00

WARNING!!! The instructions in this post are applicable only to EM7345 installed in Lenovo laptops!! For example, models T440, X240, X1 Carbon 2nd and 3rd gen, X250. For tablets or other devices don’t use the firmware given in this post, you can brick your EM7345!

Finally, I was able to figure out what *.flz files actually are! EM7345 Intel firmware updater asks for *.flz files when you want to flash the firmware. But there were none available, only *.fls files, which Intel firmware updater doesn’t accept. If you have a flz file, you can flash your EM7345 without editing out xml files and rebooting your laptop. Just open a flz file in the updater and you’re good to go!

A flz file is just a zipped fls file together with an xml description file. For example, if you want to flash FIH7160_V1.2_WW_01.1415.09_NAND.fls firmware, just do the following:

Create FLSInformation.xml file with the following contents:

<?xml version="1.0" encoding="utf-8"?>
<FLSImageList>
	<FLSImage name="FIH7160_V1.2_WW_01.1415.09_NAND.fls">
		<MCC>260</MCC>
		<MNC>01</MNC>
	</FLSImage>
</FLSImageList>

Then zip these two files, FLSInformation.xml and FIH7160_V1.2_WW_01.1415.09_NAND.fls together. Rename the zip archive to FIH7160_V1.2_WW_01.1415.09_NAND.flz. Now you can launch Intel Firmware updater, click “Add firmware” and it will be recognized and showed in the list.

Then you can click “Update Firmware” and that’s it!

Note if you put different MCC and MNC values than your currently installed SIM card, you will get a warning from the updater saying that the firmware does not match your device. Ignore the warning if you know what you are doing and you really want to flash that version. Alternatively, use MCC and MNC values to match your SIM, and there will be no warning shown.

You may find this method of having a flz file a lot easier in order to update your EM7345 firmware, no need to edit xml files and reboot any more, and the updating process is now visual and straight forward. Enjoy.

Sierra Wireless EM7345 AT commands

2015-02-15T11:56:00+08:00

Sierra Wireless EM7345 AT commands

AT commands are very helpful for troubleshooting your device and changing the settings that are not available from standard Windows settings. For example, you can choose the access technology – 2G, 3G, 4G and even stick to particular frequency bands.

EM7345 is using Intel (formerly Infineon) AT command set and it’s not compatible with Quallcomm AT command set. All basic AT commands like AT+CFUN are more or less the same for all 3G/4G devices, but advanced ones, starting from AT+X, are unique to Intel XMM platform devices.

No official documentation for AT commands was released by Intel, all I was able to find is some source code fragments for Samsung phones (that are based on the earlier XMM platform, like XMM 6380, or so) on GitHub.

To use AT commands, first you have to enable EM7345 AT command port, as I described in this post.

There are many cases when your newly installed EM7345 doesn’t work. Let’s start step by step.

AT+CFUN?

should return: +CFUN: 1,0

1 means the device is turned on. If it’s not 1, make sure your EM7345 is turned on in Windows Connection Manager. Or try to turn it on using the AT command:

AT+CFUN=1

Let’s check if the SIM card is working and recognized by the EM7345:

AT+CIMI

should read from your card and display your IMSI number.

Check your SIM card status:

AT+CPIN?

should return: +CPIN: READY. That means your SIM card is properly recognized and no SIM card PIN is required to enter.

Let’s check if your EM7345 is SIM locked:

AT+CLCK=”PN”,2

should return +CLCK: 0

0 means your device is not locked and can work with any SIM card. If it is 1, then bad luck, your EM7345 is SIM locked and will work only with SIM card of the operator it is locked to.

Let’s check which access technology is currently used:

AT+XREG?

returns something like +XREG: 0,8,BAND_LTE_20,0

it means your device is currently using LTE, frequency band 20. For 3G, the band will be BAND_UMTS_I, for example. That means 3G band I. All actual band frequencies you can find in Google.

How to change the access technology?

AT+XACT=n

where n is: 0 – for 2G (EDGE), 1 – for 3G, 2 – for 4G/LTE.

You can also check your current access technology configuration:

AT+XACT?

response: +XACT: 0,0,,900,1800,1900,850,1,2,4,5,8,101,102,103,104,105,107,108,113,117,118,119,120

the first number is n number above. Then come numbers 900,1800,1900,850. Those are bands currently enabled for 2G technology. So the configuration is to use only 2G, and use the above bands. If the band is not listed, it won’t be used by the EM7345. This is very useful when you want to stick to only one access technology and even some particular band. Then we see numbers 1,2,4,5,8. Those are 3G bands. And finally, numbers starting from 101 and up to 120. Those are 4G/LTE bands. 101 means LTE band 1, 102 stands for LTE band 2 and so on.

How do we set the bands? For example to use only LTE band 20, use the following command:

AT+XACT=2,,,120

To stick to LTE bands 7 and 20, use:

AT+XACT=2,,,107,120

You get the idea.

What about automatic selection of access technologies? For example in some areas where 4G is not avaialble and you want the device to use 3G and then go back to 4G when you’re back to the coverage? Use this:

AT+XACT=6,2,1,900,1800,1900,850,1,2,4,5,8,101,102,103,104,105,107,108,113,117,118,119,120

That tells your device to use all access technologies and the bands listed in the command (6 number) with the priority of 4G/LTE. This is the default factory EM7345 setting. What 2 and 1 numbers mean I don’t know yet.

If your SIM card seems to be ok, but you cannot get a working connection, try to check for connection errors:

AT+XEER

AT+CEER

AT+NEER

Each of it will get you some text error report if your EM7345 cannot connect to a network.

Your device is frozen or you get “1 CDC error”? No need to reboot your laptop, just use:

AT+CFUN=16

This will reboot your EM7345, and it will reappear in Device Manager shortly.

Want to check your EM7345 for internal errors? Use:

AT+XLOG=0

This will list all recorded errors (exceptions). Firmware version 1.1 had some bugs, and every time “1 CDC” error appeared, it got logged and appeared in this list. Since version 1.2 (1415.09) I see no errors in this log.

To clear this list of errors, use:

AT+XLOG=2

New Sierra Wireless EM7345 firmwares available

2015-02-01T11:56:00+08:00

Yesterday I’ve been checking on Lenovo drivers website and have noticed that they added the X250 model. And what did I find there? Sierra Wireless EM7345 Software for Windows 8.1 (32-bit, 64-bit) – ThinkPad version 1.11.10610.4225, released on 12/16/2014 . So Lenovo doesn’t update WWAN drivers for their “old” models, like X240 or T440 and the latest drivers out there are dated July 31. So I downloaded it, unpacked it and found the following EM7345 firmwares inside:

FIH7160_V1.1_WW_01.1410.13_AT_NAND.fls version 1.1 (1410.13) for AT&T (United States only) dated 2014-May-19 12:32:21
FIH7160_V1.2_WW_01.1415.07_NAND.fls version 1.2 (1415.07) Worldwide dated 2014-Jun-5 11:54:58. This is the version I had flashed into my EM7345, as described in this post
FIH7160_V1.2_WW_01.1415.09_NAND.fls version 1.2 (1415.09) Worldwide dated 2014-Oct-22 17:47:10. Seems to be an update for 1415.07.
FIH7160_V1.2_WW_01.1442.04_VZ_NAND.fls version 1.2 (1442.04) for Verizon (United States only) dated 2014-Nov-20 11:23:44.

Of course I couldn’t resist and flashed the new firmware FIH7160_V1.2_WW_01.1415.09. Everything seems to work fine.

I didn’t dare to flash Verizon or AT&T version, even though Verizon seems to be the latest, compiled on 2014-Nov-20. US operators love to SIM lock their devices, and those firmwares can be locked. Unless you are in the US and your network is Verizon/AT&T or you just don’t care, I cannot recommend to flash those AT&T and Verizon firmwares.

How to flash it? Just put file FIH7160_V1.2_WW_01.1415.09_NAND.fls into the folder c:\ProgramData\Intel\MBIM Toolkit\FirmwareDatabase\PreInstalled (first you have to have the EM7345 drivers installed as desrcibed in this guide ) and make changes to file c:\ProgramData\Intel\MBIM Toolkit\FirmwareDatabase\PreInstalled\FLSInformation.xml. But this time use FIH7160_V1.2_WW_01.1415.09_NAND.fls instead of FIH7160_V1.2_WW_01.1415.07_NAND.fls when editing the xml and you’re done.

After reboot, you will be prompted by the Intel firmware updater:

Press Yes and you’re set! Interestingly, VID/PID weren’t reset to their default values so I had no need to restore them. Also GNSS and AT ports were not affected at all, and continued to work just fine.

I’d like to know what new features and bug fixes are brought by the updates, but (as usual) we have no information, no change logs… I’m not using my EM7345 much these days, but if you guys notice something new in this update, feel free to let me know.

Sierra Wireless EM7345: How to flash the latest firmware

2015-01-13T11:56:00+08:00

WARNING!!! The instructions in this post are applicable only to EM7345 installed in Lenovo laptops!! For example, models T440, X240, X1 Carbon 2nd and 3rd gen, X250. For tablets or other devices don’t use the firmware given in this post, you can brick your EM7345!

Unfortunately, the default factory EM7345 firmware version (1.1) has some bugs. For example, after connecting to a LTE network and then disconnecting manually, the network status of the connection was changing for me to “No service” until device restart. Also, the device often disappears from Device Manager and reappears there with the name “1 CDC” and does not work until you disable and then enable it again in Device Manager. All those issues are caused by some bugs in EM7345 firmware.

But there is a newer version of firmware, namely 1.2, where the above bugs are fixed. But by default, you cannot flash it, because firmware updating is supposed to work unattended. And this is not nice of Intel and Lenovo. The users must be able to do firmware updating when they need or want it!

Make sure you’re using Windows 8 or 8.1

Go to the control panel and uninstall Sierra Wireless EM734x 4G LTE Software from Program and Features.

Reboot your laptop.

Download and install the latest EM7345 driver package from the Lenovo website. https://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t440/downloads/DS040771. This package already includes the 1.2 firmware, but by default it’s never going to be flashed into your EM7345, unless you live in some specific country.

Find the file c:\ProgramData\Intel\MBIM Toolkit\config\Config.xml and open it in any text editor. Find the following string in the file: true and change true to false. Also check that the string true is set to true and set it to true if it’s not.

Make sure after you edit the file contents is the following:

<?xml version="1.0" encoding="UTF-8"?>
<Config>
	<EmailTo>
	</EmailTo>
	<EmailSubject>
	</EmailSubject>
	<!-- Location of where the trace file will be stored -->
	<TraceDir>%USERLOCALDATA\temp\TraceApp</TraceDir>
	<!-- Trace level can be any number between 1 - 9 -->
	<TraceLevel>1</TraceLevel>
	<!-- EnableTracelevel true = show trace level in GUI. Works only in Windows 8, not in
     Windows 7 -->
	<EnableTraceLevel>false</EnableTraceLevel>
	<!-- Location of where the firmware database is located. -->
	<CustomFirmwareDatabase></CustomFirmwareDatabase>
	<!-- 0 - turn off Application logging. 1 - turn on  Application logging -->
	<AppLogging>1</AppLogging>
	<!-- Max size for debug logger file -->
	<AppLogSize>4096000</AppLogSize>
	<!-- Resource file with translated string table -->
	<ResourceFile>Resource_en-us.xml</ResourceFile>
	<!-- Silent Auto Firmware Update -->
	<SilentAutoFWUpdate>false</SilentAutoFWUpdate>
	<!-- Prompt Silent Auto Firmware Update failures, this configuration is only applicable if 'SilentAutoFWUpdate' is true -->
	<PromptForSilentAutoFwUpdateFail>true</PromptForSilentAutoFwUpdateFail>
	<!-- Enable Firmware System Tray. Default is true to enable -->
	<FirmwareSysTray>true</FirmwareSysTray>
</Config>

Now, reboot your laptop.

After reboot, you will notice a new icon in the system tray for Intel firmware updater service:

Don’t proceed if you don’t see this icon.

Double click the icon to bring up the Intel firmware updater utility:

Notice the highlighted area. You should see your country and cellular operator listed there. Also check “Home Provider ID” value. It should contain a 5-digit code, for example “26299”. If you don’t see any data shown, make sure your SIM card is inserted and you can see your cellular provider name in Windows 8 Connections Manager.

Don’t proceed if you don’t see Home Provider ID, your county and your operator name!

Now, find and open in a text editor the following file: c:\ProgramData\Intel\MBIM Toolkit\FirmwareDatabase\PreInstalled\FLSInformation.xml. Scroll to the very end of it and before string insert the following text:

	<FLSImage name="FIH7160_V1.2_WW_01.1415.07_NAND.fls">
		<MCC>262</MCC>
		<MNC>99</MNC>
	</FLSImage>

where MCC is the first 3 digits of the code shown in “Home Provider ID”. If your code is 26299, then MCC must be 262. MNC is the last 2 digits of the code, if your code is 26299, then your MNC must be 99.

Make sure the end of the file with your added data looks like this:

	<FLSImage name="FIH7160_V1.2_WW_01.1415.07_NAND.fls">
		<MCC>262</MCC>
		<MNC>99</MNC>
	</FLSImage>	
</FLSImageList>

Save the file and reboot your laptop.

After reboot, wait for some time until you get a prompt from Intel firmware updater to update your firmware. Press “Yes” and the firmware update progress will begin!

It should complete in a few seconds, maybe 10-20. After the process is done and the updater says so, wait for a couple of minutes. Don’t reboot your laptop.

After the updating is done, your EM7345 can appear in Device Manager with a different name, and AT and GNSS ports can be gone, and VID/PID can be reset again to bad values. You will need to reinitialize your EM7345 again, as described in this post. If you want to also get back your AT and GNSS ports, refer to this post.

If you have AT ports enabled, check the version of firmware:

AT+XGENDATA
+XGENDATA: "    FIH7160_XMM7160_V1.2_MBIM_GNSS_NAND_REV_4.5 2014-Jun-5 11:54:58
                                                                               FIH7160_V1.2_WW_01.1415.07*"
 
"*"
 
OK

The version should read as 1.2 now. If so, you have successfully updated your EM7345 to the latest available firmware. I personally noticed that “1 CDC” bug is gone, and LTE connecting and reconnecting works fine now. I also can observe a very rare bug when my EM7345 is shown with an exclamation mark in Device Manager after the laptop wakes up from sleep, but I use to fix that by disabling it in Device Manager and enabling it again. Other than that, there are no bugs and LTE works like a charm 🙂

How to enable AT command and diagnostic ports and GPS for Sierra Wireless EM7345

2014-12-28T11:56:00+08:00

Sometimes it’s useful to know what’s going on under the hood. Almost all modern 3G and 4G modules offer an AT command interface to run AT commands.

What can you do using AT commands? To name just a few:

Check the cellular signal strength.
Lock your EM7345 to use only 2G, 3G, or 4G if you have such a need.
Check for some problems, for example if your newly bought EM7345 is SIM-locked to some provider.
Reboot your EM7345 without rebooting Windows.
Check what’s wrong if your EM7345 doesn’t connect to a cellular network.

Also, the EM7345 includes a fully functional GPS device! With active antennas connected inside your Lenovo laptop!

Unfortunately, out-of-the-box EM7345 comes with only MBIM interface enabled, all AT ports are switched off by default. GPS is also switched off and there are no standard means to enable it! Shame on you Lenovo! Why you restrict us, buyers of your laptops, to use all features and potential of hardware we bought from you? Do you think GPS is not important?

But OK, this is where we come in! To enable AT command port and GPS on your EM7345, do the following:

Ensure you’re running Windows 8 or Windows 8.1. Windows 7 can use AT and GPS too, but to enable it, you must be running Windows 8!
Ensure you have the latest EM7345 drivers installed from Lenovo website.
Ensure your EM7345 is visible in Device Manager with the correct VID/PID identificators:

When the above requirements are met, download and run this file: EM7345_MBIM_ACM

Wait for a minute and then check your Device Manager again. You will notice three new devices:

Sierra Wireless EM7345 AT Port
Sierra Wireless EM7345 Trace Port
Sierra Wireless GNSS Sensor EM7345 4G LTE

Congratulations! Now you have fully enabled GPS in your Lenovo laptop ready to work with built-in Windows 8 Maps, also you can make it work with any NMEA-compatible GPS software for Windows. Also you have your AT command ports enabled. Download putty and open your corresponding COM port in putty. In this picture example, my COM port number is COM7:

And press “Open”.

In the opened window, type:

AT+XGENDATA and press ENTER

You should have a reply from your EM7345:

+XGENDATA: "    FIH7160_XMM7160_V1.2_MBIM_GNSS_NAND_REV_4.5 2014-Jun-5 11:54:58
*FIH7160_V1.2_WW_01.1415.07*"
 
"*"
 
OK

Congratulations! Your AT port is now working and you can query your EM7345 with AT commands. The above command asks for a device firmware version, it is FIH7160_XMM7160_V1.2_MBIM_GNSS_NAND_REV_4.5 2014-Jun-5 11:54:58 in my case, the latest one.

You can do a lot more things with your EM7345 using AT commands, and in my next posts I will give some more very useful examples.

Sierra Wireless EM7345 initial setup

2014-11-20T11:56:00+08:00

Recently I bought this all-band LTE 4G card for my Lenovo X240 laptop. Unfortunately, Lenovo X240 BIOS contains a whitelist of allowed 4G devices, and EM7345 is the only solution officially available for the European LTE bands.

Device specifications:

Chipset: Intel XMM7160
LTE bands: B1, B2, B3, B4, B5, B7, B8, B13, B17, B18, B19, B20 (12 bands total). This is awesome as the device is really ready to work world-wide.
Form factor: m.2
Platform: Intel X-Gold, Software is based on ThreadX RTOS.

Nothing much is known about this Intel XMM7160 chipset. Actually, Intel bought Infineon some time ago and this device appears to be very similar to Infineon models. AT command set is not compatible with Quallcomm and everything is organized differently. In this post, I’m going to explain how to get this device working on Windows and how to do the initial setup.

First, If you bought EM7345 from China, like I did, you may find that once you installed it in some Lenovo laptop, the system refuses to boot!

But why is this happening? Isn’t the EM7345 an officially certified device for Lenovo X240, Lenovo T440, etc? Yes and no. Just check the Vendor and Device ID if you see this screen when you turn your laptop on. Chances are it reads (8087/0911). In this case, like I did, you received your device directly from Chinese factory and it’s not initialized with correct ID yet. What can you do to boot up successfully:

EM7345 is an USB device and it is slow to initialize when turned on. You can switch off the power of your laptop then quickly turn it on again.
Some people reported after they flashed a new or old BIOS, the system allowed them to boot successfuly. Try that.
You can use some other laptop with a m.2 slot to “initialize” your EM7345. Once it is initialized, you can put it back in your Lenovo laptop and it will boot up just fine without this dreaded screen.
If you have no other laptop, you can insert EM7345 into your Lenovo after you booted into Windows. Since it is an USB device, no harm should be done with hot plugging it. But be very careful doing that! I never tried this myself and can’t recommend this method!

Now you are booted into Windows 8. Yes, the device can be initialized and its Vendor and Device IDs changed in Windows 8 only. Windows 7 won’t work since it has no drivers allowing you to change the ids. Again, you only need Windows 8 or 8.1 !

Open your device manager and find your EM7345 there. It should be listed there with a name similar to “CDC” or something like that. Also possible names include “Microsoft Mobile Broadband device”. Open that device properties and make sure the device id strings are 8087/0911. Click “Details” tab and select “Hardwsre Ids”. The string should look like or begin with: PCI\VEN_8087&DEV_0911.

Now you can download and install the drivers for EM7345 from the Lenovo website.

https://support.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x240/downloads/ds040771

After you’re done installing, it’s time to initialize the device so it’s accepted by Lenovo BIOS.

Download and run the following file: EM7345_MBIM_only. Allow it to do its work and wait for 10-15 seconds.

After that, go back to the Device Manager. Your 4G card should now look like this:

Note that the device name has changed to Sierra Wireless EM7345 4G LTE and vendor and device ids are now 1199 and A001, respectively. Now you can reboot your Lenovo laptop or you can put your EM7345 back into your Lenovo (if you were doing the above procedure on a different laptop) and the BIOS will never complain again while booting!

If you like Windows 7, you can start using it from now on, since the device has the correct Vendor and Device ID. Just use the above drivers from Lenovo for your EM7345.

In my next post I will show you how to enable GPS and AT diagnostic port on your EM7345. AT port is a convenient way of receiving some technical info about your EM7345 and also operating it. You can lock your device into using only 2G, 3G or 4G and do some other useful things.