Automatic Activation, Hotplug and UDEV, Configuration
Post Reply
Ibod
Posts: 4
Joined: 22 Sep 2011, 10:43
Location: Kent, UK

Huawei U7510 + Ubuntu 9.10 install OK but won't switch

Post by Ibod » 22 Sep 2011, 11:50

Hi

I have a Huawei U7510 and Ubuntu 9.10.

USB_ModeSwitch installs OK but won't switch ??.
Thanks for any help to solve this.

I can see :-
The windows install device, as usual
I can not see :-
The phones internal file device
The memory card device
The modem in network manager

------------------------------------------------------------------------------------------------------------------------
I have version 1.1.4-1 and 20100826-1 installed with Synaptic, but this did not switch my device.
So I needed to update to a newer version.
I left the old version there because the "How to install" said "If you have a version after 1.1.0 you can just update and overwrite all existing files. "

I have installed version 1.1.9 and 2011-08-05 data, In accordance with How to install
I checked for tcl got the % prompt
I downloaded and extracted both packages and then
make install both packages, no errors as far as I could tell.

I looked in Synaptic to see if the package had updated, and to my surprise it was still 1.1.4-1 & 20100826-1.
Did a Reload, but synaptic still lists the old version

So I checked the version in the terminal

Code: Select all

$ usb_modeswitch -e

 * 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 !

$
This looked Ok, but still don't know why synaptic does not see the new version ?
As I was still not switching
I turned on logging in /etc/usb_modeswitch.conf as in troubleshooting

Code: Select all

 EnableLogging=1
Here are the three log files that appear
----------------------------------------------------------------------
1.) usb_modeswitch_ttyUSB1

Code: Select all

USB_ModeSwitch log from Thu Sep 22 10:32:32 BST 2011

* called with --symlink-name: params /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.1/ttyUSB1/tty/ttyUSB1 *

My name is ttyUSB1
My port is ttyUSB1, my interface is 1
 devDir:  /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6
 dev_top: 1-6
sysPath: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.1/ttyUSB1/tty/ttyUSB1
Checking my endpoints in /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.1
  in epDir /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.1/ep_83 ...
  in epDir /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.1/ep_02 ...

--> I am not an interrupt port

Return empty name and exit
------------------------------------------------------------------------
2.) usb_modeswitch_ttyUSB0

Code: Select all

USB_ModeSwitch log from Thu Sep 22 10:32:32 BST 2011

* called with --symlink-name: params /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/ttyUSB0/tty/ttyUSB0 *

My name is ttyUSB0
My port is ttyUSB0, my interface is 0
 devDir:  /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6
 dev_top: 1-6
sysPath: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/ttyUSB0/tty/ttyUSB0
Checking my endpoints in /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0
  in epDir /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/ep_81 ...
 /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6:1.0/ep_81 has interrupt transfer type

--> I am an interrupt port


--> No interrupt interface below me

Return symlink name "gsmmodem" and exit
------------------------------------------------------------------------
3.) usb_modeswitch_1-6:1.0

Code: Select all

USB_ModeSwitch log from Thu Sep 22 10:32:22 BST 2011

Raw args from udev: /1-6:1.0

Using global config file: /etc/usb_modeswitch.conf
Bus ID for device not given by udev.
 Trying to determine it from kernel name (1-6:1.0) ...
Warning: USB attribute "serial" not found.
----------------
USB values from sysfs:
  manufacturer	Huawei Technologies
  product	HUAWEI MOBILE
  serial	
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /etc/usb_modeswitch.d/12d1:101e
Using config file from override folder /etc/usb_modeswitch.d
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -c /etc/usb_modeswitch.d/12d1:101e)

Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are expected in the process)
--------------------------------
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002

Reading config file: /etc/usb_modeswitch.d/12d1:101e

 * 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=  0x12d1
DefaultProduct= 0x101e
TargetVendor=   not set
TargetProduct=  not set
TargetClass=    0xff
TargetProductList=""

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

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


Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
   adding device
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Found devices in default mode, class or configuration (1)
Accessing device 004 on bus 001 ...
Skipping the check for the current configuration
Using endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: Huawei Technologies
     Product: HUAWEI MOBILE
  Serial No.: not provided
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 004 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
 OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01

Checking for mode switch (max. 20 times, once per second) ...
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matchiusb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 001
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 005
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 005 on 001
skipped 6 class/vendor specific interface descriptors
skipped 5 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 002 on 002
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 002
ng vendor ID
   found matching product ID
   target class ff not matching
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001
 Searching for target devices ...
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 12d1:101e
   found matching vendor ID
   found matching product ID
   target class ff matching
   adding device
  searching devices, found USB ID 1d6b:0002
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 04a9:1093
  searching devices, found USB ID 1d6b:0001
  searching devices, found USB ID 0451:1446
  searching devices, found USB ID 1d6b:0001

Found target device, now opening

Found target device 005 on bus 001

Target device description data
-------------------------
Manufacturer: Huawei Technologies
     Product: Mobile Configuration
  Serial No.: not provided
-------------------------
 Found correct target device

Mode switch succeeded. Bye.

ok:12d1:101e
--------------------------------
(end of usb_modeswitch output)

Warning: USB attribute "serial" not found.
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1

