[hatzfeld]

I just got an UMTS Stick from t-mobile (with an additional SD slot). Before switching it is accessible as a CDROM drive with VID=0x19d2 and PID=0x2000.

After switching the PID changes to 0x0031; according to a Windows installation it has 4 subdevices, MI=00 is a serial diagnostic device, MI=01 is a serial NMEA device, MI=02 is USB storage (probably the SD slot?), MI=03 is a ZTE modem. A text on the stick states that it is a "HSUPA USB MODEM MF637" supplied by ZTE.

usb_modeswitch works with the same parameters as ZTE MF628+:

Code: Select all

DefaultVendor=  0x19d2
DefaultProduct= 0x2000

TargetVendor=   0x19d2
TargetProduct=  0x0031

MessageEndpoint=0x01
MessageContent="55534243123456782000000080000c85010101180101010101000000000000"

Output of usb_modeswitch is:

Code: Select all

 * usb_modeswitch: tool for controlling "flip flop" mode USB devices
 * Version 0.9.5 (C) Josua Dietze 2008
 * Works with libusb 0.1.12 and probably other versions

Looking for target devices
 No target device found
Looking for default devices
 Found default devices (1)
Prepare switching, accessing latest device
Looking for active default driver to detach it
 No driver found. Device probably not initialized. Trying to continue ...
Setting up communication with device
Trying to send the message
 OK, message successfully sent.
-> See /proc/bus/usb/devices (or call lsusb) for changes. Bye

Now some useful informations for those who actually want to use that stick :

I installed it under opensuse 11.1. For usb_modeswitch and umtsmon (both to be run as root) I simply installed the packages from the suse repo oss. After deleting the comment signs in the section of MF628+ in /etc/usb_modeswitch.conf (as cited above), usb_modeswitch works and make three GSM modem device files /dev/ttyUSB[0..2] appear (and a generic scsi device).

After some experiments I discovered that umtsmon fails guessing the modem devices. In my case it works when started as

Code: Select all

umtsmon -s/dev/ttyUSB1,/dev/ttyUSB2

or (for debugging purposes)

Code: Select all

umtsmon -s/dev/ttyUSB1,/dev/ttyUSB2 -v4

Note: It worked also when I at first used ttyUSB2 in place of ttyUSB1, but the connection was extremely slow.

For using it with t-mobile (Germany) I hat to create a profile in umtsmon with APN="internet.t-mobile", username="t-mobile" and password="tm" (probably username and t-mobile may be any string, but not empty).

[Josh]

Thanks for the information!

Could you probably add the ID strings that version 1.0.2 prints out?

You don't need to install it, just unpack it and run (with the unswitched device present):

./usb_modeswitch -v 0x19d2 -p 0x2000

This is important for the future development. See the sticky topic at the beginning of this subforum for details if you want.

[hatzfeld]

Could you probably add the ID strings that version 1.0.2 prints out?

Here is the output:

Code: Select all

Looking for default devices ...
 Found default devices (1)
Accessing device 002 on bus 003 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 No driver found. Either detached before or never attached

Received inquiry data (detailed identification)
-------------------------
  Vendor String: ZTE
 Product String: USB SCSI CD-ROM
Revision String: 2.31
-------------------------

Device description data (identification)
-------------------------
Manufacturer: ZTE,Incorporated
     Product: ZTE CDMA Technologies MSM
  Serial No.: P673M2TMOBLCDROM
-------------------------

[Josh]

Thanks a lot

[rouhopher]

So it is just unpacking the file and run it. The device should just present to function the running of the file. Anyway, the future version might be better so I’ll just wait for that.



[mod: signature removed - no ads please]

[minaberfog]

That had happen to me last time that I am doing my setup. Anyway, I need to try this one later to that I can use my web connect now. It is just a complicated thing but it is quite working.






[mod: signature removed - no ads please]