IQecg, IQspiro Drivers. Windows 7, 8, 8.1 and 10; IQholter® Security Key Drivers. USB/Parallel Driver; IQvitals® Drivers. Please note that IQvitals PC is no longer supported. USB Driver; Midmark 625 Barrier-Free® Examination Table Drivers. Scale Driver; USB to Serial Adapter Drivers (Diagnostic) ATEN USB to Serial Port Adapter; Edgeport USB. To update your Surface with the latest drivers and firmware from the Download Center, select the.msi file name that matches your Surface model and version of Windows. For example, to update a Surface Book 2 with build 15063 of Windows 10, choose SurfaceBook2Win100092.msi.
- Virtual COM Port Driver is an advanced way to add virtual COM port pairs. There are many instances where this Windows 10 COM Port Driver software can be instrumental when working with serial devices and applications. Some of the uses of the software include testing and debugging in usage scenarios that include.
- Data Lifeguard Diagnostic for Windows. Users should download Acronis True Image for Western Digital to back up their drives.) WD Drive Utilities for Windows.
If you’re looking for a ways on how to enter DIAG Mode and restore / backup IMEI on Xiaomi smartphone here’s a complete guide. Below you’ll find few working methods on how to boot your device in DIAG mode and backup IMEI with Qualcomm Product Support Tools.
Entering DIAG Mode and backup IMEI using QPST on Xiaomi device
Methods on how to enter DIAG Mode on Xiaomi phone
There are three methods on how to enter DIAG Mode. Below, we will look at each method:
First method:Turn off your device > Hold “Volume +” button and turn on. In “Device Manager” your phone should be identified as “Qualcomm HS-USB Modem 9091” or similar.
Second method: Using ADB mode. Connect turned on device to PC via USB-cable and enter these commands (make sure you’ve installed all required drivers). You can also type these commands in device terminal.
In “Device Manager” your phone should be identified as “Qualcomm USB Composite Device 901D” or similar.
Third method: Enter service code *#*#13491#*#* and select required connection.
How to backup IMEI using Qualcomm Product Support Tools
- Download and install QPST.
- Boot your phone in diagnostic mode (find instructions on how to boot in DIAG mode above) and connect to your PC. Download and install Qualcomm Diagnostic Drivers if required, so that your device could be identified in COM ports as “Qualcomm Diagnostic 9091”.
- Start QPST Configuration (Note! Right click and “Run as administrator).
- In “Ports” tab add COM port with the port number that is shown in “Device Manager” as “Qualcomm Diagnostic”. It could be already identified and added automatically, in this case you don’t need to add anything.
- In the top menu select “Start Clients” and select “Software Download”.
- In the opened QPST Software Download window select “Backup” tab and select name and place to save .xqcn file.
- Press “Start” and wait until backup is completed.
- To restore your IMEI backup select “Restore” tab and select your saved .xqcn file.
Important information. In the latest QPST version (including this one) IMEIbackup is saved in .xqcn format. The thing is that this format does not suitable for changing or replacing IMEI code, changing MAC address or Bluetooth. The solution is very simple: use QCNView tool (comes with QPST) to convert .xqcn into .qcn. Just open .xqcn file with QCNView and select “File” > “Save as” > .qcn-->
This topic describes the USB hardware verifier tool (USB3HWVerifierAnalyzer.exe) that is used for testing and debugging specific hardware events.
Most hardware issues manifest in ways that lead to poor end-user experience and it's often difficult to determine the exact failure. The USB hardware verifier aims at capturing hardware failures that occur in a device, port, hub, controller, or a combination of them.
The USB hardware verifier can perform these tasks:
- Capture hardware events and display information in real time.
- Generate a trace file with information about all events.
- Parse an existing trace file for event information.
This topic contains the following sections:
Getting the USB hardware verifier analyzer tool
The USB hardware verifier tool is included with the MUTT software package that is available for download at Tools in the MUTT software package.
The tools package contains several tools that perform stress and transfer tests (including power transitions) and SuperSpeed tests. The package also has a Readme document (available as a separate download). The document gives you a brief overview of the types of MUTT hardware. It provides step-by-step guidance about various tests you should run, and suggests topologies for controller, hub, device, and BIOS/UEFI testing.
How to capture events by using a USB hardware verifier
To capture events by using the hardware verifier, perform these steps:
Start a session by running this command at an elevated command prompt.
The tool supports these options:
Logs all hardware verifier events for the specified VendorID.
Logs all hardware verifier events for the specified ProductID.
-f <ETL file>
Parses the specified ETL file. Real-time parsing is not supported. With this option, the tool parses the file offline.
Displays all events to the console.
Run the test scenario for which you want to capture hardware events.
During a session, USB hardware verifier captures information about hardware events as they occur. If you want to filter events for a particular hardware, specify the VendorId and ProductId of the hardware. The tool might not capture some information (such as VID/PID) about events that occur before the device gets fully enumerated. The missing information is available in the detailed report that is generated at the end of the session (discussed next).
Here is an example output from the hardware verifier tool:
Stop the session by pressing CTRL+C.
At the end of the session, a file named AllEvents.etl is added in the current directory. This file contains trace information about all events that were captured during the session.
In addition to AllEvents.etl, the command window shows a report. The report includes certain information that was missed in the real-time output. The following output shows an example test report for the preceding session. The report shows all events that the USB hardware verifier encountered.
In the preceding example report, note the Key field value for each record. The report categorizes the information by those Key values, making it easier to read. The same Key values are used in events captured in AllEvents.etl.
Convert AllEvents.etl to text format by running the following command:
In the output file, search for the previously noted Key values. The values are associated with one of these fields: fid_UcxController, fid_HubDevice, and fid_UsbDevice.
Open AllEvents.etl in Netmon and select Add <field_name> to display filter to filter events by controller, hub, and device.
USB hardware verifier flags
Device Diagnostic Tool
|Flag||Indicates that ...|
|DeviceHwVerifierClientInitiatedResetPipe||The client driver initiated a recovery action by resetting a particular pipe in response to I/O failures. Certain client drivers might perform error recovery in other scenarios.|
|DeviceHwVerifierClientInitiatedResetPort||The client driver initiated a recovery action by resetting the device in response to I/O failures. Certain client drivers might perform error recovery in other scenarios.|
|DeviceHwVerifierClientInitiatedCyclePort||The client driver initiated a recovery action by cycling the port. This flag causes the Plug and Play Manager to re-enumerate the device.|
|DeviceHwVerifierSetIsochDelayFailure||A USB 3.0 device failed the SET_ISOCH_DELAY request. The device can fail the request because either the driver does not require the request information or a transient error occurred. However, the driver cannot differentiate between those reasons. This error is not captured in the report.|
|DeviceHwVerifierSetSelFailure||A USB 3.0 device failed the SET_SEL request. The device uses the request information for Link Power Management (LPM). The device can fail the request because either the driver does not require the request information or a transient error occurred. However, the driver cannot differentiate between those reasons. This error is not captured in the report.|
|DeviceHwVerifierSerialNumberMismatchOnRenumeration||The device reported a different serial number during re-enumeration as opposed to the one it reported during initial enumeration. A re-enumeration can occur as a result of a reset port or system resume operation.|
|DeviceHwVerifierSuperSpeedDeviceWorkingAtLowerSpeed||The USB 3.0 device is operating a bus speed lower than SuperSpeed.|
|DeviceHwVerifierControlTransferFailure||A control transfer failed to the device's default endpoint failed. The transfer can fail as a result of device or controller error. The hub logs indicate the USBD status code for the transfer failure. This flag excludes SET_SEL and SET_ISOCH_DELAY control transfers failures. Those types of requests are covered by DeviceHwVerifierSetIsochDelayFailure and DeviceHwVerifierSetSelFailure flags.|
|DeviceHwVerifierDescriptorValidationFailure||A descriptor returned by the device does not conform to the USB specification. The hub log indicates the exact error.|
|DeviceHwVerifierInterfaceWakeCapabilityMismatch||The RemoteWake bit is incorrectly set in the device. USB 3.0 devices that support remote wake must also support function wake. There are two ways in which the device indicates its support for function wake. The first way is through the bmAttributes field of the configuration descriptor and the second way is in its response to the GET_STATUS request targeted to the interface. For a non-composite device, the RemoteWake bit value must match the value returned by the GET_STATUS request that is targeted to interface 0. For composite devices, the RemoteWake bit must be 1 for at least one of the functions. Otherwise, this flag indicates that the device reported contradictory values in here.|
|DeviceHwVerifierBusRenumeration||The device is re-enumerated on the bus. A re-enumeration can occur as a result of a reset port or system resume operation. Re-enumeration also occurs, when the device is disabled/enabled or stopped/started.|
|HubHwVerifierTooManyResets||A hub has gone through too many reset operations within a short period. Even though those resets were successful, the hub is not processing requests and repeated errors occur.|
|HubHwVerifierControlTransferFailure||A control transfer targeted to the hub's default endpoint failed. The transfer can fail as a result of device or controller error. The hub logs indicate the USBD status code for the failure.|
|HubHwVerifierInterruptTransferFailure||A data transfer targeted to the hub's interrupt endpoint failed. The transfer can fail as a result of device or controller error. The hub logs indicate the USBD status code for the failure. If the transfer failed because of the request was canceled, the failure is not captured.|
|HubHwVerifierNoSelectiveSuspendSupport||The RemoteWake bit is not set to 1 in the hub's configuration descriptor.|
|HubHwVerifierPortResetTimeout||While enumerating or re-enumerating a device, the port-reset operation is timing out. A port change notification is not received indicating that the port-reset is complete.|
|HubHwVerifierInvalidPortStatus||The port status of the target port is not valid as per the USB specification. Certain devices can cause the hub to report the invalid status.|
|HubHwVerifierPortLinkStateSSInactive||The link between the target port and the downstream device is in an error state.|
|HubHwVerifierPortLinkStateCompliance||The link between the target port and the downstream device is in compliance mode. In some scenarios involving system sleep-resume, the compliance mode error is expected and in those cases the failure is not captured.|
|HubHwVerifierPortDeviceDisconnected||The downstream device on the target port is no longer connected to the bus.|
|HubHwVerifierPortOverCurrent||The downstream port reported overcurrent state.|
|HubHwVerifierControllerOperationFailure||A controller operation (such as enabling device, configuring endpoints) failed for the device that is attached to the target port. Failures from SET_ADDRESS and Reset endpoint requests are not captured.|