ZTE MF195 3G hack on Ubuntu 11.10

If you connect this modem to a machine running Ubuntu, it mounts and opens the virtual driver disk. If you unmount the partition, usb_modeswitch automatically kicks in and switches the device from CD-ROM emulation to modem mode. Unfortunately, Network Manager would not connect regardless of configuration. However, after some trial and error, wvdial was able to establish connection and start transferring data.

After reducing the unknowns, I've devised a small script which waits until the drive gets automatically mounted, unmounts the device, waits for settling and then establishes a connection with wvdial. This script was hooked up to a specific device addition udev rule to make it run automagically. As the devised udev rule did not narrow down the event good enough, actually two such invocations are done for each insertion, so a bit of an ugly hacking was involved to implement mutual exclusion.

Comments

  1. bkilMarch 20, 2012 at 8:49 PM

    The magic script is uploaded:

    http://code.google.com/p/bkil-open/source/browse/trunk/volatile/os/tmobile_mf195.sh

    ReplyDelete
  2. AnonymousMay 17, 2012 at 5:10 PM

    Could you please upload your /etc/wvdial.conf (striped from pin/passwords of course) as well? It would be very helpful!

    Thanks

    ReplyDelete
  3. bkilMay 19, 2012 at 9:10 PM

    @Anonymous: Well, actually that setup was not on my computer, but I can ask for the file from the guy that uses it. I remember that I've made minimal changes to the file - perhaps just the modem device and a standard HS init string was added.

    I myself use an MF637, and that is supported out of the box with network manager. After setting up a new connection for it in the GUI, it comes up in the interface dropdown in about half a minute from insertion without any trickery.

    Although, I do also use this on a different environment with wvdial occasionally, so I can also paste one of my own soon. Stay tuned.

    ReplyDelete
  4. bkilJune 20, 2012 at 9:45 AM

    Hm. Looks like it's taking more time than anticipated, as I've recently switched machines and don't have enough cables for the old one... What a pity. Will get back with wvdial.conf ASAP.

    ReplyDelete
  5. bkilDecember 4, 2012 at 7:58 PM

    I still couldn't grab wvdial.conf from the tested config, but we've encountered the very same issue on the same MF195 modem on KDE, and in this instance we used pretty much a default wvdial.conf and it worked like a charm. Again the modem device node, APN value and user/password is provider specific. PIN was disabled for testing.

    [Dialer Defaults]
    New PPPD = yes
    Phone = *99#
    Modem = /dev/ttyACM0
    Modem Type = USB Modem
    Baud = 460800
    ISDN = 0
    Username = web
    Password = web
    Init1 = ATZ
    Init2 = AT+CGDCONT=1,"IP","internet"
    Stupid mode = 1
    Auto DNS = 1

    ReplyDelete
  6. MartinMarch 21, 2013 at 8:38 AM

    Which driver is used to the MF195?

    ReplyDelete
  7. AnonymousMarch 21, 2013 at 7:44 PM

    Sorry, I don't have such a device to check, but I could ask when I meet one. We were basically using one of the built-in kernel modules, nothing custom needed. Did you check your USB ID on the net USB? Are you using an up to date distribution?

    ReplyDelete
  8. bkilJanuary 12, 2014 at 1:18 AM

    lsusb outputs the following when in modem mode:
    ID 19d2:1516 ZTE WCDMA Technologies MSM

    ReplyDelete
  9. bkilFebruary 15, 2014 at 12:53 PM

    The good news is that testing on live shows that the current Ubuntu can automatically handle the modem, so no hack is needed anymore.

    ReplyDelete
  10. bkilOctober 1, 2014 at 10:51 AM

    Good news: the modem works out of the box with network manager after upgrading to Ubuntu 14.04.

    ReplyDelete

Post a Comment

Popular posts from this blog

Hidden TFTP of TP-Link routers

I did some more investigation after the positive results with the TL-WR740Nv4  (click the link to get introduced to the way of recovery). Most users report that devices and firmware updates released after a point in time usually have this mode enabled. If a firmware update is available from the vendor for your device, it's a good idea to apply that update before installing OpenWRT or dd-wrt UNLESS you own something for which upgrading will ensure incompatible with OpenWrt, like a TL-WR730N , and possible some other models (please report). Note that some old models have newer updates in different languages, those may also be worth a try ( TODO : compatibility?). Also remember that later on, tftp recovery will need a type of firmware image without a boot loader, so strip it with dd if yours has it ( grep U-Boot , or check the filename). Positive reported claims so far (personal results highlighted): TL-WDR4300 router 192.168.0.86 server 192.168.0.66 query wdr4300v1_tp_...
Read more

Tftp secret of TL-WR740N uncovered

I've found out that even this particular entry level router supports anti-bricking, so there's no need for soldering, unless of course you are modding. The method I used is the following: Set up a tftp server  on your PC and verify if it works correctly (configuration, permissions, firewalls, etc.) Rename your target firmware to wr740v4_tp_recovery.bin and copy it to your base folder (by default /tftpboot). I tested with openwrt-ar71xx-generic-tl-wr740n-v4-squashfs-factory.bin r43602. Set up the following static IP for your PC: 192.168.0.66 /255.255.255.0. If you're not sure about the firmware name on a different model, start a packet sniffer on your PC ( tcpdump -i eth0 -n -l ) and look for the name in the RRQ message. Preferably disconnect WAN from the router Connect the PC to a LAN port Power off the router Press and hold the reset button Power on the router After the leftmost (power) LED and the rightmost (padlock) LED turn on alone in a few seconds, release...
Read more

When both Google *and* AppStatus is down

Here is a link where you could theoretically monitor Google outages: https://www.google.com/appsstatus#hl=en&v=status I had a problem with Google services just recently. However, as I wanted to verify whether the problem is on my side, this monitoring site was down as well. At the same time, the third party reports on alternative sites started to grow: http://outage.report/google http://downdetector.com/status/google http://aussieoutages.com/status/google This highlights why we should not put all our eggs into the same basket.
Read more