Author Message

<  Device Information  ~  Success report: ZTE K3565-Z

PostPosted: Fri May 08, 2009 4:45 pm
Posts: 6Joined: Fri May 08, 2009 1:19 am
After hours and hours I finally succeed to unlock my brand new ZTE 3565-Z (from SFR, in France).

This device have a microSD slot. It is labelled K3564-Z and FFC ID Q78-K3565-Z. The Windows drivers are labelled K3520. And the Windows modem diagnostic display K3565-Z (very usefull idea: viewtopic.php?t=152).


This device works perfectly under Windows XP pro.
I then tryied to made it work under the latest Ubuntu. It worked once, then never again. I don't understand how. I recompiled the kernel because of "unusual_devs.h" but nothing better.
I dropped this (stupid?) distro and switched to my favorite Debian: immediate success.

For the ZTE 6535-Z you just have to use the same command as for ZTE MF626 / MF628+, but the target product is 0x0052 and you have to wait at least 8 seconds to see it (9 is better), because the device first disappear and it took times to have the new ones.

Note that I sniffed the datas when using Windows XP and didn't managed to do anything uselfull with them. Nowhere I saw the same datas that the ones I use under Linux. I then think about some "compatibility mode" or so: this device probably respond to different commands.

Before the device is switched, lsusb display it only 5 seconds after. The red led on the device start to flash about 10 seconds after the connection. You then have 19d2:2000 as a mass storage, but you can't access the mass storage under Linux (or maybe you have to use special module ? I don't bother). Once the swith command is sent to the device, you have to wait 8 seconds to see the new ones. You then have 19d2:0052 with several devices inside. The mass storage and the modem work at the same time (in Windows, you can use the modem and the storage at the same time too. Not tested with the microSD).



Code:
# dmesg
[20542.992830] usb 5-3: new high speed USB device using ehci_hcd and address 15
[20543.302524] usb 5-3: configuration #1 chosen from 1 choice
[20543.304034] usb-storage: device ignored
[20543.304186] usb 5-3: New USB device found, idVendor=19d2, idProduct=2000
[20543.304193] usb 5-3: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[20543.304196] usb 5-3: Product: ZTE CDMA Technologies MSM
[20543.304201] usb 5-3: Manufacturer: ZTE, Incorporated


Code:
# lsusb -d 19d2:2000 -v
Bus 005 Device 015: ID 19d2:2000 ONDA Communication S.p.A.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x19d2 ONDA Communication S.p.A.
  idProduct          0x2000
  bcdDevice            0.00
  iManufacturer           2 ZTE, Incorporated
  iProduct                1 ZTE CDMA Technologies MSM
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      5 SFF-8070i
      bInterfaceProtocol     80
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered



Code:
# usb_modeswitch --DefaultVendor 0x19d2 --DefaultProduct 0x2000 --TargetVendor 0X19d2 --TargetProduct 0x0052 --success 8 --MessageEndpoint 0x01 --MessageContent 55534243123456782000000080000c85010101180101010101000000000000

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

Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found default devices (1)
Prepare switching, accessing device 015 on bus 005 ...
Looking for active driver ...
 No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
 OK, message successfully sent
Checking for mode switch after 8 seconds settling time ...
 Original device can't be accessed anymore. Good.
 Found a new device in target mode or class

Mode switch was successful. Bye!