Now checking for newly created serial devices ...
 new serial devices found, driver has bound
Checking for AVOID_RESET_QUIRK attribute
 AVOID_RESET_QUIRK not present

All done, exiting
Thanks Ibod
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 22 Sep 2011, 19:55

According to your logs, all went well. You should find a file (rather a symbolic link) called "gsmmodem" in the /dev directory after plugging your device (give it a moment). It points to the usable modem port. You can use it for connecting in all sorts of programs. Unfortunately, there is no manual override in Network Manager if it does not find the port automatically.

The sentence from the install Howto ("If you have a version after 1.1.0 you can just update and overwrite all existing files") refers to the package offered for download here, which is the original source. I'm doing no distribution packaging at all.

That said, there is no harm done when replacing the files from the Ubuntu package. You will have the files of the new version installed, only the package management does not know about this. If that bothers you, you can try to install the latest Debian package (1.1.9-2).

Top
Ibod
Posts: 4
Joined: 22 Sep 2011, 10:43
Location: Kent, UK

Post by Ibod » 22 Sep 2011, 22:42

Hi Josh,

Thanks for the help.
According to your logs, all went well. You should find a file (rather a symbolic link) called "gsmmodem" in the /dev directory after plugging your device (give it a moment). It points to the usable modem port. You can use it for connecting in all sorts of programs. Unfortunately, there is no manual override in Network Manager if it does not find the port automatically.
I found the symbolic link in /dev just as you said so I guess that bit worked fine.

Can you recommend any program that is likely to work with the sym-link rather than network manager ?
The sentence from the install Howto ("If you have a version after 1.1.0 you can just update and overwrite all existing files") refers to the package offered for download here, which is the original source. I'm doing no distribution packaging at all.

That said, there is no harm done when replacing the files from the Ubuntu package. You will have the files of the new version installed, only the package management does not know about this. If that bothers you, you can try to install the latest Debian package (1.1.9-2).
I am fine with synaptic not seeing the latest installed package, my only point for comment was in case it was causing a problem.

My only remaining problem is access to the files I have on the phones memory and SD card
usb-modeswitch is not switching out the windows driver device and giving me access to the internal memory and SD card

Do you know what is causing this ??
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 23 Sep 2011, 09:01

There may be more than one target mode as with other Huawei devices.

Try this: move the file "/etc/usb_modeswitch.d/12d1:101e" temporarily to annother location. Consequently, a different version of the Huawei switching message will be used (from "/usr/share/usb_modeswitch").

This may result in a different mode, although I can't predict if it includes storage interfaces.

As for the connection programs, some are listed in the paragraph "How to use" on the main doc page.

Top
Ibod
Posts: 4
Joined: 22 Sep 2011, 10:43
Location: Kent, UK

Post by Ibod » 23 Sep 2011, 11:21

Hi Josh,
Josh wrote:There may be more than one target mode as with other Huawei devices.

Try this: move the file "/etc/usb_modeswitch.d/12d1:101e" temporarily to annother location. Consequently, a different version of the Huawei switching message will be used (from "/usr/share/usb_modeswitch").

This may result in a different mode, although I can't predict if it includes storage interfaces.
Ok did that but there was no change, the sym-link to the modem is still their, but I still get the install windows drivers device, and not the internal memory device.

Any other thoughts ?

Thanks for your help :)
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 23 Sep 2011, 22:37

If you get the internal storage and the modem functionality with the Windows driver, then it might be worth sniffing what it does to the device exactly.

If not, then the device may behave like many other phones which need to be set up to provide either storage or modem.
Top
Ibod
Posts: 4
Joined: 22 Sep 2011, 10:43
Location: Kent, UK

Post by Ibod » 24 Sep 2011, 00:31

Hi
Josh wrote:If you get the internal storage and the modem functionality with the Windows driver, then it might be worth sniffing what it does to the device exactly.

If not, then the device may behave like many other phones which need to be set up to provide either storage or modem.
If I run win XP in a VBox and install the drivers then I get a screen pop up in windows asking if I
want [ File Transfer ] [ PC Assistant ] or [ Huawei Mobile Connect via the Phone ]

When I click on [ File Transfer ] option in the VBox XP the SD card device attaches in ubuntu and I can open the device in ubuntu !

I then have access to the SD card in ubuntu. The only problem is this PC is a bit old to run Windows VBox and Ubuntu, it all gets very slow

It looks like I am going to do a bit more work here to make this work properly.
Are there any good articles on how to do the sniffing ?

Thanks again for your help
Top
Josh
Site Admin
Posts: 6593
Joined: 03 Nov 2007, 00:30

Post by Josh » 25 Sep 2011, 20:34

For the very first steps and hints, see paragraph "Contribute" on the doc page.

If you get a prompt before the device is mode-switched in Windows, then you are in an ideal position!

The install mode of the stick should still be active at that time, so you will see it listed in SniffUSB's active devices list. You can install the sniffing filter in that very moment, start the sniffing and then answer the prompt. Your log should not become very long or complicated (from my point of view, that is) because the install mode device will soon cease to exist, and be replaced with the "target" mode device (modem or storage).

Hit "Refresh" repeatedly to see changes in the list of active devices and the log file size.

You will need to log twice at least, obviously.

Top
Post Reply

Return to “Setup Discussion”