Steps to download BREW application | developer.brewmp.com Steps to download BREW application | developer.brewmp.com

Developer

Steps to download BREW application

Before you download application to Mototorola T720 or any other BREW phone

1. Make sure that your phone is in developer mode
Note: If your phone is not in developer mode, you copy any file in the phone using apploader, and then do power reset, the file will get deleted.

2. Once your phone is in developer mode, get BREW tools from BREW extranet website, and use Apploader to download application to your phone. Some people had difficulties in using USB connector to T720 phone, you may be better off using serial cable.

3. From BREW extranet, make sure that you generate sig file for your phone(based on hex code in your phone's battery pack compartment).
Note: sig file generated this way has around 90 days life-time.

4. Rename the sig file to xxx.sig (where xxx is your application name) and place it in the same folder where your .mod file is located.

5. Using apploader when you connect to your device, at the "\" (root level) place your xxx.mif file, create a folder named xxx, and in that folder place your xxx.mod and xxx.sig file.

6. Now reset your phone, in the BREW menu, go to ""get it now"" location (in T720 this is red symbol on the main screen), you should be seeing your application. In fact you can dump out trace on the logger.

ruben

"

Quote:Originally posted by ruben
5. Using apploader when you connect to your device, at the "\" (root level) place your xxx.mif file, create a folder named xxx, and in that folder place your xxx.mod and xxx.sig file.
ruben
I've recently discovered that you can place all the files (including the MIF) in the same directory and the apploader will place in them in the appropriate location when the files are uploaded.
Simply select Module->New... from the AppLoader menu. In the dialog that appears, select directory that contains your application files and enter the name of the application in the second field."

Quote:Originally posted by ruben
5. Using apploader when you connect to your device, at the "\" (root level) place your xxx.mif file, create a folder named xxx, and in that folder place your xxx.mod and xxx.sig file.
ruben
I've recently discovered that you can place all the files (including the MIF) in the same directory and the apploader will place in them in the appropriate location when the files are uploaded.
Simply select Module->New... from the AppLoader menu. In the dialog that appears, select directory that contains your application files and enter the name of the application in the second field."

Yes that would work but sometime I had some issues with certain preproduction version of the phone. Personally, I use perl script in conjunction with apploader dll to do all the task for me.
Thanks for pointing out that.
ruben

Yes that would work but sometime I had some issues with certain preproduction version of the phone. Personally, I use perl script in conjunction with apploader dll to do all the task for me.
Thanks for pointing out that.
ruben

Also see this FAQ item.

Also see this FAQ item.

How about the application load steps for LG VX6000? I followed your instructions and everytime I reset the phone, the new folder I created was lost. Does that mean I need to get my phone test-enabled?
Also, does it matter where I put the new folder in? When I created the new folder in "shared" folder, it didn't get deleted but I still can't access it from Get It Now.
So, all BREW applications are accessed from Get It Now menu on the handset?
Thank you.

How about the application load steps for LG VX6000? I followed your instructions and everytime I reset the phone, the new folder I created was lost. Does that mean I need to get my phone test-enabled?
Also, does it matter where I put the new folder in? When I created the new folder in "shared" folder, it didn't get deleted but I still can't access it from Get It Now.
So, all BREW applications are accessed from Get It Now menu on the handset?
Thank you.

yes, you need to test enable the phone.. when the app gets deleted upon restart is a sign of not being test enabled. the address new is here:
http://brewforums.qualcomm.com/showthread.php?s=&threadid=3898
The app needs to be loaded into the "root" directory.. .it was "/" but i think on the newer versions of the apploader it is under "brew/".. The place where you put it when the app got deleted is most likely the correct one (once you get the phone test enabled)
Yes, they are accessed from the get it now menu... unless you created a "hidden" app that cant be seen from the main app menu ("hidden" checked in the mif file)
-Tyndal

yes, you need to test enable the phone.. when the app gets deleted upon restart is a sign of not being test enabled. the address new is here:
http://brewforums.qualcomm.com/showthread.php?s=&threadid=3898
The app needs to be loaded into the "root" directory.. .it was "/" but i think on the newer versions of the apploader it is under "brew/".. The place where you put it when the app got deleted is most likely the correct one (once you get the phone test enabled)
Yes, they are accessed from the get it now menu... unless you created a "hidden" app that cant be seen from the main app menu ("hidden" checked in the mif file)
-Tyndal

Hi,
I can load the application into the phone and it's still in there when I reset it, and it showed up in GetGoing menu. I used RoadWarrior app. I got the mif, sig, mod into the phone. When I clicked on it, it displayed:
"Application digital signiture failure (1830)"
What could be wrong? I know sig may be the porblem. But I got another one from TestSigGenerator. It still didn't work.
Do I have to compile it using RealView Compilation Tools for BREW first, before I get a sig file and put everything in the phone? Or, can I just skip that step?
Also, my phone always display this message, "initial programming required", what does that mean? Will that affect the way that I load the application?
Thank you.

Hi,
I can load the application into the phone and it's still in there when I reset it, and it showed up in GetGoing menu. I used RoadWarrior app. I got the mif, sig, mod into the phone. When I clicked on it, it displayed:
"Application digital signiture failure (1830)"
What could be wrong? I know sig may be the porblem. But I got another one from TestSigGenerator. It still didn't work.
Do I have to compile it using RealView Compilation Tools for BREW first, before I get a sig file and put everything in the phone? Or, can I just skip that step?
Also, my phone always display this message, "initial programming required", what does that mean? Will that affect the way that I load the application?
Thank you.

i have followed the instructions in this thread and the related qualcomm FAQ topic.
i know my phone is testbit enabled because i've been able to load other applications onto the phone (and they are still visible in "get it now")
i have these files loaded:
/brew/myapp.mif - Generated by BREW MIF Editor
/brew/myapp/myapp.bar - Generated by BREW Resource Editor
/brew/myapp/myapp.mod - Compiled and linked with ARM Developer Suite
/brew/myapp/myapp.sig - Digital Signature
and my application is still not listed in "get it now"
what could my problem be? i'm not sure what i did differently this time! thanks in advance :D

i have followed the instructions in this thread and the related qualcomm FAQ topic.
i know my phone is testbit enabled because i've been able to load other applications onto the phone (and they are still visible in "get it now")
i have these files loaded:
/brew/myapp.mif - Generated by BREW MIF Editor
/brew/myapp/myapp.bar - Generated by BREW Resource Editor
/brew/myapp/myapp.mod - Compiled and linked with ARM Developer Suite
/brew/myapp/myapp.sig - Digital Signature
and my application is still not listed in "get it now"
what could my problem be? i'm not sure what i did differently this time! thanks in advance :D

Your mif file needs to be at the root level that is "/"
Get rid of "brew" folder in your path.

Your mif file needs to be at the root level that is "/"
Get rid of "brew" folder in your path.

oh, it is in the root, sorry about that (i'd just copied and pasted the directory structure from the qualcomm faq ;)
it should read:
/myapp.mif - Generated by BREW MIF Editor
/myapp/myapp.bar - Generated by BREW Resource Editor
/myapp/myapp.mod - Compiled and linked with ARM Developer Suite
/myapp/myapp.sig - Digital Signature
any other suggestions? it seems weird that just this applicaiton won't load! could it be something i set in the mif?

oh, it is in the root, sorry about that (i'd just copied and pasted the directory structure from the qualcomm faq ;)
it should read:
/myapp.mif - Generated by BREW MIF Editor
/myapp/myapp.bar - Generated by BREW Resource Editor
/myapp/myapp.mod - Compiled and linked with ARM Developer Suite
/myapp/myapp.sig - Digital Signature
any other suggestions? it seems weird that just this applicaiton won't load! could it be something i set in the mif?

What kind of error you get on the screen? Use BREW logger and DBGPRINTF function to see if your initialization function is failing or not. What is the RAM size in your target phone and what is your application binary size?

What kind of error you get on the screen? Use BREW logger and DBGPRINTF function to see if your initialization function is failing or not. What is the RAM size in your target phone and what is your application binary size?

the icon is not showing up in "get it now" so i'm unable to run the program at all.
i was using the 2.1 mif editor and that was the problem. when i switched to the 1.1 mif editor the icon showed in "get it now" and ran fine.
thanks for reading ruben :D

the icon is not showing up in "get it now" so i'm unable to run the program at all.
i was using the 2.1 mif editor and that was the problem. when i switched to the 1.1 mif editor the icon showed in "get it now" and ran fine.
thanks for reading ruben :D

Hi,
I'm trying to run the BREW sample applications, without any success.
I'm using a BREW 3.1.2 based MOTOROLA RAZR V3C. Here's what I did:
Launched Apploader and connected using COM4 & QCOMOEM. OK, it showed the file listing as 2 main folders,
- brew/mod
- brew/mif
and its NOT letting me create any folder at the root. After I select Module->New, it prompts for the application directory in which the .mod, .sig and .mif are present. Selecting the appropriate folder copies these files to the above 2 locations as expected (.mod and .sig in the brew/mod folder and .mif in brew/mif). After power cycling the device, I see the applications in the 'Get Going' section. The 'expensetracker' & 'roadwarrior' when clicked moves the selection to the top, while 'whiteboard' kind of resets the device. (hangs for some time and jumps to the start screen).
Any idea why this is happening??
Thanks!

Hi,
I'm trying to run the BREW sample applications, without any success.
I'm using a BREW 3.1.2 based MOTOROLA RAZR V3C. Here's what I did:
Launched Apploader and connected using COM4 & QCOMOEM. OK, it showed the file listing as 2 main folders,
- brew/mod
- brew/mif
and its NOT letting me create any folder at the root. After I select Module->New, it prompts for the application directory in which the .mod, .sig and .mif are present. Selecting the appropriate folder copies these files to the above 2 locations as expected (.mod and .sig in the brew/mod folder and .mif in brew/mif). After power cycling the device, I see the applications in the 'Get Going' section. The 'expensetracker' & 'roadwarrior' when clicked moves the selection to the top, while 'whiteboard' kind of resets the device. (hangs for some time and jumps to the start screen).
Any idea why this is happening??
Thanks!

Try connecting to Logger and looking to see if there are any error messages printed when you try to launch your application. Specifically, look for something like "#*g*C=%x:%d" where %x is your class ID and %d is the returned error code (refer to AEEError.h to determine its meaning).

Try connecting to Logger and looking to see if there are any error messages printed when you try to launch your application. Specifically, look for something like "#*g*C=%x:%d" where %x is your class ID and %d is the returned error code (refer to AEEError.h to determine its meaning).

I have created a test application that works well in the emulator and subsequently compiled it for ARM and I have created the equivalent test.mod file *.sig file (from the QCOM web site) and the test.mif file.
I have connected the V3M to the Apploader using a USB cable and I can create the test directory /brew/mod/test but I cannot copy any of the test.mod or test.sig files there.
The error reported from Apploader is a messagebox with the following:
Error - EFS2: Could not write to file.
The file system then shows the files in the right directory with a "0" filesize.
The V3M phone has already been sent to QCOM to enable test - but was returned with the message that V3Ms are test-enabled by default now (Comments?)....
Does anyone know what is being done wrong here?
Thanks.

I have created a test application that works well in the emulator and subsequently compiled it for ARM and I have created the equivalent test.mod file *.sig file (from the QCOM web site) and the test.mif file.
I have connected the V3M to the Apploader using a USB cable and I can create the test directory /brew/mod/test but I cannot copy any of the test.mod or test.sig files there.
The error reported from Apploader is a messagebox with the following:
Error - EFS2: Could not write to file.
The file system then shows the files in the right directory with a "0" filesize.
The V3M phone has already been sent to QCOM to enable test - but was returned with the message that V3Ms are test-enabled by default now (Comments?)....
Does anyone know what is being done wrong here?
Thanks.

Found the post about the patch required for Apploader.
http://brewforums.qualcomm.com/showthread.php?t=12555
Also, choose EFS1 instead of Autodetect in Apploader and then after that the download works.

Found the post about the patch required for Apploader.
http://brewforums.qualcomm.com/showthread.php?t=12555
Also, choose EFS1 instead of Autodetect in Apploader and then after that the download works.

i connect to my mobile with brew app loader, it has
/brew
/brew/en
/brew/netfront3
/brew/shared
then i uppload my app on it, it still there after i reset the mobile.
But i can see any thing like Brew App Manager
i also use BitPim to connect and see file & directory on the mobile, it's alse not avail there. What's problem here?
Where can i find a Brew manager App to upload on my mobile.
Pls help me and thank in advance

i connect to my mobile with brew app loader, it has
/brew
/brew/en
/brew/netfront3
/brew/shared
then i uppload my app on it, it still there after i reset the mobile.
But i can see any thing like Brew App Manager
i also use BitPim to connect and see file & directory on the mobile, it's alse not avail there. What's problem here?
Where can i find a Brew manager App to upload on my mobile.
Pls help me and thank in advance

Oh sorry, i forgot it, my mobile is Curitel HX575B CDMA 450Mhz

Oh sorry, i forgot it, my mobile is Curitel HX575B CDMA 450Mhz

GPSUser wrote:I have created a test application that works well in the emulator and subsequently compiled it for ARM and I have created the equivalent test.mod file *.sig file (from the QCOM web site) and the test.mif file.
I have connected the V3M to the Apploader using a USB cable and I can create the test directory /brew/mod/test but I cannot copy any of the test.mod or test.sig files there.
The error reported from Apploader is a messagebox with the following:
Error - EFS2: Could not write to file.
The file system then shows the files in the right directory with a "0" filesize.
The V3M phone has already been sent to QCOM to enable test - but was returned with the message that V3Ms are test-enabled by default now (Comments?)....
Does anyone know what is being done wrong here?
Thanks.
i'm facing the same problem.... any idea how solve this issue ?

GPSUser wrote:I have created a test application that works well in the emulator and subsequently compiled it for ARM and I have created the equivalent test.mod file *.sig file (from the QCOM web site) and the test.mif file.
I have connected the V3M to the Apploader using a USB cable and I can create the test directory /brew/mod/test but I cannot copy any of the test.mod or test.sig files there.
The error reported from Apploader is a messagebox with the following:
Error - EFS2: Could not write to file.
The file system then shows the files in the right directory with a "0" filesize.
The V3M phone has already been sent to QCOM to enable test - but was returned with the message that V3Ms are test-enabled by default now (Comments?)....
Does anyone know what is being done wrong here?
Thanks.
i'm facing the same problem.... any idea how solve this issue ?