UPDATE
Here is what I found on Google:
Uploading
BREW Applications to Handsets
How do I transfer compiled applications to the phone?
Applicable Releases: 1.0, 1.1, 2.0
Use
BREW AppLoader to upload applications to the phone. The following example shows files and locations for an application with the name "myapp."
/
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
All directory and file names on the phone must be in lower case. Any additional files specific to your application may also be copied to the application directory, or subdirectories of the application directory.
The Digital Signature file is generated using the
BREW TestSig Generator then renamed with the name of the application. The name of the .sig filename must be the same as the name of the .mod filename. The application directory name should be same as name of the MIF file.
In order to use a test-signature file on your handset, your handset must be test-enabled. This is done as a security measure. If a test signature is loaded on a handset that is not test-enabled,
BREW will remove the application from the handset. To get your handset test-enabled, please send it to the QIS Phone Center. For more information, please refer to Where should I send my phone when it needs to be re-flashed, or have DNS configured or test-bit enabled?.
After uploading files, reset the phone.
See How to Build a Downloadable
BREW Application for more details.
b. How do I upload the device configurator (.qsc) file to the phone?
Applicable Releases: 1.0, 1.1, 2.0
The device configurator file (.qsc) is used by the
BREW Emulator application, and is not required to run applications on the phone.
Full Link: Translated version of http://blog.vckbase.com/knight/archive/2007/06/13/3615.html 
Linear Mode
