Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

I'm having trouble connecting to BREW 3x Motorola handsets with AppLoader. I have all the latest files and patches (for fixing EFS bug and what not), but when I plug in the phone (such as the K1M and RAZR V3C) and run AppLoder, the com port has weird suffixes like COM16EM, COM16???, COM16|, and other weird characters after the initial COM_xx_).

Any suggestions?

Which Tool Suit you are using ?
For connecting to the devices above 3.x you have to use Qualcomm BREW Tools Suite 3.X.X.

Which Tool Suit you are using ?
For connecting to the devices above 3.x you have to use Qualcomm BREW Tools Suite 3.X.X.

I'm using BREW Tools Suite v3.1.0 (3.1.0.34 to be more specific), the latest available for download as of a month ago.

I'm using BREW Tools Suite v3.1.0 (3.1.0.34 to be more specific), the latest available for download as of a month ago.

I am also having this problem. I deleted all any Qualcomm and Motorola files off my computer including the registry. I reinstalled all files ( tried to connect with and without the patches ) and still have the issue. My computer recognizes the phone when it is plugged in but only as a modem but does not show up as a port separately. I get the correct port for that modem. When connecting the Apploader Very quickly says Error Could not detect any device with the specified ID. When it returns to the Apploader the Port is listed as COM15w. Any Ideas?

I am also having this problem. I deleted all any Qualcomm and Motorola files off my computer including the registry. I reinstalled all files ( tried to connect with and without the patches ) and still have the issue. My computer recognizes the phone when it is plugged in but only as a modem but does not show up as a port separately. I get the correct port for that modem. When connecting the Apploader Very quickly says Error Could not detect any device with the specified ID. When it returns to the Apploader the Port is listed as COM15w. Any Ideas?

Its a known issue, and the new BREW Tools Suite that fixes the issue will be out "real soon now".

Its a known issue, and the new BREW Tools Suite that fixes the issue will be out "real soon now".

I've had this problem too for a while now. The way I'm able to fix it is to use Motorola's driver installer tool (download at http://developer.motorola.com/docstools/USB_Drivers/)
After installing, run Motorola Driver Installer.exe and do the 'Clean' option. It will remove all Moto USB drivers and re-add them. AppLoader should work fine after that.

I've had this problem too for a while now. The way I'm able to fix it is to use Motorola's driver installer tool (download at http://developer.motorola.com/docstools/USB_Drivers/)
After installing, run Motorola Driver Installer.exe and do the 'Clean' option. It will remove all Moto USB drivers and re-add them. AppLoader should work fine after that.

The new BTIL and BREW Tools Suite were posted today. You might give that a shot if you're still having troubles.

The new BTIL and BREW Tools Suite were posted today. You might give that a shot if you're still having troubles.

I uninstalled the old suite (3.1.0) and installed the new one (3.1.1), which comes with the new btil version. Unfortunately, the problem still persists.
I even cleaned out the motorola drivers and re-installed it as jpage4500's post instructs.
After all that, I still get all these weird characters accompanying the port number (I get COM27Ô?Ô, COM27lM, COM27l?Ô, just to list a few), and connecting to these motorola handsets is still futile.

I uninstalled the old suite (3.1.0) and installed the new one (3.1.1), which comes with the new btil version. Unfortunately, the problem still persists.
I even cleaned out the motorola drivers and re-installed it as jpage4500's post instructs.
After all that, I still get all these weird characters accompanying the port number (I get COM27Ô?Ô, COM27lM, COM27l?Ô, just to list a few), and connecting to these motorola handsets is still futile.

one quick question, is it imperative that the tools suite and BTIL be installed in the their default folders (C:\Program Files\common...etc) ? Because I have them installed in a custom path.
acase1 if you're browsing this thread, did you deviate from the default location when you installed the tool suite and BTIL?

one quick question, is it imperative that the tools suite and BTIL be installed in the their default folders (C:\Program Files\common...etc) ? Because I have them installed in a custom path.
acase1 if you're browsing this thread, did you deviate from the default location when you installed the tool suite and BTIL?

I installed them all in the default locations.

I installed them all in the default locations.

You should be able to install BTIL anywhere. Check your BTILDIR environment variable to make sure its being pointed at the 1.0.2 install.
If that's the case, another 1.0.2 feature that may be of use to you is the fact that you can type in COM port names into the connection dialog (i.e. we've changed the drop-down boxes on the COM ports from un-edit-able to edit-able. Therefore even if the COM port name was mangled, you should be able to type in the unmanged version. If you can't edit the text of the COM port dropdown, then you probably are somehow pointed to the old BTIL version.

You should be able to install BTIL anywhere. Check your BTILDIR environment variable to make sure its being pointed at the 1.0.2 install.
If that's the case, another 1.0.2 feature that may be of use to you is the fact that you can type in COM port names into the connection dialog (i.e. we've changed the drop-down boxes on the COM ports from un-edit-able to edit-able. Therefore even if the COM port name was mangled, you should be able to type in the unmanged version. If you can't edit the text of the COM port dropdown, then you probably are somehow pointed to the old BTIL version.

