Cara Memperbaiki Blackberry yang Rusak Akibat Kesalahan Software Terbaru 2014

Cara memperbaiki blackberry yg mati akibat kesalahan software/restart trs/hang :
Siapkan:
PC os windows
Desktop Manager
Os blackberry yg sesuai dgn type bb yg akan di perbaiki
Usb kabel

Step 1: 
Instal Desktop manager Dan Os bb nya di komputer/laptop. Setelah penginstalan Os selesai pastikan hapus file vendor.xml di C:Program Files > Common Files >Research In Motion > AppLoader.setelah di klik apploader .

Cara Install OS BB : http://softwarebb.blogspot.com/2012/06/tipstrik-blackberry-cara-upgrade-atau.html

Step 2:
Pastikan BB nya gak konek ke komputer dulu
Trus buka APP Loader Application. Ini tempatnya ada di: C:Program Files > Common Files >Research In Motion > AppLoader.setelah di klik apploader, trus klik next.

Step 3:
Nanti akan terbuka window Communication Port Selection.
Karena BB kita mati, pastinya ngga akan ketemu PIN BB tersebut, tapi nanti ada tulisan COM1. Nah.. supaya terbaca, kita langsung colokkan dengan USB kabel sampe nongol USB-PIN:UNKNOWN, nah setelah terlihat, buru2 klik Next.

Pada masa ini, led BB nya akan berwarna merah, jangan sampe led nya mati lagi, kalo begini, brarti kudu dari awal. Triknya: cabut aja baterenya. Sampe nanti nongol USB-PIN:UNKNOWN, baru masukin baterenya.

Step4:
C:Program Files > Common Files >Research In Motion > AppLoader.setelah di klik apploader, trus klik next. Tinggal di centrang aja applikasi yang mau dimasukin dlm penginstalan Os. Kalo bingung, centrang semua. Setelah ini klik Next dan approved yang mau di Install klik Finish.

Sekarang tinggal tunggu aja komputer yang ngerjain semua sambil ngupi juga bisa, karena ini akan memakan waktu yang lama. Setelah selesai , bisa diliat nanti ada window lagi

The loading operation was successful, BB nya dah siap untuk ‘reloading’ lagi, copot kabel usb nya, dan seperti biasa… loading awal ini akan memakan waktu 10 – 20 menit khan… tungguin aja, kalo berhasil berarti akan nongol wallpaper awal, kalo ngga… ya ngulang dari awal… tapi biasanya berhasil kok.

Bila blackberry anda mati total bisa gunakan :

Blackberry mati total atau matot,kasus seperti ini kerap di alami oleh blackberry, Penyebab blackbery mati total adalah:kecemplung got,kecemplung closet,jatuh,kesiram air dan di banting..ya iyalah, itu pasti bisa menyebkan semua poncel mati total, Penyebab utama blackberry mati total adalah:

• Rusaknya IC power.
• Penggunaan carger portable yang terlalu lama,dan jangka lama berhati hatilah Tapi anda jangan panik ketika anda mendapati blackberry anda mati total,kali ini saya akan berbagi tips pertolongan pertama yang harus anda lakukan ketika bb anda mati total,

Berikut langkah langkahnya:

• Cabut Baterai, SIM Card, Media Card, biarkan terbuka.
• Jalankan Desktop Manager.
• Sambungkan Blackberry dengan PC menggunakan kabel USB.
• Tunggu sampai muncul gambar battery disilang.
• Pasang battery tanpa melepas sambungan blackberry dengan PC.
• Tunggu sampai Blackberry menyala, biarkan charge sampai beberapa garis battery
• Cabut koneksi, segera charge dengan charger… Semoga membantu.

Jika Blackberry sobat sedang trouble, mungkin beberapa langkah pengerjaan dibawah ini bisa membantu:

Dari berbagai kasus yang terjadi pada BlackBerry, seperti  bold 9000, gemini 8250/8350, curve 8310/8320, javelin 8900, pearl 3G 9105,  curve 9220 – 9320, curve 9300 3G, apollo 9360,  9370 – 9380, storm 9500/9530, strom2 9550, tour 9630, essex 9650, onyx 9700, onyx2 9780, bellagio 9790, torch 9800 – 9810, monza 9860, dacota 9900, montana 9930, Porsche Design P’9981 dll. ternyata permasalahan yang juga sering didapat adalah BB dalam kondisi mati total (matot) dan hanya led yang kedip-kedip merah atau hidup loading sebentar terus restart lagi atau juga malah tidak ada tanda – tanda kehidupan sama sekali. Kasus ini ada dua kemungkinan bisa karena software bisa juga karena hardware.
Sebelum sobatt melangkah lebih jauh, jika BB tidak ada tanda – tanda kehidupan sama sekali.. maka pastikan dulu battery Blackberry dalam kondisi bagus dan terisi full, ukur dengan multitester jika punya, catu daya sekitar -+ 4v atau bisa pinjam battery BB teman yang sama dan coba hidupkan di BB sobatt, apakah bisa hidup?? coba dengan melepas simcard dan mmc serta battery -+ 5menit setelah itu coba pasang kembali.

