vB Easy Archive - Need help with LG VX3300

Pages: 1

Need help with LG VX3300
(Click here to view the original thread with full colors/images)

Posted by: mikefromdel

I have purchased 2 data transfer cables from different vendors on e-bay for my Verizon VX3300. One is just a straight USB cable, the other is a USB cable with a small "box or blob" in the center of the cable. My computer, running Windows XP Pro with SP2, doesn't recognize the plug in. I've loaded the drivers, had the phone on, off, the cable plugged in before the drivers, after the drivers, after reboot....etc, etc, etc....no combination is recognized in my device managre. the only thing both cables are successful at is charging the phone.

As far as software, I have BitPim 8.0.8, also the latest version of DataPilot. Of course the software hasn't come in to play until the computer recognizes something........Anyone have any advice???

Here is the BitPim log I come up with:

16:06:15.233 coms:[{'available': True, 'driverdate': (2001, 7, 1), 'description': 'Communications Port (COM1)', 'driverprovider': 'Microsoft', 'driverversion': '5.1.2600.0', 'hardwareinstance': 'ACPI\\PNP0501\\1', 'driverdescription': 'Communications Port', 'active': True, 'class': 'serial', 'name': 'COM1'}, {'available': True, 'driverdate': (2004, 3, 5), 'description': 'Intel(R) 537EP V9x DF PCI Modem', 'driverprovider': 'Intel Corporation', 'driverversion': '2.15.36.0', 'hardwareinstance': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04\\4&1C660DD6&0&08F0', 'driverdescription': 'Intel(R) 537EP V9x DF PCI Modem', 'active': True, 'class': 'modem', 'name': 'COM3'}, {'available': False, 'driverdate': (2002, 10, 15), 'description': 'LG CDMA USB Modem Diagnostic Serial Port Drivers (WDM) (COM5)', 'driverprovider': 'LG Electronics Inc.', 'driverversion': '3.35.0.600', 'hardwareinstance': 'USB\\VID_1004&PID_6000&MI_02\\6&109718E1&0&1_02', 'driverdescription': 'LG CDMA USB Modem Diagnostic Serial Port Drivers (WDM)', 'active': False, 'class': 'serial', 'name': 'COM5'}]
16:06:15.233 Available ports: ['COM1', 'COM3']
16:06:15.233 Available modem ports: ['COM3']
16:06:16.203 Gathering data on port: COM3
16:06:16.203 COM3: Opening port COM3, 115200 baud, timeout 1.000000, hardwareflow 0, softwareflow 0
16:06:16.203 COM3: Open of comm port suceeded
16:06:16.250 Done on port: COM3
16:06:16.250 Checking for model: LG-C2000 (Cingular)
16:06:16.250 Likely ports:[]
16:06:16.250 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.250 Checking for model: LG-G4015 (AT&T)
16:06:16.250 Likely ports:[]
16:06:16.250 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.250 Checking for model: LG-LX5450 (Alltel)
16:06:16.280 Likely ports:[]
16:06:16.280 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.280 Checking for model: LG-PM225 (Sprint)
16:06:16.296 Likely ports:[]
16:06:16.296 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.296 Checking for model: LG-TM520
16:06:16.296 Checking for model: LG-VX10
16:06:16.296 Checking for model: LG-VX3200
16:06:16.296 Likely ports:[]
16:06:16.296 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.296 Checking for model: LG-VX4400
16:06:16.296 Likely ports:[]
16:06:16.296 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.296 Checking for model: LG-VX4500
16:06:16.296 Likely ports:[]
16:06:16.296 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.312 Checking for model: LG-VX4600 (Telus Mobility)
16:06:16.312 Likely ports:[]
16:06:16.312 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.312 Checking for model: LG-VX4650 (Verizon Wireless)
16:06:16.342 Likely ports:[]
16:06:16.342 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.342 Checking for model: LG-VX5200 (Verizon Wireless)
16:06:16.405 Likely ports:[]
16:06:16.405 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.405 Checking for model: LG-VX6000
16:06:16.405 Likely ports:[]
16:06:16.405 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.405 Checking for model: LG-VX6100
16:06:16.405 Likely ports:[]
16:06:16.405 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.405 Checking for model: LG-VX7000
16:06:16.421 Likely ports:[]
16:06:16.421 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.421 Checking for model: LG-VX8000 (Verizon Wireless)
16:06:16.421 Likely ports:[]
16:06:16.421 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.421 Checking for model: LG-VX8100 (Verizon Wireless)
16:06:16.437 Likely ports:[]
16:06:16.437 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.437 Checking for model: LG-VX9800 (Verizon Wireless)
16:06:16.437 Likely ports:[]
16:06:16.437 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.437 Checking for model: MM-7400
16:06:16.515 Checking for model: MM-8300
16:06:16.515 Checking for model: Other CDMA phone
16:06:16.515 Checking for model: PM-8200
16:06:16.515 Checking for model: RL-4920
16:06:16.515 Checking for model: RL-4930
16:06:16.530 Checking for model: SCH-A310
16:06:16.530 Likely ports:[]
16:06:16.530 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.530 Checking for model: SCH-A650
16:06:16.530 Likely ports:[]
16:06:16.530 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.530 Checking for model: SCH-A670
16:06:16.530 Likely ports:[]
16:06:16.546 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}
16:06:16.546 Checking for model: SCP-4900
16:06:16.546 Checking for model: SCP-5300
16:06:16.546 Checking for model: SCP-5400
16:06:16.546 Checking for model: SCP-5500
16:06:16.546 Checking for model: SCP-7200
16:06:16.546 Checking for model: SCP-7300
16:06:16.546 Checking for model: SCP-8100
16:06:16.546 Checking for model: SCP-8100 (Bell Mobility)
16:06:16.546 Checking for model: SK6100 (Pelephone)
16:06:16.562 Checking for model: SPH-A460
16:06:16.562 Checking for model: SPH-A620 (VGA1000)
16:06:16.562 Checking for model: SPH-A660 (VI660)
16:06:16.562 Checking for model: SPH-A740
16:06:16.562 Checking for model: SPH-A840
16:06:16.562 Checking for model: SPH-N200
16:06:16.562 Checking for model: SPH-N400
16:06:16.578 Checking for model: VI-2300
16:06:16.578 Checking for model: VM4050 (Sprint)
16:06:16.578 Likely ports:[]
16:06:16.578 Detect Phone result: {'COM3': {'mode_modem': True, 'mode_brew': False, 'firmwareresponse': None, 'esn': 'PCI\\VEN_8086&DEV_1080&SUBSYS_10001028&REV_04', 'model': '', 'firmware_version': '', 'manufacturer': ''}}

Any help would be appreciated............thanx

Posted by: cashorter

<ike did you ever get an answer on this. I am having the exact same issue.
Thanks!

Posted by: mikefromdel

never got any response about it at all......oh well

Posted by: zvonomir_2

I was curious about this also.

Posted by: adidas988

I guess the LG VX3300 is just boring.. I had high hopes trying so many combos trying to make it connect to my PC..

I was wondering where did you find the drivers for the VX3300, please help me out if you remember

thanks for your help!

Posted by: mikefromdel

I have the driver...e-mail me at mike_52697@yahoo.com and I will send driver to you. Total file is 2.82 Mb

Posted by: adidas988

thanks dude sent u a email

Posted by: mikefromdel

I can send you all the drivers I have, but, as i said in my first post....they did me no good....but I will send them if you like.........Mikefromdel

Posted by: adidas988

got the driver, thanks.. but I had no luck either..

Posted by: scifigirl

Sounds like I'm not the only one with this problem, has anyone found the answer for this?

Posted by: adidas988

nope.. I wasn't able to do anything to the phone & bitpim doesn't even have the 3300 on the LG list..

Posted by: ROWDYROB

Has Anyone Ever Had Any Luck With A 3300---or Is It Not Possible---anyone--thanks

Posted by: overridex

Thanks for the great insight, helped alot.

-------------------

Best Regards,

Overridex

Cell Phone

Cell Phone Plan

Free Cell Phone

Motorola Razr

Posted by: ABTX

You need two .sys files in order for the cable to work. One is serenum.sys and the other is usb2vcom.sys. If you can not get these files then email me and i will send them to you.

Posted by: mikefromdel

One is serenum.sys and the other is usb2vcom.sys....
Can you send me these files, I'd appreciate

mikefromdel

Posted by: adidas988

yes plz.. can u plz email me the files.. I would greatly appreciate it..

Posted by: ABTX

Email Address please?

Posted by: Glasuan

can someone please email me these files as well? glasuan@gmail.com

Posted by: toddv

A straight thru cable definitely doesn't work, the cable I have doesn't have a "blob" in the middle, there is a chip embedded in the USB plug which probably amounts to the same thing. The outfit I bought it from is constantly selling them on Ebay so if anyone is interested I can post the vendor. Funny, I thought it didn't work initially when I plugged it in because no new hardware was detected. Then I realized that the usb driver for my Nokia 2255i data cable (CA-42) was loading when I plugged it in. Works for me! Using the latest release of Bitpim, and setting the phone model to the VX3200, some of the functions work. The address book and call history does download, and I have access to the file system as well. This phone is very similiar to my Audiovox 8615 as far as the procedure for uploading wallpapers and ringtones, and is actually far easier than some of the convoluted explainations I've read on the web. I will post if anyone is interested. My vx3300 is on Virgin Mobile Canada, your mileage may vary. Cheers.

Posted by: adidas988

if you can try to post maybe like a step by step on the VX3300 would be great.. maybe just a direction on how to put ringtones on it..

Posted by: adidas988

bitpim doesn't even have the LG VX3300 on the drop down menu.. I don't understand why wouldn't it have that phone.. is it possible that it just doesn't work for ringtones..

Posted by: toddv

k .. here goes. Assuming you have successfully connected the phone to your pc and can read the file system with Bitpim. BACK UP THE FILE SYSTEM before attempting this or any other hack.

Background:
On this phone, user downloads are put in the /ams folder. Menu item 4 on the phone accesses data stored in this folder. The actual content (ringtones, wallpapers) are stored in .dat files, starting with 00.dat, 01.dat, and so on (not sure how high you can go). Additionally, there will be a corresponding .gcd file for each .dat file which describes the content in the .dat file ... so 00.gcd, 01.gcd and so on. These are simple text files. If you already have downloaded content you may see .url files ... 00.url, 01.url and so on. Finally, there are two system files ... realContent and contentInfo. Now, when I started looking at this phone, my daughter had already downloaded a couple of ringers, so there was already some .dat, .gcd, .url files as well as the realContent and contentInfo files. I don't know if the realContent and contentInfo files existed before she downloaded her first ringtone or were created as a result of the first download. Maybe someone trying this with a "fresh" phone can let us know if those files exist prior to any content loading. No matter, we will be overwriting them with blank files as part of the process.

I personally have loaded midi files (usually no more than 30 seconds or so) for ringtones and 128x128 jpg and gif images for wallpapers successfully.

1. create the .dat file by renaming your content file to xx.dat, where xx is the next available sequence number. For example, if there is already a 00.dat file, the next one in sequence would be 01.dat. Upload the .dat file to the /ams folder using Bitpim. Take note of the filesize in the Bitpim file listing window after it is uploaded.

2. create the .gcd file using a text editor. This will tell the phone what the content is.
...for a midi ringtone: (gcd file text is between the *s ... don't include the *s)
*
Content-Name: Name
Content-Version: 1.0
Content-Type: audio/midi
Content-Size: size
*

...for a wallpaper
*
Content-Type: image/type
Content-Name: Name
Content-Version: 1.0
Content-Size: size
*
type for images, would be jpg or gif, depending on what type of image it is.
Name is what will appear in the phone menu for the content. Assume there is a size limit for this but don't know what it is. I keep names as short as possible.
size is the size of the .dat file as it appears in bitpim.

Once the corresponding .gcd file is created, upload it to the /ams folder using Bitpim.

Notes: I mentioned the possibility of .url files being present. These appear to be created when content is downloaded over the wireless network. The gcd files for this type of content also includes extra fields. These are unnecessary. What I am describing is all that is necessary for content uploaded to the phone from your pc.

3. The contentInfo file needs to be overwritten (or created?) with a blank version. Create a blank text file named contentInfo on your pc and then upload it to the /ams folder, overwriting the existing contentInfo file if it exists. Remember, you should have backed up the entire file system before starting.

4. The existing realContent file need not be changed. If it doesn't exist, upload a blank version from your pc.

5. Exit Bitpim, disconnect your phone, and power it off, then on. Check menu item 4 on the phone for the new content.

The phone may take longer than normal to "boot". This is because the phone will scan the /ams folder and rebuild the contentInfo and realContent files including the new content in the process. This is why it is necessary to replace the contentInfo file with a blank version. If you don't, the new content will not appear in the phone menu.

so to summarize ...
1. create the .dat file with the next sequence number. Upload and note size
2. create the .gcd file to describe the .dat file. Upload.
3. Overwrite the contentInfo file with a blank version
4. Reboot the phone (power off, on)

Good Luck.

Posted by: toddv

Note: I mistyped the Nokia phone whose drivers worked with the vx3300 cable ... it was a Nokia 2125i. Thanks.

Posted by: toddv

Additional Info:

There is another "tag" you can add to the gcd file:

Content-Folder: foldername

This will organize the content into a subfolder under Menu item 4. The folder appears to be "virtual". So, it seems that if this tag is not used, images appear under "wallpapers", and audio files appear under "ringtones", but if you specify the folder using this tag, you can separate and organize your content under different virtual folders.