Arti kedipan led merah dan Error JVM pada BlackBerry

Memahami kedipan led merah pada BlackBerry
Pada Smartphone BlackBerry led kanan atas atau lampu merah bisa mengimformasikan keadaan Handphone taubahnya separti signal morse signal ini menunjukkan keluhan yg dialami oleh Device
hal ini terjadi pada BB yg mati atau terjadi gangguan sehingga blink
ketrangannya begini, kita menggunakan angka 1 dan 0 sebagai isyaratnya
1 = lampu menyala
0 = lampu padam tidak menyala
contoh jika lampu meyala merah trus mati dan nyala merah lagi dan mati lagi dalam hitungan detik berarti di isyaratkan begini : 1010
ok jika anda sudah paham brikut adalah beberapa keterangan led merah:
 
1
Not a bootrom error: the OS is resetting during init! (device di wipe dl baru install OS)

11
No OS Loaded (pakai MFI atau di loader ulang baru install OS)

101
Bad OS CRC

111
Missing OS CRC

1011
Missing OS Trailer

1101
OS Not Signed

1111
OS Signature Invalid
(Gagal load os, solusinya cabut battery dari handset biarkan selama +/- 1jam lalu pasang kembali, langkah kedua coba wipe pakai JL_cmder lalu install os kembali. Kalau masih boot os error kemungkinan harus mengganti ic flash)

10101
Unknown Flash Manufacturer

10111
Flash Initialization Problem (ganti ic flash)

11011
Flash Erase Failure (ganti ic flash)

11101
Flash Operation Out Of Range

11111
Bad Bootrom CRC (ganti ic flash)

101011
USB Driver Error

101101
No Bootrom CRC

101111
Flash Write Failure (ganti ic flash)

110101
Invalid Memory Configuration Table

110111
Password Not Initiated

111011
RAM Initialization Problem (ganti ic flash)

111101
Cache No Pages Free

111111
Cache Invalid Page Type

1010101
Random Number Failure

1010111
OSStore Failure

1011011
Security Init Failure

1011101
NAND failure

1011111
General Assert Failure

1101011
GPIO failure

1101101
Runtime library failure

1101111
Exception: undefined isntruction

1110101
Exception: SWI

1110111
Exception: Prefetch Abor

1111011
Exception: Data Abort

1111101
Exception: Reserved

1111111
Exception: IRQ

10101011
Exception: FIQ


JVM Error Code

• 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     Internal JVM error.
• 108     Internal 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.
• 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.
• 501     Internal error.
• 502     All processes exited. The last Java process has terminated, and there is nothing left to execute.
• 503     Internal error.
• 504     Internal error.
• 505     Internal error.
• 506     An uncaught Java exception was thrown in the initial VM Java thread thus killing the only live thread in the system. The event log contains the traceback for the exception.
• 507     A dependency on a .cod file could not be satisfied due to a missing .cod file. Load the missing .cod file onto the handheld.
• 508     Invalid object. A problem has been detected with a debugger command to the VM.
• 516     Error occurred during garbage collection, which might indicate a corrupted file system.
• 510     All threads are waiting on objects, which results in a deadlock. The system cannot recover from this state since no thread can release a lock.
• 511     A problem has occurred during debugging.
• 515     The reachable objects form a group that cannot be represented properly by the VM because there are too many objects or the total size of the objects is too large.
• 516     When committing a persistent object, the VM found that the persistent store id counter has reached its limit. The object was not committed.
• 517     An inconsistency has been detected in the VM persistent object store.
• 518     Internal error.
• 519     Internal error.
• 520     Internal error.
• 521     Indicates that Object.wait() has been executed by a thread that holds a lock on another object; occurs only in simulator if the JvmDebugWaits application switch.
• 522     A thread has acquired two locks on objects in an order that doesn’t match the order that previous locks for the two types were acquired, which indicates a future potential deadlock situation; reported only in the simulator when the JvmDebugLocks application switch is set.
• 523     A critical Java process has died and the device cannot continue to operate normally.
• 524     An object has been marked as recovered by the Low Memory Manager but it was not freed during a garbage collection. This is only checked in the simulator under the control of the JvmDebugLMM application switch.
• 525     Bad persistent object. An auto-commit operation during a garbage collection has detected a non-persistent object reachable from the pers