Usb_modeswitch with ZTE AC8710
It seem ZTE AC8710 with storage, and it vendor id = 0x19d2, product id = 0xfff6, but I can't switch storage mode to modem mode
insmod ohci-hcd.ko
rmmod usb-storage.ko
insmod usbserial.ko vendor=0x19d2 product=0xfff6
only can get ttyUSB0 and can't get ATCOMMAND's response
I need a help to do mode_switch.
insmod ohci-hcd.ko
rmmod usb-storage.ko
insmod usbserial.ko vendor=0x19d2 product=0xfff6
only can get ttyUSB0 and can't get ATCOMMAND's response
I need a help to do mode_switch.
I just rebuild kernel ,and modulize the ohci-hcd.ko
the command I used to change storage mode to modem mode look like :
usb_modeswitch -v 0x19d2 -p 0xfff6 -m 0a -M 5553424312345678000000000000061b000000030000000000000000000000
usb_modeswitch -v 0x19d2 -p 0xfff6 -m 0a -M 55534243f8f993882000000080000a85010101180101010101000000000000
the command I used to change storage mode to modem mode look like :
usb_modeswitch -v 0x19d2 -p 0xfff6 -m 0a -M 5553424312345678000000000000061b000000030000000000000000000000
usb_modeswitch -v 0x19d2 -p 0xfff6 -m 0a -M 55534243f8f993882000000080000a85010101180101010101000000000000
-
- Posts: 5
- Joined: 25 Apr 2009, 11:15
- Contact:
Well, sfe doesn't seem to care anymore; or he/she was successful and didn't care to report it.
O.K.; please be so kind and clarify a bit what you've done so far: output of a plain "lsusb" (unswitched device), the command line or configuration you used, and the result ("lsusb" again after trying to switch).
O.K.; please be so kind and clarify a bit what you've done so far: output of a plain "lsusb" (unswitched device), the command line or configuration you used, and the result ("lsusb" again after trying to switch).
-
- Posts: 5
- Joined: 25 Apr 2009, 11:15
- Contact:
Hi,
I tried using a ZTE High speed CDMA modem. (ZTE AC8710 vendor=0x19d2 product=0xfff1) in an embedded device running 2.6.22 kernel.
But it always gets detected as mass storage device and the product id comes as 0xfff6
I've got this modem working on Fedora core 10 using the manufacturer driver but I want the usb_modeswitch module to work for this so that we can use this modem anywhere. Moreover the manufacture has made it work in a proprietary way and has not provided the source code fully. Especially the mode switching routine they have not given the source code.
DUMP from EMBEDDED DEVICE
------------------------------------------
usb 2-1: new full speed USB device using tangox-ohci-hcd and address 4
usb 2-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
sr0: scsi-1 drive
sr 3:0:0:0: Attached scsi CD-ROM sr0
sr 3:0:0:0: Attached scsi generic sg0 type 5
usb-storage: device scan complete
lsusb:
Bus 002 Device 004: ID 19d2:fff6
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
I cross compiled usb_modeswitch but it doesn't work. If you can help me out or give me some more pointer to try out.
I works in my fedora core 10 system using a binary mode ztemtvcdromd . The driver URL is
http://www.ztemt.com.cn/ennewzte/service/ziliao.action
Here you can download the linux driver and modify the generic.c in kernel module from 0xffff to 0xfff11
This daemon just inserts some udev rules by which the device gets changed from 0xfff6 to 0xfff1 which is the real modem.
After that connecting is very easy as its just a usbserial driver work.
The system where it works I've got the udevmonitor dump. I just need to know how to add commands by which it would come to the correct mode.
Any other info is required please let me know.
Thanks in advance.
WORKING DUMP FROM FEDORA CORE 10 PC
----------------------------------------------------------
usb 8-1: new full speed USB device using uhci_hcd and address 4
usb 8-1: configuration #1 chosen from 1 choice
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb 8-1: New USB device found, idVendor=19d2, idProduct=fff6
usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 8-1: Product: USB Storage
usb 8-1: Manufacturer: ZTE, Incorporated
usb 8-1: SerialNumber: 000000000002
usb-storage: device scan complete
scsi 5:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
sr1: scsi-1 drive
sr 5:0:0:0: Attached scsi CD-ROM sr1
sr 5:0:0:0: Attached scsi generic sg2 type 5
usb 8-1: USB disconnect, address 4
usb 8-1: new full speed USB device using uhci_hcd and address 5
usb 8-1: configuration #1 chosen from 1 choice
usbserial_generic 8-1:1.0: generic converter detected
usb 8-1: generic converter now attached to ttyUSB0
usbserial_generic 8-1:1.1: generic converter detected
usb 8-1: generic converter now attached to ttyUSB1
usbserial_generic 8-1:1.2: generic converter detected
usb 8-1: generic converter now attached to ttyUSB2
usbserial_generic 8-1:1.3: generic converter detected
usb 8-1: generic converter now attached to ttyUSB3
usbserial_generic 8-1:1.4: generic converter detected
usb 8-1: generic converter now attached to ttyUSB4
usb 8-1: New USB device found, idVendor=19d2, idProduct=fff1
usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 8-1: Product: ZTE CDMA Tech
usb 8-1: Manufacturer: ZTE, Incorporated
lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 005: ID 19d2:fff1 ONDA Communication S.p.A.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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
[root@akhilesh ~]#
udevmonitor
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
UEVENT[1239977929.900549] add /devices/pci0000:00/0000:00:
1d.2/usb8/8-1 (usb)
UEVENT[1239977929.903236] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0 (usb)
[edited for readability, Josh]
UDEV [1239977937.211584] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.1/usb_endpoint/usbdev8.3_ep04 (usb_endpoint)
UDEV [1239977937.211736] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.4/usb_endpoint/usbdev8.3_ep06 (usb_endpoint)
UDEV [1239977937.213554] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/usb_endpoint/usbdev8.3_ep00 (usb_endpoint)
Regards,
Akhilesh
I tried using a ZTE High speed CDMA modem. (ZTE AC8710 vendor=0x19d2 product=0xfff1) in an embedded device running 2.6.22 kernel.
But it always gets detected as mass storage device and the product id comes as 0xfff6
I've got this modem working on Fedora core 10 using the manufacturer driver but I want the usb_modeswitch module to work for this so that we can use this modem anywhere. Moreover the manufacture has made it work in a proprietary way and has not provided the source code fully. Especially the mode switching routine they have not given the source code.
DUMP from EMBEDDED DEVICE
------------------------------------------
usb 2-1: new full speed USB device using tangox-ohci-hcd and address 4
usb 2-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
sr0: scsi-1 drive
sr 3:0:0:0: Attached scsi CD-ROM sr0
sr 3:0:0:0: Attached scsi generic sg0 type 5
usb-storage: device scan complete
lsusb:
Bus 002 Device 004: ID 19d2:fff6
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
I cross compiled usb_modeswitch but it doesn't work. If you can help me out or give me some more pointer to try out.
I works in my fedora core 10 system using a binary mode ztemtvcdromd . The driver URL is
http://www.ztemt.com.cn/ennewzte/service/ziliao.action
Here you can download the linux driver and modify the generic.c in kernel module from 0xffff to 0xfff11
This daemon just inserts some udev rules by which the device gets changed from 0xfff6 to 0xfff1 which is the real modem.
After that connecting is very easy as its just a usbserial driver work.
The system where it works I've got the udevmonitor dump. I just need to know how to add commands by which it would come to the correct mode.
Any other info is required please let me know.
Thanks in advance.
WORKING DUMP FROM FEDORA CORE 10 PC
----------------------------------------------------------
usb 8-1: new full speed USB device using uhci_hcd and address 4
usb 8-1: configuration #1 chosen from 1 choice
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb 8-1: New USB device found, idVendor=19d2, idProduct=fff6
usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 8-1: Product: USB Storage
usb 8-1: Manufacturer: ZTE, Incorporated
usb 8-1: SerialNumber: 000000000002
usb-storage: device scan complete
scsi 5:0:0:0: CD-ROM ZTE USB Storage FFF1 2.31 PQ: 0 ANSI: 2
sr1: scsi-1 drive
sr 5:0:0:0: Attached scsi CD-ROM sr1
sr 5:0:0:0: Attached scsi generic sg2 type 5
usb 8-1: USB disconnect, address 4
usb 8-1: new full speed USB device using uhci_hcd and address 5
usb 8-1: configuration #1 chosen from 1 choice
usbserial_generic 8-1:1.0: generic converter detected
usb 8-1: generic converter now attached to ttyUSB0
usbserial_generic 8-1:1.1: generic converter detected
usb 8-1: generic converter now attached to ttyUSB1
usbserial_generic 8-1:1.2: generic converter detected
usb 8-1: generic converter now attached to ttyUSB2
usbserial_generic 8-1:1.3: generic converter detected
usb 8-1: generic converter now attached to ttyUSB3
usbserial_generic 8-1:1.4: generic converter detected
usb 8-1: generic converter now attached to ttyUSB4
usb 8-1: New USB device found, idVendor=19d2, idProduct=fff1
usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 8-1: Product: ZTE CDMA Tech
usb 8-1: Manufacturer: ZTE, Incorporated
lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 005: ID 19d2:fff1 ONDA Communication S.p.A.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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
[root@akhilesh ~]#
udevmonitor
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
UEVENT[1239977929.900549] add /devices/pci0000:00/0000:00:
1d.2/usb8/8-1 (usb)
UEVENT[1239977929.903236] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0 (usb)
[edited for readability, Josh]
UDEV [1239977937.211584] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.1/usb_endpoint/usbdev8.3_ep04 (usb_endpoint)
UDEV [1239977937.211736] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.4/usb_endpoint/usbdev8.3_ep06 (usb_endpoint)
UDEV [1239977937.213554] add /devices/pci0000:00/0000:00:1d.2/usb8/8-1/usb_endpoint/usbdev8.3_ep00 (usb_endpoint)
Regards,
Akhilesh
Your data is all very well, but does not really help here.
1. What are these udev rules inserted by the proprietary tool? Do they call annother proprietary binary? Or is it just "eject"? Did you try the "eject" command?
2. If no ZTE method works you need to sniff on the Windows driver. A link to a good example how to do it is on the USB_ModeSwitch main documentation page (see "Contribute").
1. What are these udev rules inserted by the proprietary tool? Do they call annother proprietary binary? Or is it just "eject"? Did you try the "eject" command?
2. If no ZTE method works you need to sniff on the Windows driver. A link to a good example how to do it is on the USB_ModeSwitch main documentation page (see "Contribute").
-
- Posts: 5
- Joined: 25 Apr 2009, 11:15
- Contact:
Yes I tried Eject command it didn't work.
Yes they call a propreitary binary which does the magic by adding ude rules.
My idea of giving log was to have somebody see the working udev dump and help me to form some udev rules to switch the device.
All the working udev rules I've captured using usbmonitor but I can't translate them to some script which can do the same.
Let see if somebody can enlighten us.
Regards,
Akhilesh
Yes they call a propreitary binary which does the magic by adding ude rules.
My idea of giving log was to have somebody see the working udev dump and help me to form some udev rules to switch the device.
All the working udev rules I've captured using usbmonitor but I can't translate them to some script which can do the same.
Let see if somebody can enlighten us.
Regards,
Akhilesh
Hello, I am new in Linux (I have Ubuntu 9.04).
I am trying to install ZTE AC8710 USB modem on Ubuntu, but it shows USB flash drive and not modem.
If I understood right USB_ModeSwitch can help with this problem.
Should I be geek to use it?
Can anybody help with this? Or at least point me where to start reading =)
TIA
Michael
I am trying to install ZTE AC8710 USB modem on Ubuntu, but it shows USB flash drive and not modem.
If I understood right USB_ModeSwitch can help with this problem.
Should I be geek to use it?
Can anybody help with this? Or at least point me where to start reading =)
TIA
Michael
Ok, so I installed USB_ModeSwitch and trying to use it but with no success.
Here is my output:
root@khurtsiya-laptop:~/Desktop/usb_modeswitch-0.9.7# lsusb
Bus 002 Device 003: ID 064e:a103 Suyin Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 19d2:fff5
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0458:0036 KYE Systems Corp. (Mouse Systems) Pocket Mouse LE
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07ca:a309 AVerMedia Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 138a:0001
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
root@khurtsiya-laptop:~/Desktop/usb_modeswitch-0.9.7# usb_modeswitch -v 0x19d2 -p 0xfff5 -V 0x19d2 -P 0xfff1 -m 0x01 -M 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 002 on bus 006 ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
Sending the message returned error -2. Trying to continue
-> Run lsusb to note any changes. Bye
root@khurtsiya-laptop:~/Desktop/usb_modeswitch-0.9.7# lsusb
Bus 002 Device 003: ID 064e:a103 Suyin Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 19d2:fff5
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0458:0036 KYE Systems Corp. (Mouse Systems) Pocket Mouse LE
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07ca:a309 AVerMedia Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 138a:0001
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
Here is my output:
root@khurtsiya-laptop:~/Desktop/usb_modeswitch-0.9.7# lsusb
Bus 002 Device 003: ID 064e:a103 Suyin Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 19d2:fff5
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0458:0036 KYE Systems Corp. (Mouse Systems) Pocket Mouse LE
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07ca:a309 AVerMedia Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 138a:0001
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
root@khurtsiya-laptop:~/Desktop/usb_modeswitch-0.9.7# usb_modeswitch -v 0x19d2 -p 0xfff5 -V 0x19d2 -P 0xfff1 -m 0x01 -M 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 002 on bus 006 ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
Sending the message returned error -2. Trying to continue
-> Run lsusb to note any changes. Bye
root@khurtsiya-laptop:~/Desktop/usb_modeswitch-0.9.7# lsusb
Bus 002 Device 003: ID 064e:a103 Suyin Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 19d2:fff5
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0458:0036 KYE Systems Corp. (Mouse Systems) Pocket Mouse LE
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 07ca:a309 AVerMedia Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 138a:0001
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
Hi, I must have missed your first post.
As you can see from this thread, none of the participants so far was willing to do the basic work of sniffing this device in Windows (or to share any findings). So there is not much useful information at the moment.
The first poster found a default product ID of 0xfff6, contrary to your data. So there might even be several variants of the device around.
Will you try to find the right sequence?
You'll get your first geek stripes afterwards
As you can see from this thread, none of the participants so far was willing to do the basic work of sniffing this device in Windows (or to share any findings). So there is not much useful information at the moment.
The first poster found a default product ID of 0xfff6, contrary to your data. So there might even be several variants of the device around.
Will you try to find the right sequence?
You'll get your first geek stripes afterwards