Jika usaha demikian belum berhasil, itu artinya permasalahan ada di software atau hardware (ic power, ic zocus, ic flash, ic cpu atau komponen lain).
Maksimalkan dulu ke software, coba dengan reload OS. Jika kondisi ketika blackberry dinyalakan, lampu LED menyala merah untuk beberapa detik, kemudian akan terlihat layar putih dan jam pasir dan kemudian kembali mati, kemudian setelah beberapa detik blackberry akan menyala lagi, proses booting ini berulang terus maka keadaan demikian disebut “nuked”. Untuk penyelesaiannya bisa dicoba dengan reload upgrade OS

Prosedur:
- Instal program desktop manager dan firmware BlackBerry yang akan di reload os
- Browse ke folder AppLoader menggunakan explorer, biasanya terletak di C:\Program Files\Common Files\Research In Motion\AppLoader kemudian delete file vendor.xml di dalam direktory AppLoader
- Jalankan Program loader.exe di dalam direktory AppLoader
- Klik Next sampai ada dialog “Communication Port Selection''
- Pasang Kabel USB yang sudah terhubung BB ke PC
- Klik Next, ulangi beberapa kali bila perlu sampai proses install OS dapat berjalan
Kode kedipan lampu LED pada saat awal loading menunjukkan suatu nilai biner yang menginformasikan pesan dari bootROM. biner 1, nyala kedip lampu merah sedangkan biner 0 dengan tidak nyalanya led (off). Apabila led menyala secara kontinyu, ini merupakan pesan sedang melakukan security wipe, apabila led menyala kontinyu tidak pada saat melakukan security wipe, ini mengindikasikan adanya kerusakan hardware.
1 (desimal = 1) Bukan problem, kode ini adalah normal saat restart
11 (desimal = 3) Tidak ada sistem operasi di dalam blackberry, lakukan reload sistem operasi dengan MFI
101 (desimal = 5) Bad OS CRC
111 (desimal = 7) Missing OS CRC
1011 (desimal = 11) Missing OS Trailer
1101 (desimal = 13)OS Not Signed, coba loading OS kembali
1111 (desimal = 15) OS Signature Invalid, coba loading kembali OS dan biarkan mati tanpa baterai selama hampir 30 menit, kemudian coba hidupkan kembali. Apabila tetap muncul pesak kesalahan, coba lakukan penggantian flash.
10101 (desimal = 21) Unknown Flash Manufacturer, coba lakukan penggantian flash
10111 (desimal = 23) Flash Initialization Problem, coba lakukan penggantian flash
11011 (desimal = 27) Flash Erase Failure ,coba lakukan penggantian flash
11101 (desimal = 29) Flash Operation Out Of Range
11111 (desimal = 31) Bad BootROM CRC, coba lakukan penggantian flash
101011 (desimal = 43) USB Driver Error
101101 (desimal = 45) No BootROM CRC
101111 (desimal = 47) Flash Write Failure, coba lakukan penggantian flash
110101 (desimal = 53) Invalid Memory Configuration Table
110111 (desimal = 55) Password Not Initiated
111011 (desimal = 59) RAM Initialization Problem, coba lakukan penggantian flash
111101 (desimal = 61) Cache No Pages Free
111111 (desimal = 63) Cache Invalid Page Type
1010101 (desimal = 85) Random Number Failure
1010111 (desimal = 87) OSStore Failure
1011011 (desimal = 91) Security Init Failure
1011101 (desimal = 93) NAND failure
1011111 (desimal = 95) General Assert Failure
1101011 (desimal = 107) GPIO failure
1101101 (desimal = 109) Runtime library failure
1101111 (desimal = 111) Exception: undefined isntruction
1110101 (desimal = 117) Exception: SWI
1110111 (desimal = 119) Exception: Prefetch Abort
1111011 (desimal = 123) Exception: Data Abort
1111101 (desimal = 125) Exception: Reserved
1111111 (desimal = 127) Exception: IRQ
10101011 (desimal = 171) 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 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.
Jika tidak ada tanda -tanda kehidupan sama sekali dan sudah coba ganti battery lain kemungkinan besar ic power lemah dan rusak. cobalah dengan melakukan reball ulang atau ganti yang baru jika perlu.
cek juga kadang BB short yang mengakibatkan jadi matot. cek juga komponen-komponen/ic yang lain, seperti zocus dll
Kemungkinan lain ic flash dan ic cpu, namun jika ya demikian maka harapan hidup normal akan semakin kecil, karena rata-rata BB ic nya di lem. tapi dengan usaha dan coba siapa tau ada hasil.
Semoga bermanfaat..