Sebenarnya fitur back up dan restore contact remotely sudah tertanam di BBM. Fitur ini mengenali contact pengguna berdasarkan alamat email yang didaftarkan. Tapi sepertinya masih ada yang belum mengaktifkan fitur ini. Padahal fiturnya akan sangat membantu, dan tak sulit mengaktifkannya.

Buka BBM, pilih Options, lalu pilih Back Up di sub-menu Contact List. Pilih “Back up file remotely”. (Gambar 01)

Akan muncul semua alamat email yang didaftarkan di BlackBerry. Klik salah satu, kemudian ikuti petunjuk yang diberikan. Kadang perlu juga untuk memeriksa di webmail apakah email konfirmasi dari BlackBerry masuk sebagai spam. Bila ya, tandai sebagai bukan spam dan ulang langkah di atas. Semakin banyak email yang didaftarkan semakin baik. Jangan lupa, email operator (xxx@operator.blackberry.com) biasanya lebih mudah untuk didaftarkan karena tidak memiliki inbox sehingga tak mungkin dikategorikan sebagai spam.

Hasilnya sebagai berikut. (Gambar 02)

Terlalu mudah? Biasanya setelah instal OS sebagai bagian upgrade, downgrade atau sekadar instal ulang, saya lebih memilih untuk restore contact remotely. Tidak ada bedanya, kecuali proses ini membutuhkan sinyal BIS yang bagus. Kalau tidak, hasil restore terutama BB group mungkin gagal. Tinggal minta invite ulang kan?

Software:
» BlackBerry DM (Desktop Manager) dan OS, link lokal di Antihackerlink.or.id.
» BlackBerry Swiss Army Knife (BBSAK) di bbsak.org.

1. Instal OS di komputer lalu restart.
2. Back up data via DM, simpan hasil back up di tempat yg aman dan jauh dari jangkauan anak-anak.
3. Hapus vendor.xml di folder C:\Program Files\Common Files\Research In Motion\AppLoader.
4. Jalankan BBSAK. Masukkan password bila ada.
5. Pilih tombol “Wipe OS”. Fungsinya utk menghapus (format) OS lama. Tunggu hingga BlackBerry reboot dan keluar “Error 507″. Artinya tidak ada OS.
6. Mulai instalasi. Bisa dng “Load OS” di BBSAK atau double click Loader.exe di folder AppLoader (langkah 3).
7. Ikuti wizard, check aplikasi/modul apa saja yg akan diinstal.
8. Proses instalasi akan berjalan. Tunggu hingga selesai dan BlackBerry reboot.
9. Selesai. Restore data dng DM.

Do with your own risk.

Catatan: cara ini tidak akan berhasil pada BlackBerry yang nuked.

101 Previous startup failed — The device was reset during the JVM boot process. The JVM found the boot in progress flag was set on startup. The screen is intended to break continuous reset loops so that corrective action can be taken.

102 Invalid code in filesystem — The system checked the COD files in the device for modification and determined that a problem exists with one or more COD files.
If all loads fail, a build process error might occur (a problem exists with signing the COD files).
If a user action on the device resulted in this problem, the reset cycle is continuous because the code in the filesystem has been corrupted. The only recovery method is to wipe the device and restore a new system.

103 Cannot find starting address — The starting address for the boot COD file cannot be found. This might indicate that a boot COD file has not been installed on the device or that its format is invalid or corrupt.

104 Uncaught: <Java-type-name> — An uncaught Java exception was thrown by the Java code and diagnosed by the JVM. Execution can continue, or the device can be attached to a debugger on a desktop computer. The Microsoft® Windows® Event Viewer log should contain the traceback of the thrown exception.

105 Example, DbRecSize( %d ) -> %d — The file system application programming interface (API) has returned an error status for a specific operation. This might indicate a corrupt filesystem or an error in the JVM.

106 Graphics system error — An error was detected in the graphics system on the device.

107 operator new() called — A C++ class in the JVM was coded incorrectly to inherit from VMRamObject that has the correct override for operator new. Extract the current (post-reset) BUGDISP.

