Blackberry Clinic

OTA download files from your computer

OTA downloading a file, usually done directly with the blackberry, but what if you want to download OTA files, but when you do browsing using the PC / Notebook?

This actually is very easy if you are browsing using Mozilla, because Mozilla addon already available to "download OTA files"

ota you want to download files directly from your notebook?

please let Mozilla addon download below and install on your Mozilla browser

for mozila

https://addons.mozilla.org/en-US/firefox/addon/11119

for google chrome

https://chrome.google.com/extensions/detail/nkhgpliefpgnkmoeidcfchbbkmnpbmeh

Blackberry error 523 solutions

for those of you Blackberry users are upset because error523, caused by alt + THMN and there were crashes of a particular application.
This problem is often found in some people using blackberries Jave.

The solution is quite complicated, because backup data is difficult, even I could not.
Because hangs directly connect with DM.

The solution is the wrong one: Blackberry reinstall the firmware. but data can not be backup. (Wipe then reinstall)
-. Disconnect the battery Blackberry
-. Plug into your PC / laptop to writing device connected to Unknown
-. Next and run the next step.

hopefully help

Blackberry Apps Error Code 400 to 499

today I will continue concerning the apps error that you often find on your blackberry, many people who already know about this, but more people who do not know.

I will not let a lot of pushes, just go to the point that is about the "blackberry apps error code" between 400 to 499

to erorr code rate is not much just some code only, not as in the previous code error

-400-564 Breaking lines, sistem data link lost, possibility of bad sector in hard drive
-410 Radio Failure
-411 Battery Error, Replace Internal or External Battery module
- 499 Software problems, continue to handheld device OS installation or application updates via Apploader

thanks

tomorrow I will continue to find other errors., may be useful for you

Blackberry Apps Error Code 3xx

blacberry continue my post about the apps error code 1xx and error code 2xx
-310-314 Hardware failure
Perform a hard reset on the handheld: Shut down, remove the battery wait a few second... replace battery then see when happens when it starts.
OR
Run Application Loader to reload the operating system and applications onto the handheld.
Note: If these tasks do not resolve the error, contact your service provider.

-320-325 AMX failure
Run Application Loader to reload the operating system and applications onto the handheld.

.

-330-339 Application tasks failure
Run Application Loader to reload the operating system and applications onto the handheld.

.

-340-343 Memory failure
You receive one the following error messages on your handheld:
Device Error 340 - 343

Cause
Memory failure

Resolution
Reduce the number of calendar appointments synchronized to your handheld.
1-In BlackBerry? Desktop Manager, double-click the Intellisync icon.
Click Configure PIM. The Handheld Configuration window appears.
2-In the Handheld Applications list, select Calendar.
3-Click Configure > Advanced Settings. The Advanced Settings for Calendar window appears.
4-In the Date Range tab, perform one of the following tasks to reduce the number of calendar appointments synchronized to your handheld:
If you click the Transfer only Future items option, only future calendar appointments will be synchronzied to your handheld.
If you click the Transfer items within a range of Days option and enter date range in the fields provided, only the calendar appointments that scheduled within the date range will be synchronized to your handheld.
5-Click OK to save your changes and close the window.
7-In the Handheld Configuration window, ensure that the check box beside the Calendar application is selected, then click OK.
8-In the Intellisync window, ensure that the Synchronize PIM check box is selected, then click Synchronize Now. The number of calendar entries on your handheld is reduced.
If you still receive the error

Run Application Loader to reload the operating system and applications onto your handheld..

- 350-359 Software application failure
You receive one of the following error messages on your handheld:
Device Error 350, 352, 353, 354, 355, 356, 357, 358, 359

Cause
Software application failure.

-Resolution
Perform a hard reset on the handheld.
OR
Run Application Loader to reload the operating system and applications onto your handheld. In the Application Loader Wizard window, do not select any third party applications. In the Advanced options, select the Erase all currently installed applications check box

360-363 Flash memory failure
Run Application Loader to reload the operating system and applications onto the handheld.

365-368 This one is often followed by
Contact your service provider.

Blackberry Apps Error Code 200 to 203

-200 Application manager threw an uncaught exception. The application manager event thread threw an uncaught exception and so cannot continue running.

-201 Initialization of the cryptographic system failed and the handheld cannot continue to operate

-202 An attack on the key store has been detected, and the handheld cannot continue to operate

-203 The application manager console process, usually the Home screen ribbon, has failed, like due to an uncaught exception.

list all the apps error for the Blackberry series

below is a description of error codes, which are often found in blackberries

Blackberry Apps Error code, between 101 to 110
-101 Internal JVM error.

-102 Invalid code in file system. The .cod files in the handheld have been checked for modification and it has been determined that there is a problem with one or more .cod files.

-103 The starting address for the boot .cod file cannot be found. This might mean that a boot .cod file has not been installed on the handheld, or that its format is invalid or corrupt

-104 An uncaught Java exception was thrown in the Java code and diagnosed by the JVM. Execution can be continued or the handheld can be attached to a debugger on a desktop through a serial or USB cable. The event log should contain the traceback of the thrown exception.

-105 An OS file system API returned an error status for a certain operation. This can indicate a corrupt file system or an error in the JVM.

-106 An error has been detected in the graphics system of the handheld.

-107 - 108Internal JVM error.

-109 Internal OS error.

-110 Non-idle event downtime error. A problem has been detected in the accumulation of JVM down time that represents how long the JVM has been idle. This indicates an error in either the OS code or the JVM code.

to find other errors that I will share the other day