Author Message

<  Device Information  ~  ZTE MF90C from H3G Italy

PostPosted: Thu Feb 02, 2017 7:28 pm Reply with quote
Posts: 2 Joined: Thu Feb 02, 2017 7:19 pm
Hi to all,

I trying to switch a ZTE MF90C with usb_modeswitch 2.5.0 without success. I tried many configurations but none is working.

This is the result with lsusb
Code:
lsusb -d 19d2:2004 -v

Bus 001 Device 070: ID 19d2:2004 ZTE WCDMA Technologies MSM
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x19d2 ZTE WCDMA Technologies MSM
  idProduct          0x2004
  bcdDevice           f1.2b
  iManufacturer           1 ZTE,Incorporated
  iProduct                2 ZTE WCDMA Technologies MSM
  iSerial                 3 MF90C0ZTED000000CP261718N5N0QU5OMA8D_35161H2G&&&&&&&&&&&&&&&&&&0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              4 Mass Storage
      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
      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               1
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:     0x0000
  (Bus Powered)


CD-ROM is not ready so there is no software for switch in windows.
Could someone send me the software on virtual cdrom in MF90C Virgin Australia? I would like to try it and sniff data, but I can't find in any place.

Thank you to all for help and suggestions.


Offline
PostPosted: Fri Feb 03, 2017 4:10 am Reply with quote
Posts: 1166 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
juvann wrote:
I trying to switch a ZTE MF90C with usb_modeswitch 2.5.0 without success. I tried many configurations but none is working.


You shouldn't need to try many configurations, the config file for 19d2:2004 included in the usb_modeswitch data package works.

juvann wrote:
CD-ROM is not ready so there is no software for switch in windows.


Why is cd-rom not ready? What hardware is the device plugged into and how is usb_modeswitch invoked?

A manual modeswitch from cmd line is:

usb_modeswitch -v 19d2 -p 2004 -K -W


Offline
PostPosted: Fri Feb 03, 2017 6:10 pm Reply with quote
Posts: 2 Joined: Thu Feb 02, 2017 7:19 pm
LOM wrote:
You shouldn't need to try many configurations, the config file for 19d2:2004 included in the usb_modeswitch data package works.

In the config file there is ZTE MF60, but my modem/router is MF90C and has the same product id.

LOM wrote:
Why is cd-rom not ready?
In don't know why, MF90C can be a wifi router and usb modem. With usb modem I see a virtual CD-ROM in linux and windows, but this CD-ROM is not ready maybe the firmware used by H3G Italy not has the software, so I never used as usb modem.

LOM wrote:
What hardware is the device plugged into and how is usb_modeswitch invoked?

I tried with
Code:
./usb_modeswitch -I -W -c test.conf

where is test.conf there are
Code:
# ZTE MF60
DefaultVendor=   0x19d2
DefaultProduct=  0x2004

TargetVendor=0x19d2
TargetProduct=0x1402
StandardEject=1


or with MessageContent taken from other ZTE's devices for example 19d2:0388 where there is the comment "ZTE MF90 Mobile Hotspot" but the product id is different from mine.

LOM wrote:
A manual modeswitch from cmd line is:

usb_modeswitch -v 19d2 -p 2004 -K -W


I got this result, but on /var/log/messages or lsusb nothing happens or is changed
Code:
usb-modeswitch-2.5.0$ ./usb_modeswitch -v 19d2 -p 2004 -K -W
Take all parameters from the command line


 * usb_modeswitch: handle USB devices with multiple modes
 * Version 2.5.0 (C) Josua Dietze 2017
 * Based on libusb1/libusbx

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x19d2
DefaultProduct= 0x2004

StandardEject=1

Look for default devices ...
  found USB ID 0c45:649a
  found USB ID 0bda:0129
  found USB ID 0cf3:0036
  found USB ID 046d:c043
  found USB ID 8087:8000
  found USB ID 1d6b:0002
  found USB ID 1d6b:0003
  found USB ID 19d2:2004
   vendor ID matched
   product ID matched
  found USB ID 1d6b:0002
 Found devices in default mode (1)
Access device 002 on bus 002
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 8
Use endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
     Product: ZTE WCDMA Technologies MSM
  Serial No.: MF90C0ZTED000000CP261718N5N0QU5OMA8D_35161H2G&&&&&&&&&&&&&&&&&&0
-------------------------
Sending standard EJECT sequence
Looking for active driver ...
 OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Read the response to message 1 (CSW) ...
 Response successfully read (13 bytes), status 0
Trying to send message 2 to endpoint 0x01 ...
 OK, message successfully sent
Read the response to message 2 (CSW) ...
 Response successfully read (13 bytes), status 0
Trying to send message 3 to endpoint 0x01 ...
 OK, message successfully sent
Read the response to message 3 (CSW) ...
 Response successfully read (13 bytes), status 1
Trying to send message 4 to endpoint 0x01 ...
 OK, message successfully sent
Read the response to message 4 (CSW) ...
 Response successfully read (13 bytes), status 1
Reset response endpoint 0x81
Reset message endpoint 0x01
-> Run lsusb to note any changes. Bye!



Offline
PostPosted: Sat Feb 04, 2017 9:10 am Reply with quote
Posts: 1166 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
juvann wrote:
LOM wrote:
Why is cd-rom not ready?

In don't know why, MF90C can be a wifi router and usb modem. With usb modem I see a virtual CD-ROM in linux and windows, but this CD-ROM is not ready maybe the firmware used by H3G Italy not has the software, so I never used as usb modem.


The cd-rom should be accessible and that is essential for switching and also for copying the connection manager and drivers from it in Windows. The StandardEject is a cd-rom command and it needs to be able to communicate with the cd-rom.
Does the the device work for you in Windows with usb tethering?


Offline

Display posts from previous:  Sort by:

All times are UTC+02:00
Page 1 of 1
4 posts
Users browsing this forum: No registered users and 3 guests
Search for:
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