108 operator delete() called — A C++ class in the JVM has was coded incorrectly to inherit from VMRamObject that has the correct override for operator delete. Extract the current (post-reset) BUGDISP.

109 PriorityMessageCount error: <priority-count> — The value returned by RimPriorityMessageCount is negative. It should always be greater than, or equal to, zero. This indicates an error in the operating system code. Extract the current (post-reset) BUGDISP and EVENTLOG.

110 Non-idle event downtime error: <down-time> <idle-down-time> — A problem was detected in the accumulation of JVM down time, which represents how long the JVM has been idle. This usually indicates an error in the device firmware or the JVM. This could also occur if the tick count rolls over after 400 or more days of device time.

111 Font engine error — An error was detected in the font engine system on the device. Extract the current (post-reset) BUGDISP and EVENTLOG.

112 Java Native Assertion Failure — An error was detected in the Java native code. Extract the current (post-reset) BUGDISP and EVENTLOG.

200 Application manager threw an uncaught exception — The application manager event thread threw an uncaught exception and cannot continue execution.

201 Crypto initialization code failed — The initialization of the crypto system failed and the device cannot continue execution.

202 An attack on the key store has been detected — An attack has been detected and execution cannot continue.

203 Console process died — The application manager console process (usually the Ribbon) has died. This is likely due to an uncaught exception during execution.

204 Persistent Content Exception — An application tried to commit a plaintext object to the Persistent Store. This will only happen if Content Protection is on and a process tries to save something in the PersistentStore that is marked as plaintext. Since this exception was not handled, the persistent store is in a bad state. You should reset to roll back to the last good commit point.

Note: This is not a JVM error; the JVM is simply diagnosing the problem. The eventlog contains information about the erroneous Java code.

501 VM_THREAD_SWITCHED: Internal Error — This is an error return used internally in the VM. It should never be reported as a device error.

502 VM_PROCESS_DEATH: All processes exited — The last Java process has terminated. There is nothing left to execute.

503 VM_THREAD_DEATH: Internal Error — This is an error return used internally in the VM. It should never be reported as a device error.

504 VM_THREAD_SWITCH: Internal Error —  This is an error return used internally in the VM. It should never be reported as a device error.

505 VM_BAD_CODE: Bad Byte Code — An error has occurred in the JIT compiler.

506 Uncaught Exception — An uncaught Java exception was thrown in the initial VM Java thread, thus ending the only live thread in the system. The eventlog contains the traceback for the exception.

507 Unsatisfied Link — A dependency on a COD file could not be satisfied because the COD file is missing.

508 Invalid object — A problem has been detected with a debugger command to the VM.

509 VM_PPO_INFINITE_LOOP: infinite loop in PPO phase of GC — The maximum iteration count for the PPO phase of a GC must be the maximum number of file handles in the system. This error indicates that the iteration count exceeds the maximum. Hence, a flaw exists in the PPO loop or a corrupted file system. The extra hex integer in the error string is the flash id of the current record where the infinite loop was detected.

510 Deadlock — All threads are waiting on objects, resulting in deadlock. The system cannot recover from this state because no thread can release a lock.

511 Debug connection died — A problem has occurred while debugging that may be caused by a VM problem or an incorrect debugging command being sent to the VM.

512 GC Aborted — An idle garbage collection has been interrupted by a user event (for instance, a key was pressed or the trackwheel was used).

513 <clinit> needs running — An opcode requires that a class execute before it can continue execution.

514 <init> needs running — A new instance of a class has been allocated and it must be initialized by the default constructor before it can be used.

515 Object group too big — The reachable objects form a group that cannot be represented properly by the JVM because either there are too many objects or the total size of the objects is too large.

516 Persistent ids exhausted — When committing a persistent object, the JVM found that the persistent store id counter reached its limit. The object was not committed and a critical error was reported. This error should not occur unless a device is heavily used for years.

517 Filesystem corrupt — An inconsistency was detected in the JVM persistent object store.