toddb wrote:You should be able to install BTIL anywhere. Check your BTILDIR environment variable to make sure its being pointed at the 1.0.2 install.
If that's the case, another 1.0.2 feature that may be of use to you is the fact that you can type in COM port names into the connection dialog (i.e. we've changed the drop-down boxes on the COM ports from un-edit-able to edit-able. Therefore even if the COM port name was mangled, you should be able to type in the unmanged version. If you can't edit the text of the COM port dropdown, then you probably are somehow pointed to the old BTIL version.
Hmm, I did try that feature, typing in a unmangled port, but it doesn't solve the problem. Seems like problem is deeper than simply a cosmetic bug.
What's more perplexing is that this problem is not consistent. Sometimes if I'm lucky, I can connect to a Brew 3x motorola handset without running into the mangled port bug. I've tested with the V3C, V323, K1M, W385. I've never had any success with the V3C and K1M, but occasionally I can connect to the W385 and V323. I've tried to establish a pattern to this behavior but I can't.

toddb wrote:You should be able to install BTIL anywhere. Check your BTILDIR environment variable to make sure its being pointed at the 1.0.2 install.
If that's the case, another 1.0.2 feature that may be of use to you is the fact that you can type in COM port names into the connection dialog (i.e. we've changed the drop-down boxes on the COM ports from un-edit-able to edit-able. Therefore even if the COM port name was mangled, you should be able to type in the unmanged version. If you can't edit the text of the COM port dropdown, then you probably are somehow pointed to the old BTIL version.
Hmm, I did try that feature, typing in a unmangled port, but it doesn't solve the problem. Seems like problem is deeper than simply a cosmetic bug.
What's more perplexing is that this problem is not consistent. Sometimes if I'm lucky, I can connect to a Brew 3x motorola handset without running into the mangled port bug. I've tested with the V3C, V323, K1M, W385. I've never had any success with the V3C and K1M, but occasionally I can connect to the W385 and V323. I've tried to establish a pattern to this behavior but I can't.

We've got the V3M working here in the lab. Other than that, I'm grasping at straws as to why you might be having problems. Have you tried other PCs?

We've got the V3M working here in the lab. Other than that, I'm grasping at straws as to why you might be having problems. Have you tried other PCs?

I've also had the problem of mangled COM port names for a long time. Sometimes, I have to remove and re-install the phone's drivers. Sometimes, I've had to re-install the BTS suite. But, it's happening again - this time with an LG Chocolate and I can't connect! I was connecting just fine yesterday with the only difference being that I restarted my PC!
I saw this thread and upgraded to BTS3.1.1 but that isn't any better.
The phone is connected just fine to windows and has 2 COM ports - 1 under modems and another under COM (in device manager). But, in AppLoader I see both of these as corrupted strings (such as "COM14Looku" this time).
I can now manually type in COM14 but that doesn't help any.
Personally, I'd love to scrap Apploader altogether and use EFS Explorer - which is a lot more convenient and flexible. But, that stopped working for newer Brew devices so this is all I've got now.
EFS Explorer had a screen that detected all of the devices you had connected along with their ESN's (great for getting a test .sig file). You only had to click on the device to connect to it. Why is Apploader such a step back?

I've also had the problem of mangled COM port names for a long time. Sometimes, I have to remove and re-install the phone's drivers. Sometimes, I've had to re-install the BTS suite. But, it's happening again - this time with an LG Chocolate and I can't connect! I was connecting just fine yesterday with the only difference being that I restarted my PC!
I saw this thread and upgraded to BTS3.1.1 but that isn't any better.
The phone is connected just fine to windows and has 2 COM ports - 1 under modems and another under COM (in device manager). But, in AppLoader I see both of these as corrupted strings (such as "COM14Looku" this time).
I can now manually type in COM14 but that doesn't help any.
Personally, I'd love to scrap Apploader altogether and use EFS Explorer - which is a lot more convenient and flexible. But, that stopped working for newer Brew devices so this is all I've got now.
EFS Explorer had a screen that detected all of the devices you had connected along with their ESN's (great for getting a test .sig file). You only had to click on the device to connect to it. Why is Apploader such a step back?

, i seem to recall it happening before and the reason was that there were a lot of com ports in the system and i went through and cleaned up all the extra ones.
even though only 2 com ports show, there are 14 or so virtual ones.
I've actually got the same problem myself again so i''ll check and see if thats what it is.

, i seem to recall it happening before and the reason was that there were a lot of com ports in the system and i went through and cleaned up all the extra ones.
even though only 2 com ports show, there are 14 or so virtual ones.
I've actually got the same problem myself again so i''ll check and see if thats what it is.

add one to the motorola connection problem list

add one to the motorola connection problem list

Also having all the same issues. Has anyone heard of a fix for this?

Also having all the same issues. Has anyone heard of a fix for this?

on top of this, AppLoader now fatal errors each time i try to connect to the LG VX8500 (Chocolate)
I just uninstalled, and reinstalled the latest version of AppLoader also, same problem persists ... x_x

on top of this, AppLoader now fatal errors each time i try to connect to the LG VX8500 (Chocolate)
I just uninstalled, and reinstalled the latest version of AppLoader also, same problem persists ... x_x

If anybody else has the "mangled comport Apploader problem" here is a solution that worked for me.
It turns out a lot of my comports were "In use", in fact, like 15. I used the trick described here to fix of all of them, then I was able to use the same method to MOVE port 31 down to a lower port and AppLoader decided it liked it and finally let me connect.

If anybody else has the "mangled comport Apploader problem" here is a solution that worked for me.
It turns out a lot of my comports were "In use", in fact, like 15. I used the trick described here to fix of all of them, then I was able to use the same method to MOVE port 31 down to a lower port and AppLoader decided it liked it and finally let me connect.