Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
anoopjohn
Posts: 3
Joined: 23 Apr 2010, 23:01
Location: India
Contact:

HSPA WCDMA 3G Modem Provided by BSNL(19d2:2000)

Post by anoopjohn » 23 Apr 2010, 23:47

I came across a modem provided by BSNL that was not automatically switched by usb_modeswitch.

device id: 19d2:2000

target id: 19d2:0108

I had to add 0108 to the TargetProductId in /etc/usb_modeswitch.d/19d2\:2000 before I could get the device to switch. Also I ran into a problem in Ubuntu 9.10 where modem-modeswitch udev rule was conflicting with the usb_modeswitch preventing the modeswitch. I had to delete the corresponding udev rule of modem-modeswitch before I could get this to work. Also commenting the rule did not work. I have written out the instructions on configuring this specific device in Ubuntu 9.10. Here are the instructions for this.

Installing BSNL 3G USB modem in Ubuntu 9.10

Hope this helps somebody

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 24 Apr 2010, 00:01

There is a check in the wrapper script looking for that modem-modeswitch rule. There were conflicts in the past where only this rule seemed to work. So right now, usb_modeswitch does nothing if this rule is found, commented or not.

This whole 19d2:2000 business is weird. The "eject" method is suggested by the manufacturer, but in most cases doesn't work.

I'll remove that check in the wrapper or at least make it only give a warning and proceed.


anoopjohn
Posts: 3
Joined: 23 Apr 2010, 23:01
Location: India
Contact:

MessageContent also seems to be different for the device

Post by anoopjohn » 30 Jun 2010, 19:27

For the above mentioned device(19d2:2000) the MessageContent seems to be different as well. The message content given in the file /etc/usb_modeswitch.d/19d2\:2000 is

MessageContent="5553424312345678000000000000061b000000020000000000000000000000"

The working message content is

MessageContent="55534243123456782000000080000c85010101180101010101000000000000"

Also 0108 was still not in the TargetProductList. Is there some additional information that I have to provide before this can be added to the list. The device is the standard 3G device provided by the National Telecom carrier in India. So quite a lot of people would be looking and staring at this issue :-)

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 30 Jun 2010, 20:53

Sorry about that missing target ID ...

Would you be so kind and test some combinations? "NeedResponse" should always be set to 1:

1.
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
MessageContent2="55534243123456792000000080000c85010101180101010101000000000000"

2.
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"

2.
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"


anoopjohn
Posts: 3
Joined: 23 Apr 2010, 23:01
Location: India
Contact:

Will test and get back

Post by anoopjohn » 30 Jun 2010, 21:09

I am sorry but I have configured the system and the person has left happily with the working system. I will have to wait until somebody comes in again asking for help in setting up 3G :-). Will definitely do so then.

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 01 Jul 2010, 00:47

What a pity !

I just tried all of the variants I posted on my Nokia N810 which had problems switching my ZTE test stick at the first run only once.

They all worked well and reliably, but this may be a different firmware ...

If you encounter someone else with such a device, tie him/her down and run all kinds of cruel tests - on the modem, of course ...


Post Reply