518 Unexpected longjmp — A garbage collection marking phase was terminated via a longjmp. This indicates that the marking phase was interrupted when it should have completed without interruption. This error should not occur because these actions are executed when the device is not idle, and GCs can only be interrupted when the device is idle.

519 Internal Error — The JVM host is missing or has been disabled.

520 Internal Return — This is an internal state that indicates a Java method return needs to be executed.

521 Dangerous Wait — An Object.wait() was executed by a thread that holds a lock on another object.

522 Interlaced synchronization — A thread acquired two locks on objects in an order that doesn’t match the order in which a lock on the two types were previously acquired. This indicates a future potential deadlock situation and is reported. The check is only available in the simulator under the control of the JvmDebugLocks application switch.

523 System process died — A critical Java process has terminated, and the device cannot continue to operate in a normal manner.

524 LMM error —  An object has been marked as recovered by the Low Memory Manager, but it was not freed during a garbage collection.

525 Bad persistent object — An auto-commit operation during a garbage collection detected a non-persistent object reachable from the persistent store root. The type of the object was output into the eventlog.

526 java.lang.Object not found — The class definition for java.lang.Object cannot be found.

527 java.lang.String not found — The class definition for java.lang.String cannot be found.

528 Corrupt filesystem. Unrecoverable. All data will be lost — All data will be lost when execution continues. The error message screen contains a number representing an internal reason for the corruption. This error is not diagnosed if a COD file was removed because the JVM must delete objects that were defined in the removed COD file. Thus, this error is not expected in normal device operation. Refer to the following reason codes:

1. Root array reference is not a valid array reference
2. Root array type is not Object[]
3. Root array size < 1 (i.e., Object[0])
4. Contents of root[0] is not a valid ref
5. Type of root[0] is not a LongIntHashtable
6. Persistent segmented array header contains an invalid reference
7. An entry in a persistent Object[] contains an invalid reference
8. An Object’s type refers to an unknown codfile
9. An Object’s type description in the codfile doesn’t match the size in the store
10. A reference type field in an Object has an invalid reference in it
11. A reference type field in an object points to an object of the wrong type
12. A persistent Object[] is missing its descriptor
13. Object in persistent store is not marked as persistable
14. Root array is segmented and one of the segments is invalid

529 Corrupt filesystem. About to attempt recovery. Some data may be lost — Some data will be lost when execution continues. The error message screen contains a number representing an internal reason for the corruption. This error is not diagnosed if a COD file WAS removed because the VM must delete objects that were defined in the removed COD file. Thus, this error is not expected in normal device operation. Refer to the following reason codes:

1. Root array reference is not a valid array reference
2. Root array type is not Object[]
3. Root array size < 1 (i.e., Object[0])
4. Contents of root[0] is not a valid ref
5. Type of root[0] is not a LongIntHashtable
6. Persistent segmented array header contains an invalid reference
7. An entry in a persistent Object[] contains an invalid reference
8. An Object’s type refers to an unknown codfile
9. An Object’s type description in the codfile doesn’t match the size in the store
10. A reference type field in an Object has an invalid reference in it
11. A reference type field in an object points to an object of the wrong type
12. A persistent Object[] is missing its descriptor
13. Object in persistent store is not marked as persistable
14. Root array is segmented and one of the segments is invalid

530 VM_PREVENT_GC_OVERFLOW: _preventGC overflow — A fixed number of native objects can be protected from garbage collection. This error indicates that a native has exceeded the fixed limit of objects that can be protected. If the device is reset or thread tracebacks are logged, the name of the actual native can be extracted.

531 Flash exhausted — There are certain operations where the JVM cannot withstand running out of flash space. In these circumstances, this error will be reported if the JVM cannot allocate a required amount of flash space.

532 VM_ASSERTION_FAILED: Assertion failed Normally this JVM error should not be reported since the device is not shipped with assertions enabled. The simulator may report this error in debug mode indicating a VM assertion was violated. Try typing BKPT to activate the debugger and dump the native call stack for forwarding to the VM team.