Code:
# dmesg
[20757.342196] usb 5-3: USB disconnect, address 15
[20762.728303] usb 5-3: new high speed USB device using ehci_hcd and address 16
[20762.899353] usb 5-3: configuration #1 chosen from 1 choice
[20762.917652] scsi26 : SCSI emulation for USB Mass Storage devices
[20762.918044] scsi27 : SCSI emulation for USB Mass Storage devices
[20762.918273] usb 5-3: New USB device found, idVendor=19d2, idProduct=0052
[20762.918281] usb 5-3: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[20762.918283] usb 5-3: Product: ZTE CDMA Technologies MSM
[20762.918288] usb 5-3: Manufacturer: ZTE, Incorporated
[20762.918292] usb 5-3: SerialNumber: 1234567890ABCDEF
[20762.918310] usb-storage: device found at 16
[20762.918312] usb-storage: waiting for device to settle before scanning
[20762.925756] usb-storage: device found at 16
[20762.925763] usb-storage: waiting for device to settle before scanning
[20763.873984] ACPI: Transitioning device [FAN1] to D0
[20763.873984] ACPI: Unable to turn cooling device [f7437fa4] 'on'
[20763.885982] ACPI: Transitioning device [FAN1] to D0
[20763.885982] ACPI: Unable to turn cooling device [f7437fa4] 'on'
[20767.947035] usb-storage: device scan complete
[20767.955031] scsi 27:0:0:0: CD-ROM            ZTE      USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 0
[20767.955031] usb-storage: device scan complete
[20767.955031] scsi 26:0:0:0: Direct-Access     ZTE      MMC Storage      2.31 PQ: 0 ANSI: 2
[20767.971030] sr1: scsi3-mmc drive: 0x/52x cd/rw xa/form2 cdda tray
[20767.971030] sr 27:0:0:0: Attached scsi CD-ROM sr1
[20767.971030] sr 27:0:0:0: Attached scsi generic sg2 type 5
[20767.974094] sd 26:0:0:0: [sdb] Attached SCSI removable disk
[20767.974142] sd 26:0:0:0: Attached scsi generic sg3 type 0
[20781.259349] ISO 9660 Extensions: Microsoft Joliet Level 1
[20781.261906] ISOFS: changing to secondary root

note that the four ACPI lines are always present at the same place.

Code:
# lsusb -d 19d2:0052 -v

Bus 005 Device 016: ID 19d2:0052 ONDA Communication S.p.A.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x19d2 ONDA Communication S.p.A.
  idProduct          0x0052
  bcdDevice            0.00
  iManufacturer           2 ZTE, Incorporated
  iProduct                1 ZTE CDMA Technologies MSM
  iSerial                 3 1234567890ABCDEF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          184
    bNumInterfaces          7
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      5 SFF-8070i
      bInterfaceProtocol     80
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x89  EP 9 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered


Offline Profile
PostPosted: Fri May 08, 2009 9:36 pm
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
Excellent analysis!

The line
Code:
[20543.304034] usb-storage: device ignored

is an idication for an IGNORE entry in unusual_devs.h; you kept it in Debian, right? Otherwise, there wouldn't be a problem to access the initial storage device. Well, who cares, right?


Offline Profile
PostPosted: Fri May 08, 2009 9:51 pm
Posts: 6Joined: Fri May 08, 2009 1:19 am
Josh wrote:
The line
Code:
[20543.304034] usb-storage: device ignored

is an idication for an IGNORE entry in unusual_devs.h; you kept it in Debian, right? Otherwise, there wouldn't be a problem to access the initial storage device. Well, who cares, right?


This is a fresh Debian installation used as a sandbox for my tests, with stock kernel 2.6.26-2. The Ubuntu (on the same computer) have 2.6.28-11 (stock kernel) and 2.6.29 (compiled by me).

This means even with this unusual_dev.h the device works well. Then with Ubuntu their is something else preventing things to work. Any clue ?


Offline Profile
PostPosted: Sat May 09, 2009 1:01 am
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
Either it's an udev thing (probably trying to remember devices, just like Windows does) or it's the newer kernel; there are ever more attempts to switch devices via special handling in usb-storage.

I am not very fond of these entries because they tend to interfere with usb_modeswitch and often don't even work right.


Offline Profile
PostPosted: Sat May 09, 2009 12:41 pm
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
Did you ever try to use the last message string from your log?

MessageContent="55534243123456782400000080000c12000000240000000000000000000000"

Mind that the eight chars after "55534243" are just a tag, a kind of fingerprint for that specific command packet. I'm always replacing it with "12345678" to make clear it's not part of the command. Obviously it is not good for telling two commands apart.


Offline Profile
PostPosted: Sat May 09, 2009 1:20 pm
Posts: 6Joined: Fri May 08, 2009 1:19 am
Josh wrote:
Did you ever try to use the last message string from your log?

Already tested, as the others. Just redone it to be sure (cut and paste with your datas), but nothing happens.


Offline Profile
PostPosted: Sat May 09, 2009 9:53 pm
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
Maybe all of the bulk transfers in the log have to be implemented. Including transmitting all those zeros and everything.

That's the joy of reingeneering :roll:


Offline Profile
PostPosted: Sat May 09, 2009 10:50 pm
Posts: 6Joined: Fri May 08, 2009 1:19 am
Josh wrote:
Maybe all of the bulk transfers in the log have to be implemented. Including transmitting all those zeros and everything.


