How to Unlock the LG Rumor Touch - VM510 from Virgin Mobile (possibly others)

[Crogon]

bobbyj - That is commonly known as 'Tethering' your phone. I'm not sure if anyone on this forum is working on that or not, but I do know that some folks over on HowardForums are looking into it, you might want to check there. I told them they should come here to get more technical help, but I'm not sure if they ever did. good luck!

Everyone else - You are very welcome!

[Rodgman15]

After unlocking a Vm510 is it possible/recommended to update the firmware from pv5 to pv7 If anyone knows Or has any idea please let me know!

[texasboy]

i got com4 error message entering dm mode error what did i do wrong please help

[squealyhelium]

Hi new to this board as of today. I followed Crogon's steps and got the SPC entered and can now enter ##PORT# and ##DEBUG#. What I noticed reading the debug menu is that the bluetooth chip is a BCM 2070 and it is limited to these profiles only: HSP/HFP/OPP/A2DP/AVRCP/PBAP/HID/MAP. So no DUN or FTP.

It also says that that the main chipset is a QSC6075T (Qualcomm Single Chipset). I looked on google and found out that the Sanyo Innuendo also uses this chipset.

My goal is to use the RT to tether. So is knowing what kind of chipset is has going to tell us anything about tethering? Will tethering be similar to the Innuendo - can the the Innuendo even do it?

[squealyhelium]

For those of us who are trying to determine why nobody (it seems) has been able to tether on the Rumor Touch (RT), let's be systematic.

I am trying to see whether people just haven't been able to get the proper configurations on the PC once the phone is in DM mode or if there are some more complicated reasons such as the phone itself.

1. We know that if you follow crogon's steps you can get the phone in DM mode. The phone can be seen in the device mananger with 3 ports: Serial, GPS and Modem. So obviously the drivers have been installed. The Modem com port can also be changed if needed.


2. If you query the modem it *seems* to be communicating with computer giving responses to commands. 3 of the "AT..." commands are not supported - this may or may not be important. The modem query log is in the next post:

Now I have questions:

3. Are other VMO phones able to tether by using the "Dial-up connection" in windows? If so what are the username password and dialing number? If this works with other vmo phones does it NOT work with the RT?

4. Has anyone used QPST (I am using 2.7 build 3.55) to change the tethered NAI to be the same as the normal NAI? I have done this and it makes no difference.

5. are there 3rd party software programs that can tried given that the modem can be seen by the computer?

I feel that we are close and would it would be terrible if the way to tether was not found now.

Can someone put up a log of a phone that can work as a modem for VM? From an layman point of view it sort of looks like the modem is jus not dialing at all.

Basically the thrust of this attempt is to look ONLY at the computer side (except changing tethered NAI on the phone) to rule out something that would be easier than fiddling with the innards of the phone. Once it has been ruled out then it would make sense to look at the phone itself.

I wish this were more organized, but it is a bit beyond my technical ability. If this tethering is going to happen we need to be organized. Someone tell me what to do and test, I am willing to be a foot soldier in this fight! I can be able to put a few more hours into this part of the project.

P.S.

Below are two small programs that can monitor the network adapters and attached USB devices. This makes troubleshooting easier:

I wish this were more organized, but it is a bit beyond my technical ability. If this tethering is going to happen we need to be organized. Someone tell me what to do and test, I am willing to be a foot soldier in this fight! I can be able to put a few more hours into this part of the project.

P.S.

Below are two small programs that can monitor the network adapters and attached USB devices. This makes troubleshooting easier.

[Only registered and activated users can see links. ]
[Only registered and activated users can see links. ]

[squealyhelium]

This is what I got in from the device manager after running a query on the modem:

Model: +GMI: LG Electronics Inc.+GMM: Model:LG-VM510
Revision: +GMR: VM510PV7, 61006
ESN: +GSN: 0x80726BA9
+GCAP: +CIS707-A, CIS-856, +MS, +ES, +DS, +FCLASS
ATI6 - Manufacturer: +GMI: LG Electronics Inc.
Model: +GMI: LG Electronics Inc.+GMM: Model:LG-VM510
Revision: +GMR: VM510PV7, 61006
ESN: +GSN: 0x80726BA9
+GCAP: +CIS707-A, CIS-856, +MS, +ES, +DS, +FCLASS
ATI7 - Manufacturer: +GMI: LG Electronics Inc.
Model: +GMI: LG Electronics Inc.+GMM: Model:LG-VM510
Revision: +GMR: VM510PV7, 61006
ESN: +GSN: 0x80726BA9
+GCAP: +CIS707-A, CIS-856, +MS, +ES, +DS, +FCLASS
11-29-2010 01:26:00.500 - File: C:\Windows\system32\tapisrv.dll, Version 6.1.7600
11-29-2010 01:26:00.501 - File: C:\Windows\system32\unimdm.tsp, Version 6.1.7600
11-29-2010 01:26:00.501 - File: C:\Windows\system32\unimdmat.dll, Version 6.1.7600
11-29-2010 01:26:00.502 - File: C:\Windows\system32\uniplat.dll, Version 6.1.7600
11-29-2010 01:26:00.504 - File: C:\Windows\system32\drivers\modem.sys, Version 6.1.7600
11-29-2010 01:26:00.504 - File: C:\Windows\system32\modemui.dll, Version 6.1.7600
11-29-2010 01:26:00.505 - File: C:\Windows\system32\mdminst.dll, Version 6.1.7600
11-29-2010 01:26:00.506 - Modem type: LGE CDMA USB Modem
11-29-2010 01:26:00.506 - Modem inf path: oem64.inf
11-29-2010 01:26:00.506 - Modem inf section: LGSI.Install
11-29-2010 01:26:00.506 - Matching hardware ID: usb\vid_1004&pid_6000_modeminterface
11-29-2010 01:26:00.531 - Opening Modem
11-29-2010 01:26:00.531 - 460800,8,N,1, ctsfl=0, rtsctl=1
11-29-2010 01:26:00.548 - Initializing modem.
11-29-2010 01:26:00.548 - CTS is low while initializing modem.
11-29-2010 01:26:00.558 - Send: AT<cr>
11-29-2010 01:26:00.560 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.560 - Interpreted response: OK
11-29-2010 01:26:00.570 - Send: ATE0V1&D2&C1S0=0<cr>
11-29-2010 01:26:00.572 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.572 - Interpreted response: OK
11-29-2010 01:26:00.582 - Send: ATS7=60<cr>
11-29-2010 01:26:00.584 - TSP(0000): Making Call
11-29-2010 01:26:00.584 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.584 - Interpreted response: OK
11-29-2010 01:26:00.585 - Waiting for a call.
11-29-2010 01:26:00.598 - Send: ATS0=0<cr>
11-29-2010 01:26:00.600 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.600 - Interpreted response: OK
11-29-2010 01:26:00.600 - 460800,8,N,1, ctsfl=0, rtsctl=1
11-29-2010 01:26:00.617 - Initializing modem.
11-29-2010 01:26:00.617 - CTS is low while initializing modem.
11-29-2010 01:26:00.627 - Send: AT<cr>
11-29-2010 01:26:00.629 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.629 - Interpreted response: OK
11-29-2010 01:26:00.639 - Send: ATE0V1&D2&C1S0=0<cr>
11-29-2010 01:26:00.641 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.641 - Interpreted response: OK
11-29-2010 01:26:00.651 - Send: ATS7=60<cr>
11-29-2010 01:26:00.653 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.653 - Interpreted response: OK
11-29-2010 01:26:00.653 - Dialing.
11-29-2010 01:26:00.653 - TSP Completing Async Operation(0x00010259) Status 0x00000000
11-29-2010 01:26:00.653 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
11-29-2010 01:26:00.654 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
11-29-2010 01:26:00.663 - Send: ATDT####<cr>
11-29-2010 01:26:00.665 - Recv: <cr><lf>ERROR<cr><lf>
11-29-2010 01:26:00.665 - Interpreted response: Error
11-29-2010 01:26:00.665 - Hanging up the modem.
11-29-2010 01:26:00.675 - Send: ATHE1<cr>
11-29-2010 01:26:00.677 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.677 - Interpreted response: OK
11-29-2010 01:26:00.677 - 460800,8,N,1, ctsfl=0, rtsctl=1
11-29-2010 01:26:00.694 - Initializing modem.
11-29-2010 01:26:00.694 - CTS is low while initializing modem.
11-29-2010 01:26:00.704 - Send: AT<cr>
11-29-2010 01:26:00.706 - Command Echo
11-29-2010 01:26:00.707 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.707 - Interpreted response: OK
11-29-2010 01:26:00.717 - Send: ATE0V1&D2&C1S0=0<cr>
11-29-2010 01:26:00.719 - Command Echo
11-29-2010 01:26:00.720 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.720 - Interpreted response: OK
11-29-2010 01:26:00.730 - Send: ATS7=60<cr>
11-29-2010 01:26:00.732 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.732 - Interpreted response: OK
11-29-2010 01:26:00.732 - Waiting for a call.
11-29-2010 01:26:00.742 - Send: ATS0=0<cr>
11-29-2010 01:26:00.746 - Recv: <cr><lf>OK<cr><lf>
11-29-2010 01:26:00.746 - Interpreted response: OK
11-29-2010 01:26:00.746 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x4000)
11-29-2010 01:26:00.747 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
11-29-2010 01:26:00.773 - TSP(0000): Dropping Call
11-29-2010 01:26:00.773 - TSP Completing Async Operation(0x00010215) Status 0x00000000
11-29-2010 01:26:00.777 - TSP(0000): Closing Call
11-29-2010 01:26:00.780 - Session Statistics:
11-29-2010 01:26:00.780 - Reads : 44 bytes
11-29-2010 01:26:00.780 - Writes: 35 bytes