533 VM_RUN_METHOD:  <method> needs running — This is used internally for ECMAScript to call Java methods.

534 VM_FAST_RESET_DISABLED: Fast Reset Disabled — This is used internally to indicate that fast reset capability is not available. Often used in platform-specific code.

535 VM_UNUSED_535: Unused — This is an unused VM error.

536 VM_FAST_RESET_BAD_INSTANCE: VM Instance Check Failed — This is used internally to indicate that the VM structure passed in is at the wrong address or has been corrupted.

537 VM_FAST_RESET_BAD_HEAP: Heap Check Failed — This is used internally to indicate that the VM heap has been corrupted or pointers into the heap have been corrupted.

538 VM_FAST_RESET_BAD_IRAM: IRAM Check Failed — This is used internally to indicate that the VM IRAM checks have detected corruption of VM data structures (threads and local stacks) that reside in IRAM.

539 VM_FAST_RESET_NOT_IDLE: Not Idle — This is used internally to indicate that the VM was not idle when the reset occurred and, as such, cannot continue with a fast reset.

540 VM_FAST_RESET_MULTIPLE_RESETS: Multiple Resets — This is used internally to indicate that the time since the last fast reset is less than a minimum time. By disallowing multiple fast resets in a short amount of time, this should prevent fast reset loops.

541 VM_HEAP_COMPACT_INFINITE_LOOP: infinite loop detected in heap compaction — The VM detected a problem in its RAM heap that indicates its RAM was corrupted. The problem was detected by identifying a possible infinite loop during RAM heap compaction. A bugdisp log and eventlog should be extracted quickly when the device is in this condition. If possible, images of RAM should be saved.

542 Transient memory leak — The JVM detected that some memory was not freed, indicating that a memory leak has occurred. This condition is detected as early as possible to improve chances of isolating the cause.

543 VM_FS_MISMATCH: Incompatible Java filesystem installed — The VM detected that the operating system binary is different from the operating system binary used to create the Java file system. This means that the Java native methods may not be linked properly and as such, the integrity of the system cannot be guaranteed. The system can be recovered by using the VM DLFX and DLPS commands to delete the fixups and persistent store. This will clear all data and fixups and let the filesystem re-link to match the new operating system binary.

Note: The recovery order is:

1. Delete fixups
2. Delete persistent store
3. Reset device

544 VM_SECTION_MAP_OVERFLOW: a module references more than 255 other modules — The VM detected that a module is trying to reference more than 255 other modules. Extract the filesystem immediately when this error is detected.

545 VM_INCOMPATIBLE_FILESYS: an incompatible or corrupt filesystem was found — The VM detected an incompatible or corrupt filesystem. Extract the filesystem immediately when this error is detected.

546 VM_UNUSED_546: unused — The VM detected that the RAM image of its filesystem is corrupted (failed CRC check). Better to reset than to duplicate the corruption into flash.

547 VM_UNUSED_547: unused — This is an unused VM error.

548 VM_UNUSED_548: unused — This is an unused VM error.

549 VM_UNUSED_549: unused —  This is an unused VM error.

Sebenarnya masih ada beberapa error lain namun saya belum dapat menemukan referensinya. Contoh error 552: Reload Software yang biasanya disebabkan setelah instal aplikasi atau theme yang tidak cocok dengan spesifikasi BlackBerry yang digunakan. Solusi untuk error ini tentunya dengan menghapus aplikasi atau theme tersebut. Bisa juga dengan menggunakan BBSAK (BlackBerry Swiss Army Knife) menu Remove COD(s) dan mencari file cod dari aplikasi/theme itu. Namun bila sudah parah, terpaksa harus wipe kemudian instal ulang OS di handheld. Sambil berharap semoga BlackBerry tidak nuked.

Sumber: BlackBerry Developers Knowledge Base.

* * * * * * * * * *

Visi:
Membangun menyebarkan pemahaman tentang dunia internet dan komunikasi teks melalui perangkat BlackBerry.