I did it. If I remeber well, 4 usb_modeswitch in a row. But maybe we have to read values, or to send a reset or so.

Really, I don't understand why designers/manufacturers don't give details. Just imagine the first who give the specs: immediate fame :-)


Offline Profile
PostPosted: Fri Jul 31, 2009 5:21 pm
Me, as windows-dau, doesn't get it working yet. Try to make alle the things you listed above.

First i installed the drivers, than i changed the modeswitch-conf file, but the device not change (lsusb still listed 19d2:2000 even after a period of waiting time)

Here my ConfFile
Code:
########################################################
# ZTE MF628+ (tested version from Telia / Sweden)
# ZTE MF626
# ZTE MF636 (aka "Telstra / BigPond 7.2 Mobile Card")
#
# Contributor: Joakim Wennergren

DefaultVendor=  0x19d2
DefaultProduct= 0x2000

TargetVendor=   0x19d2
TargetProduct=  0x0052
;TargetProduct=  0x0031

# only for reference
# MessageEndpoint=0x01

MessageContent="55534243123456782000000080000c85010101180101010101000000000000"

# if that command doesn't work, try the other ("eject")
;MessageContent="5553424312345678000000000000061b000000030000000000000000000000"



Output:
Code:
Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found default devices (1)
Accessing device 029 on bus 005 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached

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.: P673A2VDF_MS
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
 OK, message successfully sent
-> Run lsusb to note any changes. Bye.



Somebody an idea?

thx a lot
D


PostPosted: Fri Jul 31, 2009 10:21 pm
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
First, make sure your config file entry is really active. Run "usb_modeswitch -W" and check the value of the variables.

Then I recommend looking at this posting:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=919#919

Try all the commands listed there; you can paste all the different MessageContents into your config file and activate/deactivate them by commenting out or in with ";" or "#"). Only one should be active at any time, of course.


Offline Profile
PostPosted: Sat Aug 01, 2009 12:38 am
Hi thx for your help, but it seems that i am too stupid to get it working.
here all in detail again, device:

Stick:
Vodafone Mobile Connect
HSDPA USB Stick
Model: K3565-Z

i Try all of the six Statements (not in the config, but copy it direct to my terminal, with same Output at all), the storage disappered from my folder list as storage device, but with lsusb it still remains with the entry: 19d2:2000 .

Here my Output with "-W":
Code:
 * usb_modeswitch: tool for controlling "flip flop" mode USB devices
 * Version 1.0.2 (C) Josua Dietze 2009
 * Works with libusb 0.1.12 and probably other versions

Reading config file: /etc/usb_modeswitch.conf
DefaultVendor=  0x19d2
DefaultProduct= 0x2000
TargetVendor=   0x19d2
TargetProduct=  0x0031
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint= not set
MessageContent="55534243123456782000000080000c85010101180101010101000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 005
usb_os_find_busses: Found 004
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 043 on 005
usb_os_find_devices: Found 001 on 005
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 001 on 001

Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found default devices (1)
Accessing device 043 on bus 005 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached

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.: P673A2VDF_MS
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
 OK, message successfully sent
-> Run lsusb to note any changes. Bye.

dadom@domeee:/media/disk/Downloads/usb_modeswit


Here the active Part of my Config:
Code:
########################################################
# ZTE MF628+ (tested version from Telia / Sweden)
# ZTE MF626
# ZTE MF636 (aka "Telstra / BigPond 7.2 Mobile Card")
#
# Contributor: Joakim Wennergren

DefaultVendor=  0x19d2
DefaultProduct= 0x2000

TargetVendor=   0x19d2
;TargetProduct=  0x0052
TargetProduct=  0x0031

# only for reference
#MessageEndpoint=0x01

MessageContent="55534243123456782000000080000c85010101180101010101000000000000"

# if that command doesn't work, try the other ("eject")
;MessageContent="5553424312345678000000000000061b000000030000000000000000000000"



lsusb:
Code:
Bus 005 Device 043: ID 19d2:2000 
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 0b05:b700 ASUSTek Computer, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub



thx 4 helping again
Dom


PostPosted: Sun Aug 02, 2009 11:18 am
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
Just to make sure: you are running the program as "root", aren't you?

If you have the possibility on your desktop to "eject" the pseudo CD-ROM you can try that once. Alternatively, there is a command line program called "eject" as well; you need to call it with the right storage drive name (like "eject /dev/sdb"). The output of "dmesg" should give you a hint for the name right after you plugged the modem in.

