http://www.kaskus.co.id/showthread.php?t=1357725

Apa yang membedakan Blackberry dengan henpon lainnya ?

Henpon Blackberry melakukan koneksi internet dengan APN: blackberry.net, di mana setting ini builtin di henpon BB atau di software BlackBerry Connect… dan gak bisa dipake di henpon biasa dengan bermain setting APN seperti GPRS biasanya. Akses untuk APN blackberry.net inilah yang harus kita bayar per bulan ke operator sekitar 185rb - 200rb.

Sedangkan akses email / account email Blackberry itu gak ada hubungannya dengan pembayaran per bulan ke operator td. Account Blackberry bisa kita buat jika kita punya handset/henpon Blackberry. Dan aturan “umum”nya …. 1 henpon punya 1 account. Jadi hubungannya henpon-to-account … terserah mo pake operator apa pun.

Di setiap henpon Blackberry, kita musti tahu PIN dan IMEI dari si henpon. PIN di sini bukan PIN untuk nyalain henpon, tetapi lebih mirip IMEI kedua dari si henpon. PIN BB merupakan identitas henset BB, yang memungkinkan ngobrol PIN-to-PIN.

Nah untuk pembuatan account BB, kita tinggal masuk ke situs seperti:
- xl.blackberry.com
- telkomsel.blackberry.com
- indosat.blackberry.com

Sebenernya ini terserah aja mo pake yg mana, sama aja … krn itu ke server nya RIM. Hanya saja lebih baik ngikutin operator yang digunakan. Pada saat registrasi, nanti akan ditanyakan PIN dan IMEI dari henset BB milik kita. Nah, kl misalnya nanti ganti henset … musti masuk ke account ini dulu en pilih Change Device, en kita musti masukin PIN ama IMEI BB yang baru.
Kl gak, pemilik henset BB yang baru tidak bakal bisa daftar account ke Blackberry (RIM).

Untuk temen2 yg mo beli BB, persiapkan dulu kartu / SIM card yng udah siap BB servis.
Jadi pas beli henset BB baru, lsg dicoba untuk diregistrasi account BB, krn beberapa kasus yg aku alamin … banyak jg henset BB yang masih nggantung alias udah terdaftar ama orang lain. Kl kasus nya gini, urusan ribet … bisa dibilang ampir gak bisa “dibenerin” … kecuali kita minta pemilik account tsb utk ngelepas PIN BB nya.

Tp andaikata sempet ngalamin, coba deh lakukan hard reset dulu si BB … kadang BB nya msh rada o’on … cara hardresetnya: Options - Security Options - General Settings - (klik Menu) - Wipe Handheld. Kl emang msh nggantung, ya udah deh )

Proses testing henset BB:
1. Siapkan SIM Card yang sudah siap BB servis
2. Masukkan SIM card ke henset BB, nyalakan, dan lakukan proses registrasi servis BB
3. Jika perlu restart BB dulu ( ALT - CAP - DEL )
4. Perhatikan indikator tulisan GPRS / EDGE … dari hurup kecil (gprs), nanti berubah jadi hurup besar (GPRS). Ini menandakan servis BB dari operator sudah aktif.
5. Buka Options - Advanced Options - Host Routing Table
Harusnya ada beberapa baris tulisan di sana, kl masih kosong … klik Menu - Register Now
Tunggu sampe muncul beberapa baris di Host Routing Table
6. Buka web browser di PC, dan masuk ke situs BB
- xl.blackberry.com
- telkomsel.blackberry.com
- indosat.blackberry.com
Pilih sesuai operator SIM Card.
7. Buka di BB, Options - Status, catet PIN en IMEI
8. Register new account di situs BB dengan PIN en IMEI si henset.
9. Jika sukses, nanti tinggal setting email account aja di situs BB.
10. Setting Email cukup dari situs BB, gak perlu di henset lg.

sumber : Dicky Wahyu Purnomo

Berikut ada prosedur untuk mengupgrade Blackberry…

Syarat:
1. Windows XP
2. BlackBerry Desktop Manager versi 4.5/4.6/5/6 (saya pake yg 5 )

Prosedur:
1. Download installer OS Blackberry … cari dulu di internet …
2. Install file OS yang udah didownload (Jangan lupa matiin Desktop Manager dulu)
3. Buka direktori C:\Program Files\Common Files\Research In Motion\AppLoader
4. Hapus file Vendor.xml
5. Colok BlackBerry ke USB
6. Nyalain Desktop Manager
7. Klik AppLoader
8. Tinggal ikutin panduan untuk install OS …

Proses butuh sekitar 1 jam, paling lama saat proses Erasing Application (awal) ama Waiting for Device (terakhir) …

Note: Selama proses berlangsung, jangan dicabut Blackberry ama USB nya …
Kl terjadi kegagalan, tinggal diulangin aja koq proses nya …

Upgrade Blackberry relatif aman, selama ini selalu bisa diperbaiki dengan re-install dengan proses ini.

List dari kode error yang bisa saja terjadi di Java Virtual Machine (JVM) BlackBerry anda:

* 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 persistent store root. The type of the object has been output into the event log.
* 526 The class definition for java.lang.Object cannot be found.
* 527 The class definition for java.lang.String cannot be found.
* 528 The file system is corrupted. Data on the handheld is unrecoverable.
* 529 The file system is corrupted. An attempt is going to be made to recover data, but some data might be lost.
* 530 Internal JVM error.
* 531 Flash memory has been exhausted.
* 532 A JVM assertion has been violated. This error can occur only in the simulator, not on an actual handheld.