Misi:
Menyebarkan pengetahuan tentang BlackBerry beserta layanannya dan pemanfaatannya dalam kehidupan sehari-hari. Menjembatani keluhan pengguna jasa layanan telekomunikasi XL untuk disampaikan ke provider XL.

Selayang Pandang
Komunitas ini awalnya merupakan sebuah bentuk kepedulian anak bangsa terhadap pengembangan penggunaan komunikasi teks terhadap masyarakat sehari-hari. Berawal dari owner milis (Heru Subiyantoro) yang aktif di beberapa komunitas BlackBerry Surabaya, maka pada tanggal 12 Februari 2009, dibentuk milis ini XLent Blackberry Community. Banyaknya ketidakmengertian beberapa pengguna BlackBerry terhadap gadget ini, menjadi pendorong khusus untuk lebih membantu pengguna untuk berdiskusi dan saling tukar pengetahuan tentang BlackBerry.

Dalam proses berdirinya milis komunitas ini mencoba berafiliasi dengan sebuah provider jasa telekomunikasi yaitu XL Axiata East Region yang berkantor pusat di Jalan Pemuda Surabaya. Kenapa kami pilih operator, karena kami menganggap bahwa operator (XL) merupakan pintu paling baik untuk berhubungan dengan visi dan misi kami. XL merupakan perusahaan jasa telekomunikasi yang berkembang pesat dengan user yang merata dari kalangan bawah sampai atas. Dengan persetujuan dan dukungan XL East Region kami diresmikan dengan acara seremonial 2 minggu setelah meluncurnya milis komunitas.

Nama XLent didapatkan atas proses konsultasi dengan XL East Region, karena ke depan milis ini diharapkan menjadi salah satu tumpuan XL untuk membantu pengguna BlackBerry terutama pengguna layanan XL. Milis ini sifatnya lebih ke layanan aktif, sehingga beberapa pengetahuan, berita, trick n tips, layanan XL, tentang BlackBerry akan selalu dikirimkan oleh moderator. Hal-hal berupa layanan keluhan terhadap layanan XL akan dijembatani untuk diteruskan ke pihak XL secara langsung. Sehingga milis ini menjembatani pengguna layanan XL dengan penyedia layanan jasa XL.

Keanggotaan
Milis Xlent Blackberry Community saat ini juga terus berkembang menjadi salah satu alternatif layanan jasa mediasi dengan pihak XL. Awalnya difokuskan untuk layanan XL East Region namun saat ini sudah mencakup wilayah nasional. Wilayah yang sudah terlayani keanggotaannya adalah Jawa (Timur, Tengah, Barat, Jakarta, Banten), Bali (Denpasar), Nusa Tenggara (Lombok), Irian Jaya, Sulawesi (Makasar, Ujung Pandang), Kalimantan, Sumatra (Medan, Palembang, Lampung). Dan saat ini wilayah keanggotaan terus berkembang secara pesat dengan subscriber lebih dari 10 setiap minggu.

Sifat keanggotaan bebas dengan cara melakukan subscribe ke milis, mengirim email kosong ke alamat xlent-bb-subscribe@yahoogroups.com menggunakan email akun selain operator. Jumlah keanggotaan hingga saat ini (Februari 2010) hampir mencapai 600 subcriber aktif.

Seputar Milis
Trafik email yang terjadi dalam 1 bulan sekitar 5000 email. Dengan jam kerja 24 jam dalam 7 hari seminggu. Dengan topik khusus berhubungan dengan Blackberry dan layanan XL. Member dapat melakukan diskusi, jual beli BlackBerry dan asesorisnya, keluhan layanan jaringan XL, info produk dan program XL.

Milis komunitas ini bekerjasama dan berafiliasi dengan penyedia jasa layanan telekomunikasi Exelcomindo East Region (XL). Kami sampai saat ini bukan perwakilan official dari provider XL Axiata.

