[ask]Hisense E89

Alex.C · Post by **Alex.C** » 13 May 2012, 14:52

i c pid changed from f009 to 908a,but there is no ttyusb or ttyacm in dev,what should i do next?

acer a500 ICS4.04(thor V160)
3G phone: hisense E89
usb_modeswitch-1.1.9-arm-static.bz2.

Code: Select all

root@android:/ # usb_modeswitch -c /etc/usb_modeswitch.d/109b\:f009 -s 20 -W
usb_modeswitch -c /etc/usb_modeswitch.d/109b\:f009 -s 20 -W

 * usb_modeswitch: handle USB devices with multiple modes
 * Version 1.1.9 (C) Josua Dietze 2011
 * Based on libusb0 (0.1.12 and above)

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x109b
DefaultProduct= 0xf009
TargetVendor=   0x109b
TargetProduct=  0x908a
TargetClass=    not set
TargetProductList=""

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint=  not set
MessageContent="5553424380995386000000000000061b000000020000000000000000000000"
NeedResponse=1
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check enabled, max. wait time 20 seconds
System integration mode disabled

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 023 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device

Looking for target devices ...
  searching devices, found USB ID 109b:f009
   found matching vendor ID
  searching devices, found USB ID 1d6b:0002
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 109b:f009
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1d6b:0002
 Found devices in default mode, class or configuration (1)
Accessing device 023 on bus 001 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
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

SCSI inquiry data (for identification)
-------------------------
  Vendor String: eSurfing
   Model String: Mass storage
Revision String: ffff
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: Hisense Incorporated
     Product: Hisense HSUSB Device
  Serial No.: not provided
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to message 1 (CSW) ...
USB error: error reaping URB: No such device
 OK, response successfully read (13 bytes).
Resetting response endpoint 0x81
USB error: could not clear/halt ep 129: No such device
 Could not reset endpoint (probably harmless): -19
Resetting message endpoint 0x01
USB error: could not clear/halt ep 1: No such device
 Could not reset endpoint (probably harmless): -19
USB error: could not release intf 0: No such device
 Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 001
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 001
  searching devices, found USB ID 1d6b:0002
 Searching for target devices ...
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 024 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
  searching devices, found USB ID 109b:908a
   found matching vendor ID
   found matching product ID
   adding device
  searching devices, found USB ID 1d6b:0002

Found target device, now opening

Found target device 024 on bus 001

Target device description data
-------------------------
Manufacturer: Hisense Incorporated
     Product: Hisense HSUSB Device
  Serial No.: not provided
-------------------------
 Found correct target device

Mode switch succeeded. Bye.

root@android:/ #

Alex.C · Post by **Alex.C** » 13 May 2012, 14:54

dmesg

Code: Select all

<4>[44090.677557] sr0: scsi3-mmc drive: 0x/0x caddy
<7>[44090.683405] sr 20:0:0:0: Attached scsi CD-ROM sr0
<5>[44090.685175] sr 20:0:0:0: Attached scsi generic sg0 type 5
<6>[44225.780958] usb 1-1: USB disconnect, device number 22
<6>[44240.143976] usb 1-1: new high speed USB device number 23 using tegra-ehci
<6>[44240.187214] usb 1-1: New USB device found, idVendor=109b, idProduct=f009
<6>[44240.187751] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumbe
r=0
<6>[44240.188044] usb 1-1: Product: Hisense HSUSB Device
<6>[44240.188547] usb 1-1: Manufacturer: Hisense Incorporated
<6>[44240.198205] scsi21 : usb-storage 1-1:1.0
<5>[44241.197636] scsi 21:0:0:0: CD-ROM            eSurfing Mass storage     fff
f PQ: 0 ANSI: 2
<4>[44241.208677] sr0: scsi3-mmc drive: 0x/0x caddy
<7>[44241.217716] sr 21:0:0:0: Attached scsi CD-ROM sr0
<5>[44241.227538] sr 21:0:0:0: Attached scsi generic sg0 type 5
<4>[44301.132341] usb 1-1: usbfs: process 9797 (usb_modeswitch) did not claim in
terface 0 before use
<6>[44301.295726] usb 1-1: USB disconnect, device number 23
<6>[44303.473969] usb 1-1: new high speed USB device number 24 using tegra-ehci
<6>[44303.517209] usb 1-1: New USB device found, idVendor=109b, idProduct=908a
<6>[44303.517741] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumbe
r=0
<6>[44303.518248] usb 1-1: Product: Hisense HSUSB Device
<6>[44303.518533] usb 1-1: Manufacturer: Hisense Incorporated
<6>[44303.545125] scsi22 : usb-storage 1-1:1.4
<5>[44304.548234] scsi 22:0:0:0: CD-ROM            eSurfing Mass storage     fff
f PQ: 0 ANSI: 2
<4>[44304.561680] sr0: scsi3-mmc drive: 0x/0x caddy
<7>[44304.565338] sr 22:0:0:0: Attached scsi CD-ROM sr0
<5>[44304.581468] sr 22:0:0:0: Attached scsi generic sg0 type 5
<6>[44338.818839] ec battery percentage: 23

Post by **Josh** » 14 May 2012, 22:32

You have to do manually what the complete package of usb_modeswitch (on a full Linux system) will do automatically.

Tell the serial driver to bind to the (newly mode-switched) device:

Code: Select all

# modprobe -v option
# echo "109b 908a" > /sys/bus/usb-serial/drivers/option1/new_id

Note that the first command may fail if the "option" driver is built into the kernel, but then the path to the "new_id" attribute should already be in place.