Unfortunately, my time is very limited at the moment. So I am not able to do a step by step guidance.
But you showed that you are able to use the command line and the important tools, so it might not be as hard as you think.
For an introduction, be sure to read the blog entry (linked on the USB_ModeSwitch page - see "Contribute") about the "Alltel" sniffing. There is also a link to the only Windows tool you need: USBSnoop.
You probably have to run this tool with admin rights too, depending on your setup. First, just try to start it up.
But you showed that you are able to use the command line and the important tools, so it might not be as hard as you think.
For an introduction, be sure to read the blog entry (linked on the USB_ModeSwitch page - see "Contribute") about the "Alltel" sniffing. There is also a link to the only Windows tool you need: USBSnoop.
You probably have to run this tool with admin rights too, depending on your setup. First, just try to start it up.
Hmm, not quite. You still need to install the filter.khurtsiya wrote:Done
VID = vendor ID, PID = product ID
The filter will be inserted between your device and the driver. As soon as you replug your stick it writes down all communication into a log file. After switching the log should not grow anymore because the original setup (including the PID) is replaced by the modem setup. Then you are done.
Please do not post the whole log here if possible; better use some file sharing or "pastebin.com".
You got it a bit wrong again. You sniff only on the default device which has VID 0x19d2 and PID 0xfff5. This is the device Windows sees first when you plug in. Then the driver attaches to it and some time later sends the switching command - to this very device, because at first there is no other.
It vanishes shortly after ("not present" anymore), so in order to see it you need to list all devices that were ever recognized by your Windows installation, even when they are at the moment "not present".
If you do that with the device already unplugged, there should be no problem. Install the filter, "Start Logging" and plug it back in.
Don't bother to sniff the "ZTE" devices.
It vanishes shortly after ("not present" anymore), so in order to see it you need to list all devices that were ever recognized by your Windows installation, even when they are at the moment "not present".
If you do that with the device already unplugged, there should be no problem. Install the filter, "Start Logging" and plug it back in.
Don't bother to sniff the "ZTE" devices.
1. Unplug modem
2. Check "List Devices Not Present"
3. Look in the list for your default vendor/product ID (Vid 19d2, Pid fff5), select it and press "Install" at "Filter Control"
4. Plug in modem
5. Press "Refresh" several times, see if "Log size" grows; if it doesn't grow anymore, "Uninstall all". Ready.
2. Check "List Devices Not Present"
3. Look in the list for your default vendor/product ID (Vid 19d2, Pid fff5), select it and press "Install" at "Filter Control"
4. Plug in modem
5. Press "Refresh" several times, see if "Log size" grows; if it doesn't grow anymore, "Uninstall all". Ready.
Very cool
Now we test some of the commands in the log with your device.
I suggest you create a small config file in your working directory, edit it with your favourite editor and let USB_ModeSwitch work with it. In my opinition this is easier than changing the command line all the time.
Suppose this little file is named "test.config". Then you can put your values into it (like in the big "usb_modeswitch.config" but only for your device). You would then call:
Of course you can do it all with parameters like you did before.
You certainly know how to work with the command line history (arrow up) to remember previously typed commands.
Try first these values (or file content for "test.config"): You can leave out the MessageEndpoint, it will be determined automatically.
Remember to call not only "lsusb" but "dmesg" too after each test, it will show what the system is doing if the device switched (or not).
Your log shows a long interval from sending the commands to the vanishing of the device (129 ms to 2299 ms) which is unusual. You might have to wait a little before you see any effect of your commands.
Now we test some of the commands in the log with your device.
I suggest you create a small config file in your working directory, edit it with your favourite editor and let USB_ModeSwitch work with it. In my opinition this is easier than changing the command line all the time.
Suppose this little file is named "test.config". Then you can put your values into it (like in the big "usb_modeswitch.config" but only for your device). You would then call:
Code: Select all
usb_modeswitch -c test.config
You certainly know how to work with the command line history (arrow up) to remember previously typed commands.
Try first these values (or file content for "test.config"):
Code: Select all
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= 0xffff
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
Remember to call not only "lsusb" but "dmesg" too after each test, it will show what the system is doing if the device switched (or not).
Your log shows a long interval from sending the commands to the vanishing of the device (129 ms to 2299 ms) which is unusual. You might have to wait a little before you see any effect of your commands.
I don't know if it failed. What I see is that your device already switched before!
See the line "Bus 005 Device 002: ID 19d2:ffff" from lsusb.
This is your target ID (0xffff). No more 0xfff5. That's why USB_ModeSwitch found 1 target device and no default device. In that case it does not do anything.
Did you plug it in freshly?
See the line "Bus 005 Device 002: ID 19d2:ffff" from lsusb.
This is your target ID (0xffff). No more 0xfff5. That's why USB_ModeSwitch found 1 target device and no default device. In that case it does not do anything.
Did you plug it in freshly?