Beberapa anak milis saat ini juga disediakan oleh milis induk. Milis anak tersebut antara lain XLent-chat yang merupakan media komunikasi selain BlackBerry, XLent-bbhybrids untuk mereka yang senang tukar info dan diskusi tentang proses hybrids.

Kegiatan
Kegiatan komunitas milis ini selain banyak berdiskusi di dunia maya, juga melakukan kegiatan rutin untuk workshop bersama member tentang pemeliharaan Blackberry, mini workshop Upgrade OS BlackBerry, bakti sosial, mini gathering (silaturahim).

* * * * * * * * * *

Selain milis juga ada grup di Facebook dengan nama yang sama: XLent BlackBerry Community. Salah satu hal unik yang menjadi aturan di milis adalah panggilan ‘Cak’ untuk lelaki dan “Ning’ untuk perempuan. Selain itu milis terbuka bagi pengguna layanan BlackBerry yang menggunakan operator selain XL. Asal tak lupa mengubah signature yang ada di ekor email. Dan menyambut ulang tahun pertama tanggal 12 Februari mendatang, di milis lagi ada sayembara sekalian saya ucapkan…

Selamat ulang tahun XLent! Semoga selalu XLent!

Sebenarnya ada aplikasi BlackBerry Swiss Army Knife (BBSAK, terakhir versi 1.7) yang bisa digunakan untuk proses back up dan restore aplikasi. Namun sewaktu proses restore ternyata harus dilakukan satu per satu alias tidak bisa sekaligus semua aplikasi dikembalikan. Hasil bertanya mbah Google ternyata proses ini bisa dilakukan cukup dengan BlackBerry Desktop Manager (DM).

Langkah-langkahnya sebagai berikut:

Sambungkan perangkat BlackBerry Anda dengan komputer melalui kabel USB. Jalankan DM dan masuk ke menu Device Switch Wizard.

Pada kolom sebelah kiri klik Start di bawah Switch BlackBerry devices.

Layar selanjutnya seperti terlihat pada gambar. Pastikan di kolom pilihan paling kanan hanya dicentang Third-party applications, klik Next.

Biarkan proses back up berjalan hingga selesai. Setelah muncul pemberitahuan Please connect your new device seperti ini diamkan saja. Tinggalkan DM dan jangan klik apapun.

Cari folder bernama PIN di folder Temp. Untuk pengguna Windows XP biasanya folder ini berada di C:\Documents and Settings\nama_user\Local Settings\Temp. Mudahnya ketik %temp% di kolom Address di Windows Explorer. Atau gunakan fasilitas Search untuk mencari file angkaPIN.alx lalu simpan semua file yang ada bersama file ini. Misal PINnya 12345678, cari folder 12345678 di Temp atau cari 12345678.alx dan simpan semua file yang ada di tempat yang sama dengan itu. Pindahkan (cut) folder 12345678 dan letakkan (paste) di tempat yang mudah terjangkau, misalnya My Documents.

Kembali ke DM dan klik Cancel. Lakukan ini setelah memindahkan folder tadi. Bila tidak maka harus mengulang proses back up mulai dari awal. Saat back up dengan cara ini jaringan akan otomatis OFF. Jangan lupa centang jaringan kembali.

Jalani proses instalasi; wipe, upgrade atau downgrade OS. Setelah selesai kembali buka DM dan pilih Application Loader. Klik Start pada Add/Remove Applications.

Masuk ke menu berikutnya, pilih Browse (kotak merah) dan arahkan pada 12345678.alx tadi. Akan muncul pilihan aplikasi, klik Next lagi.

Akan muncul aplikasi apa saja yang akan di-restore ke handheld, klik Next.

Konfirmasi sekali lagi bahwa aplikasi-aplikasi seperti yang tercantum yang akan di-restore ke handheld, klik Finish.

Setelah selesai, BlackBerry akan restart dan setelah itu mestinya aplikasi-aplikasi sudah kembali ke tempatnya.

