Google
 
Web www.howardforums.com
Pages: 1

Device no longer recognized as software modem

(Click here to view the original thread with full colors/images)

Posted by: prchandler

A couple of days ago I successfully installed the Motorola Software Modem driver and got my new V3m working with BitPim. When I plugged the phone into my PC yesterday, the "Install New Hardware" wizard started. My PC now recognizes my phone as a "Motorola V3c" rather than a "Motoraola Software Modem". As a result, any attempt to install the modem driver has been unsuccessful. Since I can't get the modem driver working, any attempt to communicate withthe device is futile.

The phone shows up in Device Manager under "Other Devices". I have attempted to get my PC to "forget" about the V3c by removing refrences to it from the registry. When I try, however, I am not allowed to delete or modify those keys - even when in Safe Mode.

Does anyone know what I can do to the Motorola Sotware Modem driver reassociated with my device?

Thanks


Posted by: JBDial

I am having the same issue. I was succesfully using the USB cable on my RAZR V3m to download/upload files via the Motorola Phone Tools and also SEEDS via P2k SEEM Editor as per http://www.howardforums.com/showthread.php?t=947130

While connected via USB Cable, I started the "Sync Music" feature on my RAZR V3m for the first time. I was immediately prompted with the Add New Hardware Wizard and I now am contiinually being prompted to "Add new hardware" "Motorola V3c" - BUT none of the drivers that worked before given in the above thread are recognized as what I need. I can no longer connect to the MPT either.

Any ideas why this happend , how I can fix this or where I can just go back to how it was? Thanks!


Posted by: prchandler

Now that you mention it - I did the same thing (Sync Music) right before my troubles started. It obviously has something to do with that, but I cannot figure out how to remedy it. I was able to successfully remove all references to "V3c" from the registry (which were USB device registrations), but they come right back when the device is attached again. The definition is apparently stored somewhere else. I'm guessing it is in with the Media Player stuff, but I have no idea about how to fix it. anyone have an idea?


Posted by: Mark_Venture

as posted elsewhere..
Quote:
Originally Posted by Mark_Venture
Its important to understand the phone has "different" modes... and each mode uses different drivers!! each gets listed in device manager differently too...

1. Modem mode (shows as Motorola Usb Modem in device manager, uses USBMOT2000.INF)... This is the DEFAULT Mode when you first turn the phone on. This is the mode BitPim and MPT want the phone in. This driver is what is installed by BVRP's Drivertool. BitPim and MPT will NOT see the phone if it is NOT in this mode, or using this driver!!

2. (V3M only) MTP Device (not sure how it shows in device manager, uses WPDMTP.INF as the driver)... This is the mode that allows Windows Media Player 10 to see/sync with the phone. When first entering this mode, Windows detects the phone as a Moto V3C when trying to install drivers.

3. P2K Device (when PST or MSU is running, etc.. uses P2K.INF/P2K.SYS), this is the mode you need the phone in when you want to do seem edits or use P2Kcommander.

BUT, in many cases, it takes disconnecting the phone from the PC, powering it off/on (or removing the battery) to get it back into the Moto USB modem mode...

NOTE: the drivertool... that basically clears stuff out, including registry entries about what driver files were being used for the phone, etc... drops a new copy of the USBMOT2000.INF driver on the PC... and gets windows ready to install the drivers needed to have your phone listed as Moto USB Modem (USBMOT2000.INF). The next time you plug your phone in after running the driver tool, windows will see it as "new hardware"...

NOTE: installing or upgrading MSU also clears out the registry entries for what drivers were used, etc for your phone, drops a DIFFERENT USBMOT2000.INF onto your PC, along with the P2K.INF/P2K.sys drivers. Again, after install or upgrade of MSU, windows will see your phone as "new hardware".


So, You might want to try unplugging the phone, turn it OFF, then back on.. or removing/re-inserting the battery.

You can also try the MTPFIX.EXE and alternate driver linked off ITEM #1a on the HOW TO's page at http://mark.cdmaforums.com


Posted by: prchandler

Boy do I feel stupid! Something as simple as turning the phone off and back on does indeed fix the problem. I'm back on track now using BitPim and doing SEEM edits. THanks for the help.




vBulletin Copyright ©2000 - 2008, Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2008 - Created by Stefan "Xenon" Kaeser