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

Developer

Forums

Forums:

I have a device which is Motorola w385. I transfered apps via apploader successfully. but when trying to install BTIl on this device an error showing that

PC BTIl version is 1.0.06
Detecting BTIl on device
Couldn't connect to phone using BTIL
Attempting to connect with OEM layer
Connected to phone using OEMLayer, Checking for BTIl files on device
Btil not present on device
Select an appropriate image type to install..

i tried with all image types but an error btilmain.sig was not found is shown.
i dont know which is actual the actual device image Type.

any one plz help me .. i already tried with the patches of BTIL which is available at extranet.

BTIL is need on device because i want to transfer apps from TRIGBUILDER
Thanks

1.) Check your BTILDIR. It should be an 8.3 path pointing to the BTIL installation directory (usually C:\Program Files\Common Files\Qualcomm\BTIL Development Kit)
2.) I'm not sure how it wouldn't happen, but make sure there are btilmain.sig and btilsec.sig files in the $(BTILDIR)\Client\device\\. There should also be a mif and a mod in each of those directories. If you're still having problems, could you print out what's in your $(BTILDIR)\Client\devices directory?
I'm assuming #1 will fix the problem, but if not, we can take it from there.
I should mention, however that there is a problem currently where many OEMs don't support BTIL, and so even after installing the app it won't function. While this will be addressed shortly in the upcoming BTIL release, it remains a problem for now (and I personally don't know if the device you mentioned has support from the OEM or not). If you have what you know to be a perfectly valid test signature in BTIL's Test Signature Repository, and BTIL complains that the signature is "probably expired", then you have an unsupported device.

1.) Check your BTILDIR. It should be an 8.3 path pointing to the BTIL installation directory (usually C:\Program Files\Common Files\Qualcomm\BTIL Development Kit)
2.) I'm not sure how it wouldn't happen, but make sure there are btilmain.sig and btilsec.sig files in the $(BTILDIR)\Client\device\\. There should also be a mif and a mod in each of those directories. If you're still having problems, could you print out what's in your $(BTILDIR)\Client\devices directory?
I'm assuming #1 will fix the problem, but if not, we can take it from there.
I should mention, however that there is a problem currently where many OEMs don't support BTIL, and so even after installing the app it won't function. While this will be addressed shortly in the upcoming BTIL release, it remains a problem for now (and I personally don't know if the device you mentioned has support from the OEM or not). If you have what you know to be a perfectly valid test signature in BTIL's Test Signature Repository, and BTIL complains that the signature is "probably expired", then you have an unsupported device.