Kini aplikasi sudah kembali ada di BlackBerry tanpa repot download dan instal ulang. Kompatibilitas aplikasi dapat berubah terutama bila aplikasi tersebut bukan diperuntukan OS yang digunakan. Ini hanya berbagi pengalaman dan saya tidak menanggung resiko terhadap apapun yang dilakukan. DWYOR. Do with your own risk. Tapi mestinya sih semua berjalan normal

Saya coba copot baterai, diamkan sejenak lalu pasang lagi ternyata hasilnya sama saja. Saya ulangi kembali sambil juga mencopot memory dan SIM card namun tetap tidak berhasil. Sampai di situ baru saya ambil kesimpulan bahwa GenTa (Gemini sang Taurus, panggilan manja BlackBerry saya) mati suri.

Cara untuk mengatasinya sebagai berikut:

Software yang diperlukan:
- BlackBerry Desktop Manager (saya menggunakan DM versi 5.0.1)
- OS yang ingin diinstal di BlackBerry

Langkah-langkahnya:
- jangan panik, sambil tak lupa berdoa
- instal OS di komputer kemudian restart komputer
- setelah restart, hapus file vendor.xml di folder C:\Program Files\Common Files\Research In Motion\AppLoader
- copot baterai
- sambungkan kabel USB ke komputer dan belum terhubung ke BlackBerry
- jalankan Loader.exe yang ada di dalam folder AppLoader, seperti vendor.xml yang tadi dihapus
- akan muncul tampilan seperti gambar 1, klik Next

Gambar 1

- pada gambar 2 BlackBerry belum terhubung di box Connection terlihat kosong

Gambar 2

- colokkan kabel USB ke BlackBerry, saat sudah terdeteksi dan muncul tulisan USB-PIN: UNKNOWN segera klik tombol Next (gambar 3) dan pasang baterai kembali. Bila gagal artinya handheld sudah terdeteksi dan tidak bisa melanjutkan instalasi OS. Ulangi langkah ini

Gambar 3

- kemudian akan muncul menu berikutnya, gunakan pilihan yang bawah (Replace the device’s applications with the older version provided by the BlackBerry Desktop Software), klik Next

Gambar 4

- jalani proses instalasi OS seperti biasa
- mestinya BlackBerry sudah bisa booting dan normal kembali

Secara umum mestinya solusi di atas sama saja bila menggunakan DM versi berapapun atau handheld BlackBerry jenis apapun. Kebetulan karena saya cuma punya BlackBerry Curve 8520 jadi ya itu saja yang kebetulan saya alami dan contohkan di sini untuk mengatasi penyakit nuked ini. Versi OS akhirnya saya putuskan untuk downgrade ke versi OS 5.0.0.238. Sama-sama leaked OS sih, tapi sepertinya versi 238 lebih stabil. Dan GenTa normal kembali.

A – Contact
B – Browser
C – Compose
D – Memopad
E – none
F – Profiles**
G – Google Talk
H – Help
I – AOL Instant Messenger
J – none
K – Keypad lock (selain alt + enter)
L – Calendar
M – Messages
N – BlackBerry Messenger
O – Options
P – Call log
Q – ICQ
R – none
S – Search
T – Task
U – Calculator
V – Saved messages
W – none
X – Windows Live Messenger
Y – Yahoo Messenger
Z – none

Sebagai pengguna baru mungkin saja ada shortcut yang salah atau kurang. Untuk bisa menjalankan shortcuts di atas harus memilih No pada menu Options > Phone Options > General Options > Dial From Home Screen. Bisa juga melalui tombol hijau untuk dial lalu menu (logo BB) > Options dan langkah-langkah berikutnya sama.

* shortcut bisa digunakan bila aplikasi yang dituju sudah tersedia (install) di handheld. Misal Q untuk ICQ, tak bisa digunakan bila tidak instal ICQ.
** shortcut F tidak berlaku untuk OS 5. Mungkin disebabkan nama menu berubah dari Profiles menjadi Sounds.
*** daftar shortcut di atas bisa dijalankan bila menggunakan menu bahasa Inggris. Bahasa yang berbeda akan membuat perbedaan shortcut juga.