Activation Codes and Methods, Hardware Details, Sniffing
-
Jazb
- Posts: 5
- Joined: 01 Apr 2013, 05:31
Post
by Jazb » 01 Apr 2013, 05:58
I have a Axesstel MU130 trying to make it work on my MR-3040 router with OpenWRT but I can not change, so the information I have gathered with the sniffer attached below as well as my configuration files and MessageContent I've tried to see if I can help find the correct sniffing should be noted that I did from a virtual machine with windows xp
usb-modeswitch.conf
Code: Select all
DefaultVendor=0x1726
DefaultProduct=0xf00e
TargetVendor=0x1726
TargetProduct=0xa000
MessageEndpoint=0x01
MessageContent=""
CheckSuccess=20
I've tried MessageContent
- 1# 55534243985b04862400000080010612000000240000000000000000000000 ON 0x05
2# 55534243f008ef852400000080000612000000240000000000000000000000 ON 0x01
3# 5553424378f603860010000080000a28000000000000000200000000000000 ON 0x01
4# 55534243d8150c860000000000000600000000000000000000000000000000 ON 0x01
5# 55534243d8bc0a861200000080000c03000000120000000000000000000000 ON 0x01
6# 55534243003a06862400000080000612000000240000000000000000000000 ON 0x01
7# 55534243d8bc0a862400000080000612000000240000000000000000000000 ON 0x01
8# 55534243003a06860800000080000a25000000000000000000000000000000 ON 0x01
9# 55534243d8bc0a860000000000000600000000000000000000000000000000 ON 0x01
A# 5553424366f0ab872400000080000685000000240000000000000000000000 ON 0x01
B# 55534243d8bc0a860000000000000600000000000000000000000000000000 ON 0x01
lsusb -v -d 1726:f00e
Code: Select all
Bus 001 Device 015: ID 1726:f00e Axesstel, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1726 Axesstel, Inc.
idProduct 0xf00e
bcdDevice 0.00
iManufacturer 3 USB Modem
iProduct 2 USB Modem Device
iSerial 4 1234567890ABCDEF
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 Modem
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 6 SCSI
bInterfaceProtocol 80 Bulk-Only
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: 0x0000
(Bus Powered)
-
Attachments
-
- UsbSnoop_Logs.7z
- Logs fo Axesstel
- (93.28 KiB) Downloaded 450 times
-
Josh
- Site Admin
- Posts: 6570
- Joined: 03 Nov 2007, 00:30
Post
by Josh » 02 Apr 2013, 19:00
I would always try the standard "eject" sequence if nothing else seems to help:
5553424312345678000000000000061b000000020000000000000000000000
Don't set the endpoint manually. This is only for very special uses.
Just leave it away.
-
Jazb
- Posts: 5
- Joined: 01 Apr 2013, 05:31
Post
by Jazb » 03 May 2013, 00:21
Exactly this is the command, did not know that there was a default command sequence now usb_modeswitch -v 1726 -p f00e -V 1726 -P a000 -M 5553424312345678000000000000061b000000020000000000000000000000, but a shift perfectly in fedora testing before returning to the router, or networkmanager not detect it as a modem wvdial though the switching is done correctly .. lsusb when I check with both the product and the vendor are differnt and correspond to 1726: a000 may be due to this?
PS: This modem is my only form of connection and not very good to say not even in Windows if it is slow to respond Connection failures
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 03 May 2013, 12:53
post the lsusb info for the device after it has switched ( lsusb -vd 1726:a000) so we can see
what interfaces the device has.
-
Jazb
- Posts: 5
- Joined: 01 Apr 2013, 05:31
Post
by Jazb » 04 May 2013, 05:43
Log of lsusb
Code: Select all
Bus 002 Device 005: ID 1726:a000 Axesstel, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1726 Axesstel, Inc.
idProduct 0xa000
bcdDevice 0.00
iManufacturer 2 USB Modem
iProduct 1 Modem
iSerial 3 1234567890ABCDEF
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 131
bNumInterfaces 5
bConfigurationValue 1
iConfiguration 1 Modem
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 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 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 32
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 32
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 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
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 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 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: 0x0000
(Bus Powered)
Log Swtich
Code: Select all
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 003 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String: UsbModem
Model String: Storage Disk
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem Device
Serial No.: 1234567890ABCDEF
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.
attachment log of dmesg in file
-
Attachments
-
- log.txt
- (63.08 KiB) Downloaded 467 times
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 04 May 2013, 08:35
You need to install the openwrt kmod package which contains the usb_wwan driver and the option driver and then modprobe them, usb_wwan first and then option.
This will create ttyUSB0 - ttyUSB3 devices, something that is currently missing in your dmesg.
ttyUSB3 ought to be the modem.
-
Jazb
- Posts: 5
- Joined: 01 Apr 2013, 05:31
Post
by Jazb » 05 May 2013, 01:04
The dmesg log above is from the Fedora installation here include those of openwrt with all outputs and all loaded modules that possess the strange thing is that even makes the correct change, and that this modem does not assign any tty or ttyUSB* port, corresponding to each tty port seems to be one to communicate with the processor. When tested with a USB 3G Huawei and ZTE other friends both work perfectly the first time without much fight.
-
Attachments
-
- log.7z
- (5.1 KiB) Downloaded 422 times
-
LOM
- Posts: 1404
- Joined: 11 Jul 2012, 15:14
- Location: Koh Samui, TH
Post
by LOM » 05 May 2013, 01:30
Sorry, I forgot the important cmd you need to do:
echo "1726 a000" > /sys/bus/usb-serial/drivers/option1/new_id
The usb_wwan and option drivers need to be loaded before you make the cmd.
-
Jazb
- Posts: 5
- Joined: 01 Apr 2013, 05:31
Post
by Jazb » 09 May 2013, 20:52
Perfect with this script to work for me magnificent Fedora recognizes and connects without any inconvenience the only thing that would automate the process.
Code: Select all
#!/bin/sh
usb_modeswitch -v 1726 -p f00e -V 1726 -P a000 -M 5553424312345678000000000000061b000000020000000000000000000000
modprobe -v usb_wwan
modprobe -v option
echo '1726 a000' > /sys/bus/usb-serial/drivers/option1/new_id
and the same but with insmod equally in OpenWRT works perfect thank you very much because you achieve that work without any problem on linux and so I can say goodbye to Windows, the only thing that I wanted to automate the process to connect the device ... and certainly the modem is in the port /dev/ttyUSB3 .