Verizon Q9c GPS Hack

[weinster666]

I was able to enter the sprint reg edits to allow com3 to be detected by GMaps. It seems the output from the gps back to gpsid.dll is being blocked. Still working on it. Anyone have luck getting the dll files from a Sprint phone?

Which registry settings exactly did you add and how were you able to verify that com3 is working as stated? Did you use the com3 activator from modaco also?

I just want to make sure my phone as at the same state as yours.

Thanks,

W666

[n55rc]

[HKLM\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer\]
String name="DriverInterface"
String value="COM3:"

[HKLM\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer\ActiveDevice\]
String name="DriverInterface"
String value="COM3:"
DWord name="Index"
DWord value="3"
String name="Prefix"
String value="COM"


[HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GenericGPSDriver\]
String name="CommPort"
String value="GDD0:"

[MarkG121087]

[HKLM\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer\]
String name="DriverInterface"
String value="COM3:"

[HKLM\System\CurrentControlSet\GPS Intermediate Driver\Multiplexer\ActiveDevice\]
String name="DriverInterface"
String value="COM3:"
DWord name="Index"
DWord value="3"
String name="Prefix"
String value="COM"


[HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GenericGPSDriver\]
String name="CommPort"
String value="GDD0:"

Thanks for the post, Im trying out these registry hacks now. I have a Verizon Q9c and I can find DriverInterface in the 2nd chunk of hacks. I just created a new file and I'm gonna see how that works.

[thebixcuit]

I have the gpsid.dll from a Sprint rom and is the same. This rom that I have people have been using to load on to their HTC's and using GPS.

I started going down several different paths in this problem. The Q9c does have the gpsOne (amazingly so does the regular Q). Getting in to this would require getting to the bootloader. All I can seem to find with that is people who have accidentally found themselves in it.

I ran a registry watch on the vz nav program and I saw that is accesses motgpsapi.dll. I haven't found this in the other roms.

Still digging....

[thebixcuit]

Exports of motgpsapi.dll...


Section contains the following exports for MOTGPSAPI.dll

00000000 characteristics
7DDDF593 time date stamp Sun Nov 30 17:52:03 2036
0.00 version
1 ordinal base
22 number of functions
22 number of names

ordinal hint RVA name

1 0 00005D68 oGPSCloseDevice
2 1 00006560 oGPSEnableSecurity
3 2 00006A8C oGPSGetBaseSSD
4 3 000061AC oGPSGetDeviceParam
5 4 000062CC oGPSGetDeviceState
6 5 000071E4 oGPSGetEnhancedTBFAlgorithm
7 6 00006FF4 oGPSGetFixDelay
8 7 00006BF0 oGPSGetIMSI
9 8 00006D20 oGPSGetLBSPrivacySetting
10 9 00005F2C oGPSGetPosition
11 A 00005AA8 oGPSOpenDevice
12 B 0000666C oGPSReadSecurityConfig
13 C 00006E24 oGPSResetAssist
14 D 0000607C oGPSSetDeviceParam
15 E 000070FC oGPSSetEnhancedTBFAlgorithm
16 F 00006F0C oGPSSetFixDelay
17 10 00006870 oGPSSetRandPeriod
18 11 000078A4 oGPSSetSMSPrefixAppInfo
19 12 00006954 oGPSSetShortCodes
20 13 00006770 oGPSWriteSecurityConfig
21 14 0000645C oGPSWriteServerConfig
22 15 000076FC oMOTLBSTestCode

[thebixcuit]

motgpsapi.dll is certainly the driver that vznav uses. In the DLL I found "oGPSSetSMSPrefixAppInfo Cannot create file \Windows\MT_SMS_Prefix.txt".

So I started VZNav and looked for this file. Magic.. There it is.
"//VZW-NAV00001 \Program Files\VZ Navigator\VZ Navigator.exe"

So VZNav definately has its own driver to use. Now back to figuring out how to use the GPSID API with the chipset

[thebixcuit]

LBSDriver.dll has the exports:

ordinal hint RVA name

1 0 00003790 GPSCloseDevice
2 1 000035E8 GPSGetDeviceParam
3 2 0000367C GPSGetDeviceState
4 3 00003700 GPSGetPosition
5 4 000034B4 GPSOpenDevice
6 5 00003554 GPSSetDeviceParam

and also contains references to the exports from motgpsapi.dll like oGPSSetSMSPrefixAppInfo.

[bugme~]

perhaps create a dll that replaces and uses a (renamed) VZNav's motogpsapi.dll?

[thebixcuit]

My thought is that the lbsdriver.dll replaces the gpsapi.dll since it has the same exports. Its much larger and accesses some cryptographic api's.

So my thoughts are either:
1. Make LBSDriver.dll get used for the GPSID API calls instead of gpsapi.dll and maybe that will make the calls to motgpsapi.dll which will access the hardware.

OR

2. Find the correct replacement for motgpsapi.dll so that there is access to the radio from a COM port with gpsapi.dll instead of API calls.

[bugme~]

check out this:
http://usa.autodesk.com/adsk/servlet...112&id=7783092