Your output of "lsusb" is somewhat strange because the device name of the modem is not given. If all fails there might be a hardware problem with the thing. Do you have annother machine to test it on?


Offline Profile
PostPosted: Tue Aug 04, 2009 12:01 pm
Josh wrote:
Just to make sure: you are running the program as "root", aren't you?


Yes, do all that things with "sudo" command in front.

Josh wrote:
If you have the possibility on your desktop to "eject" the pseudo CD-ROM you can try that once.


I have try the following settings and all the listed Messages once with unmounted usb device and once with mounted device: nothing seems to work, device stay with 19d2:2000

Settings:
Code:
DefaultVendor=  0x19d2
DefaultProduct= 0x2000

TargetVendor=   0x19d2
TargetProduct=  0x0031

# only for reference
;MessageEndpoint=0x01

;MessageContent="55534243123456782000000080000c85010101180101010101000000000000"
 ;MessageContent="55534243f8f993882000000080000a85010101180101010101000000000000"
;MessageContent="5553424312345678000000000000061b000000030000000000000000000000"
MessageContent="55534243123456782000000080000c85010101180101010101000000000000"


I recognize one further crazy thing: if i eject the device on my self (eject in the file manager), the device disappeared, and the output of lsusb changed:
from: Bus 005 Device 019: ID 19d2:2000
to: Bus 005 Device 020: ID 19d2:0063

But that not seems to fix the problem, my Connection Software (umtsmon v.0.9) still alerts that no device could be found.

Josh wrote:
Do you have annother machine to test it on?


I tested on a Windows XP machine, after some configuration work (use the Vodafone Stick with a Fonic SIM Card (Germany)), i get it running, on Windows it seems there is no switching issues, two devices are installed in windows (Modem and Storage), > works: Device recognized, Internet Connection established.

I thought that it maybe have something todo with the drivers, so i removed, the driver and used the installed script i find on betavine:
https://forge.betavine.net/frs/download ... taller.run
Now i have i Vodafone Icon in on my Desktop and the Problem is still active :(

Me is somekind of hopeless...somebody more good ideas?
thx a lot
D


PostPosted: Tue Aug 04, 2009 6:15 pm
Site AdminPosts: 4702Joined: Sat Nov 03, 2007 12:30 am
No reason to lose hope :P

In fact, the "eject" did obviously change the device. But there is no driver bound to it for use as a modem device. Still, you are halfway there!

Can you post the final output lines of "dmesg" right after plugging in and ejecting from the file manager?


Offline Profile
PostPosted: Tue Aug 04, 2009 7:23 pm
First: Very very much for your patienc and help.
Second: Get it Running *jumpUp*

I try to get the Beta Software of Vodafone running, therefor it seems that i make somethink real stupid because i removed the desktop manager and god knows what else, so i reinstall my System with EEEBuntu NBR .

Here my Working Story, maybe somebody will find it helpful:
https://forge.betavine.net/frs/?group_id=12
go there, under the point. " Debian, Ubuntu, Ubuntu Netbook Remix, Linux Mint" i downloaded:

- ozerocdoff_0.4-2_i386.deb
- usb-modeswitch_0.9.4-1_i386.deb
- vodafone-mobile-connect_2.10.01-1_all.deb

and install all (in this order) with the normal install-routines. I dont's know if the last thing is necessary, this is the original vodafone software (which after a system update, does't start anymore), but in my opinion the drivers are installed this way too.

Now i installed "UMTSmon"
http://umtsmon.sourceforge.net/

After the start of umtsmon, the Stick switch to modem-mode (yes really ;) ) .

After detecting the provider (in my german-case: Fonic, displayed as O2, but it's correct). Change in Profil Settings the APN to: pinternet.interkom.de . In my case there was still a problem (SMS sending works, but no PPP Connection, got an Timeout), in the starting Screen of the software (with some warnings) i recognize 2 USB device he seems to use (ttyUSB1,ttyUSB3), in the PPP Error he try to use one of them (ttyUSB1). Then i start the programm with the following command, and it works perfect:

./umtsmon -s ttyUSB3

thx for helping again @ Josh, don't know what in fact now was the problem, the last device switch to 19d2:0063 seems to be correct, maybe the drivers, maybe bad installation of the software...

Greets
Dom


Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 2
25 posts
Go to page 1, 2  Next
Users browsing this forum: No registered users and 2 guests
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum