Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
arnotixe
Posts: 5
Joined: 20 Apr 2009, 16:34

Getting the ZTE MF636 to work

Post by arnotixe » 20 Apr 2009, 22:12

Hi all

The telecom company Netcom in Norway gave me a ZTE MF636 to use for internet broadband.

The setup application crashed in windows XP SP3. I wasn't surprised that I had to manually install the drivers

Connecting the dongle it reports at first as 19d2:2000.
After installing the drivers it connects as 10d2:2000 then switches to 19d2:2031.

I USBsnooped the traffic to 19d2:2000 only, and the log is sitting in:
http://arno.homelinux.org/files/Usbsnoop-zteMF636.txt

Now, I tried to use usb_modeswitch -W with the parameters in URB7 in the above log file, and the device responds OK
But it doesn't switch to 19d2:2031...
I tried to send to endpoint 0x81, too, as it seems (to me) that windows is doing in URB9 of the snoop file above. Then it responds error -110.

Any suggestions?
Ubuntu 8.10

arnotixe
Posts: 5
Joined: 20 Apr 2009, 16:34

Re: Getting the ZTE MF636 to work

Post by arnotixe » 21 Apr 2009, 08:06

arnotixe wrote:Hi all


I USBsnooped the traffic to 19d2:2000 only, and the log is sitting in:
http://arno.homelinux.org/files/Usbsnoop-zteMF636.txt
Just adding a bit of detail here:
http://arno.homelinux.org/files/detaile ... tching.txt

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

Post by Josh » 21 Apr 2009, 22:52

I'm not able to access the files you provide. Is the server O.K.?

arnotixe
Posts: 5
Joined: 20 Apr 2009, 16:34

SOLVED (the switch part)

Post by arnotixe » 26 Apr 2009, 21:45

Josh wrote:I'm not able to access the files you provide. Is the server O.K.?
Well it's a home server. Not an exceptionally stable line. Works for me (now)...


Hi
Jerry(CC&C) wrote me a fix:

Code: Select all

usb_modeswitch -v 0x19d2 -p 0x2000 -V 0x19d2 -P 0x0031 -m 0x01 -M 55534243123456782000000080000c85010101180101010101000000000000
That is the preferred way, and adding it to udev it comes up automatically. I then execute wvdial on /dev/ttyUSB2 to connect to the ISP. Works great.

That should be included in the newer usb_modeswitch.conf files by default:

Code: Select all

########################################################
# ZTE MF636
#
# Even the manuals on the stick show up with this
#
# Contributor: Arno Teigseth (thanks Jerry)

;DefaultVendor=  0x19d2
;DefaultProduct= 0x2000

;TargetVendor=   0x19d2
;TargetProduct=  0x0031                  

;MessageEndpoint=0x01           
;MessageContent="55534243123456782000000080000c85010101180101010101000000000000"

You COULD as an alternative and just a bit faster way run the AT+ZCDRUN=8 command to the modem port in, say, windows (if the drivers install without problems). Then ZeroCD will be permanently disabled on that particular dongle, and you can use wvdial on /dev/ttyUSB3 to connect to the internet. To re-enable ZeroCD, AT+ZCDRUN=9. See also this ubuntu page.


Now, the only small problem I have left is that wvdial does not update the DNS info in /etc/resolv.conf, just in /etc/ppp/resolv.conf.

Anyone?

arnotixe
Posts: 5
Joined: 20 Apr 2009, 16:34

Re: SOLVED (the switch part)

Post by arnotixe » 12 Feb 2010, 09:51

arnotixe wrote: Now, the only small problem I have left is that wvdial does not update the DNS info in /etc/resolv.conf, just in /etc/ppp/resolv.conf.

Anyone?
Well if anyone ever runs into this: If you're using ubuntu, after you've got modeswitch right with the above command, networkmanager will try and set up the connection for you. Just select your local operator.

(I think I turned off SIM PIN check first, though. Just stick the ZTE SIM into a mobile phone and turn off sim security)

Post Reply