Pages

2008-01-15

Unofficial DUN Tethering guide: LG Chocolate (vx8550) Hack

-- OR --
Adventures of a new mobile phone Pt. 3...



Editor's note: this particular article involves downloading and installing software from un-trusted web site. That's dangerous. It also involves running Windows. That's also dangerous. To top it all off, it also involves software that interacts with your mobile phone at a very low level. That, too, is dangerous. In short, HiR isn't responsible if you get in trouble with the law or your service provider, get a virus from a russian s3ri4lz site, get somehow addicted to running Windows, or brick your shiny new gadget.





Now for the fun stuff. One of the things I kind of relied on my Motorola e815 for was dial-up networking (DUN) via bluetooth. I didn't necessarily use it a lot, but as a sysadmin that's always been a bit of a road warrior, I often find myself places where there simply is no Internet. Inevitably, the pager-of-doom goes off and I'm out at the lake camping or at a location where there's no obvious Internet connection available. Other times, I'll be on a commuter bus and have the burning desire to check the news, or do some research on something really quick.

Whatever the reason, I enjoyed this functionality. On the e815, this was simple to enable. A quick punch-of-numbers on the keypad and voila. My MacBook could see it as a bluetooth modem with surprisingly quick download speed nonetheless -- at times upwards of 1mbit/sec.

The LG Chocolate? Different story. My MacBook saw it, but I wasn't getting anywhere. The connection would be refused with an invalid login and password, even though my login and password were fine when using my e815. This had me concerned.

I did a quick bit of research, and found that the phone has some internal IDs that differ when used for DUN. There's no quick handset-hack for this. Two things were required: A Data Cable, and the proprietary software from Qualcomm (called QPST) for changing the phone's settings. Even BitPIM wouldn't help me here.

All of the Windows operations were done within Parallels Desktop on a small Windows 2000 partition with all the latest patches. This isn't saying much, I don't know when the last patch was released for Windows 2000 but it's a lightweight operating system that can run the few Windows apps that I am ever tempted to launch.

The first order of business was to find the software. Unfortunately, the location where I got it seems to be offline, but you'll have to search for it. The specific file I found was a compressed installer for QPST 2.7 Build 231. Other builds might work fine. I'll caution you that a lot of sites that I found contained massive amounts of shady stuff, so do this at your own risk. I scanned the downloaded file for viruses before transferring it to my Win2K virtual machine. This is only available for Windows. Once downloaded, install it. It's a pretty straight-forward next-next-next installation.

Next, of course, was finding the data cable. I went ahead and purchased the Verizon Chocolate music accessory kit. It was a relative bargain at only $45. Along with the USB Data cable, I also got a special stereo 1/16" headset, a 2GB TransFlash card and adapters. The package also came with drivers for the USB connection as well as software for managing music on the phone. I obviously had no intention of using their Windows software just to copy files to my phone, but the driver was also Windows-only. I installed the USB driver, inserted the 2GB card into my phone, and went on my way with the rest of this hack.

Once the drivers are installed, the phone shows up on a high COM Port. Make sure the phone is plugged in and if running Parallels (versus doing this on a dedicated Windows machine) make sure that the USB Device is enabled for Parallels (Devices > USB menu) then open QPST Configuration and hit "Add Port". If all's well, you should see your phone in the dialog. Select and add it accordingly.





Once the port has been added, close QPST Configuration.

Next, open QPST's Service Programming tool. It should immediately prompt you to select your phone. Select it and continue. BEFORE YOU DO ANYTHING AT ALL, hit "Read from Phone", enter the SP code (usually 000000) and then save the data to a file. This will back-up your phone's configuration.


Now that that's out of the way, on the row of tabs across the top, scroll over until you find the M.IP tab. Expand the "NAI" and "Tethered NAI" columns so you can read them both clearly. You can see that Tethered NAI is not the same as NAI.


Edit Tethered NAI so that it matches.


Then, save this configuration to a different backup file. Don't over-write your pristine backup, please. Finally, get your phreak on and click the "Write to Phone" button and cross your fingers.

Quit the QPST Service Programming tool. Your phone should reboot and be completely intact.


From there, you set up your dial-up networking as usual. This is straight-forward in both Windows and Mac OS X.

Phone Number: #777
User Name: the tethered NAI you used above, ex: 1234567890@vzw3g.com
Password: vzw (but anything should work)

Now that you have the cable with a driver for Windows, you can do USB Serial or bluetooth on Windows.

Without a USB Driver on OS X you can still do Bluetooth DUN. If you configured your phone's Bluetooth connection with the "Access the internet with this phone's data connection" option checked, it should simply ask for a username and password.

8 comments:

  1. The other way you can try is using the service menu (Always write down or backup your settings);

    ##77647268550, SEND
    000000

    4. Data
    1. MIP Setting
    8. NAI Setting
    Change the Settings under
    2. SIP DUN NAI
    4. MIP DUN NAI
    They should match what is under
    1. SIP NAI
    3. MIP NAI

    ReplyDelete
  2. Holy crap! That's awesome!

    I was looking for a handset-only way to do this since my old e815 was that easy, but couldn't find anything.

    Thanks, man!

    ReplyDelete
  3. Any chance you know of a way to make this work on a BB Storm? I had it on my Voyager and loved it for when I went away on business conferences.

    ReplyDelete
  4. Given that LG and Blackberry are nothing alike at all, I'm pretty sure this walk-through won't help you at all. Some have gotten This to work on the Storm with VZW. Other than that, maybe try HowardForums. The Storm is pretty new, so it could take a while for someone to get this working 100%.

    ReplyDelete
  5. a few questions:

    - must this be done with a usb cable, or can it be done with bluetooth? I'm talking about the QPST 2.7 stuff, not the DUN itself.

    - could I use QPST 2.7 to back up my phone's data but then use the services menu to do the changes? in other words, combine both sets of instructions in this post?

    - could this trigger something on Verizon's end that might negatively affect my contract?

    ReplyDelete
  6. You might be able to. If you can get it to show up as a serial bluetooth port in Windows, you should be all set with QPST. I don't have a Windows machine with Bluetooth. I was using Win2K in a virtual machine (which can't access the Bluetooth adapter in the host machine)

    I think using BitPIM to back up your stuff and the service menu to activate DUN should work.

    And as far as VZW goes, you'll be breaking your terms of service. They could term your contract for this. I have the V-Cast plan, which gives your phone unlimited data -- IN THEORY. The reality is that v-cast videos and music are ultra-compressed and low quality. The downloads are small. If you go nuts with bandwidth while tethered, they might get suspicious. I'm sure they have a way to find out if you're tethering, but I can't prove it.

    I know people who stay tethered 8 hours a day, 5 days a week that have never caught any hell, though.

    ReplyDelete
  7. after going to the MIP tab, i see the user profile box, but it's empty, there are no entries. what do i do? i am using QPST 2.7 v215 and a lg chocolate vx8500

    ReplyDelete
  8. Damnit, my screen-shots died in a server migration. here's a screen shot of what mine looked like. Strange that there's not any entries in the M.IP tab, though.

    ReplyDelete