pico

Diberdayakan oleh Blogger.

Selasa, 13 Desember 2011

Blackberry Hardware Solution Part 2

Photobucket
SOS and VBatt BB-9300

Photobucket
Trackball Bold BB-9000

Blackberry Hardware Solution Part 1

Photobucket
USB Way Storm-2 BB-9550

Photobucket
USB Way Storm BB-9500


Photobucket
USB Way BB-9300

Photobucket
USB Way Javelin BB-8900

Photobucket
USB Way BB-8520

Photobucket
USB Way Bold BB-9000

Photobucket
USB Way BB-8100

Photobucket
USB Way Onyx BB-9700

Photobucket
USB Way BB-9100

Photobucket
USB Way BB-8310

Photobucket
USB Way Tour BB-9630



Selasa, 06 Desember 2011

PINOUT Nokia BB5

Pada kesempatan kali ini, kami buatkan kumpulan Pinout khusus BB5 dari Losnn Clamp, semoga bermanfaat. Terima kasih kami haturkan kepada Losnn Electronic atas Produck dan Support-nya.

Photobucket

DOWNLOAD HERE

TITIK UKUR NOKIA ( Check Point )

Untuk menangani ponsel mati total, sebaiknya terlebih dahulu kita cek tegangan kerja yang diperlukan ponsel tersebut untuk booting pertama atau sering disebut 1st boot. Untuk itu kami coba memberikan beberapa koleksi dari hasil copas dari berbagai sumber. Semoga bermanfaat.

Photobucket

Download Area :

PART 1
PART 2
PART 3
PART 4
PART 5
PART 6
PART 7
PART 8

Senin, 26 September 2011

FIRMWARE NOKIA BI ONLY

1800 RM-653 BI ONLY 5030 RM-524 BI ONLY

Kamis, 22 September 2011

SKEMA BLACKBERRY ( BLACKBERRY SCHEMATIC )



Berikut ini kami coba mengumpulkan skema Blackberry, semoga bisa bermanfaat.

SKEMA BLACKBERRY ( BLACKBERRY SCHEMATIC )

Blackberry 8130


Blackberry 8900


Blackberry 88xx


Blackberry 8100


Blackberry 8520


Blackberry 8800


Blackberry 8900


Blackberry 9000


Blackberry 9500


Blackberry 9700



dari berbagai sumber

Senin, 22 Agustus 2011

HWK Update v.2.2.0.2

HWK Release 22/08/2011

Release Date: 22/08/2011

The Official release is ready in our download area http://sarunasoftware.com.


WARNING !!!
If the HWK is a "TRIAL" or affected by 3rd party tools, this software may not work properly, so use at your own risk.


Since this is a minor update release, there is no need to update your HWK if you have already updated on the v2.2.0.0 release.


DCTxBB5 v2.2.0.2
-----------------

1. BB5 RAPU Based Products USB Flashing / UI support added:
RM-776 (C3-01.5)
2. DCT4 INFINEON Based Products USB Flashing / UI support added:
RM-692,RM-693,RM-702,RM-713 (C2-02,C2-02.1,C2-03,X1-01)


LG_GSM v2.2.0.2
-----------------

1. Infineon:
A108,A190,A190a,A190b,A210,A210b,GB125R,GC900fGO,G T350f,
KS360GO added.
2. EGV V3-32 and EGV V3-64 Direct Unlock and IMEI enable added.
Note: Use [Unlock] before IMEI rebuild.
3. EGV V3-64 new Flash Chips Support.


SAMs v2.2.0.2
--------------

TRIDENT VISION
for non 8 Digits PCK Fixed.
SWIFT-AEROFONE
E1050-CHN,E1050V,E1086i,E1150-CHN,E1155L,E1180,E1190,E1220i
added (PUNL,PIM,FL)
E1182L added (DUNL,PUNL,PIM,FL)
E1225T,E1182 TFS Flashing bug Fixed.
C3322 Unlock, IMEI, Sections bug Fixed.
B7722,B7732 Slave Part Flashing/Read/E2P added.
QUALCOM
T669 Added.
INFINEON
C3011,C3560,C3750,C3752 added (CUNL,PUNL,PIM,FL,UFL)
E2232 Flashing bug Fixed.
for non 8 Digits PCK Fixed.

Many thanks to all those who have supported us!!!


Odia.
www.sarasbox.co.uk
www.gsm-solutions.co.uk

DOWNLOAD HERE

Sabtu, 23 Juli 2011

KODE ERROR PADA BLACKBERRY

Berikut adalah daftar error code yang mungkin dialami Java Virtual Machine (JVM) di BlackBerry. Silakan terjemahkan sendiri dan googling untuk mendapat keterangan tambahan.



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: — 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: — 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: — 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 needs running — An opcode requires that a class execute before it can continue execution.

514 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 <> 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.com

Rabu, 13 Juli 2011

TUTORIAL SE-TOOL

Photobucket

CID36 DB2010
CID49 DB2010
CID49 DB2020
CID51 DB2020
CID52 DB2012
CID52 DB2020
CID52-53 DB2020-DB2012-DB2001-PNX5230
CID52 DB2012 Unlock Procedure (FLASH Method)
CID52 DB2012 Unlock Procedure (RESTORE Method)
Manual for DB2020 unlock by flash patch
PDA - Old security
PERMANENT unlock from network DB2020-DB2012-DB2001-PNX5230

Sabtu, 18 Juni 2011

ultimate_blackberry_howto_ebook

Ebook : ultimate blackberry

Download

Jumat, 03 Juni 2011

HWK Release 22/05/2011

Release Date: 22/05/2011

The Official release is ready in our download area http://sarunasoftware.com.


WARNING !!!
If the HWK is a "TRIAL" or affected by 3rd party tools, this software may not work properly, so use at your own risk.

Please make sure you un-install all old versions, first HWK Suite, then HWK Support Suite, you can then install the new software, first HWK Support Suite and then HWK Suite.

You MUST update your HWK using client 2.2.0.0, old client versions will no longer work.

You MUST be running HWK software 2.2.0.0 to access support.

DOWNLOAD :

http://rapidshare.com/users/VAY6Q3

OR :

HWK_Major_Suite_v02.02.000.part01
HWK_Major_Suite_v02.02.000.part02
HWK_Major_Suite_v02.02.000.part03
HWK_Major_Suite_v02.02.000.part04
HWK_Major_Suite_v02.02.000.part05
HWK_Major_Suite_v02.02.000.part06
HWK_Major_Suite_v02.02.000.part07
HWK_Major_Suite_v02.02.000.part08
HWK_Major_Suite_v02.02.000.part09
HWK_Major_Suite_v02.02.000.part10

HWK_Support_Suite_Setup_v02.02.000

Senin, 23 Mei 2011

PETUNJUK UPGRADE BLACKBERRY

Syarat:
1. Windows XP
2. BlackBerry Desktop Manager versi 4.6

Prosedur:
1. Download installer OS Blackberry
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.

MENGHAPUS SEMUA KONTAK BLACKBERRY

1. Go to address book
2. Tekan tombol menu
3. Pilih options dari menu
4. Klik ALT+aA bersamaan kemudian ketik huruf RSET
5. Biarkan terus sampai seluruh contact hilang

RESET DEFAULT SETTING BLACKBERRY

1. pilih option

2. pilih security option

3. pilih general setting

4. tekan tombol menu

5. pilih Wipe Handheld


setelah muncul enter "black berry" to comfirm handheld wipe


6. masukan kata blackberry



cabut baterai dan pasang kembali....

semoga bermanfaat

Minggu, 08 Mei 2011

ANALISA DAN SOLUSI SIGNAL HP NOKIA

Analisa dan solusi problem signal All nokia dct4 & bb5

mungkin semua pada udah mengerti langkah2 apa yg harus di analisa & dan yg akan dikerjakan,bila teman2 mempunyai kasus masalah signal.

Dan sekarang saya akan memberi tips / cara analisa & cara pengerjaannya,ini sedikit info pengalaman tentang kasus/masalah signal ;

Kerusakan paling banyak dan paling menjengkelkan adalah masalah sinyal. Ponsel semahal apapun tanpa ada signalnya tidak ada harganya. Juga bila membawa ponsel mahal sekalipun tapi problem pada signalnya maka bisa membuat malu pembawanya.
Sinyal merupakan problem yang gampang-gampang susah bagi semua teknisi ponsel. Signal kebanyakan identik dengan PA atau IC PA, walau sebenarnya tidak benar seratus persen. Problem signal mempunyai banyak keterkaitan antara satu IC (komponen) dengan komponen yang lain.
Untuk bisa menyelesaikan problem signal dibutuhkan beberapa syarat mutlak bagi setiap teknisi ponsel. Diantaranya :
Teknisi harus mempunyai pengetahuan tentang fungsi tiap komponen, kedua, teknisi harus mempunyai alat test dan alat perbaikan, serta yang ketiga, teknisi harus mempunya kemampuan lebih atau ilmu plus, maksudnya teknisi harus bisa memecahkan problem dengan tehnik yang berbeda.

Ada bebarapa macam tentang problem signal, diantaranya :
1. Signal lemah
2. Signal naik turun
3. Signal pada lokasi tertentu
4. Signal 5 detik
5. No signal
6. Signal 112 only
7. Signal drop
8. Signal semu
9. Signal sim tertentu

Langkah persiapan awal :
a. Lakukan reset atau kembali pada pengaturan awal, yang dapat anda lakukan melalui menu lalu phone setting, setelah itu masukkan 12345.
b. Lakukan panggilan 112 only atau jaringan manual, bila bisa maka IC RF dalam keadaan masih baik.
c. Lakukan update pada software ponsel anda. Bisa juga melakukan downgrade bila dirasa perlu dan memang versi yang sebelumnya terlalu tinggi.
d. Lakukan pengujian tegangan pada komponen seperti IC PA, IC RF, IC AUDIO, apakah sudah mendapat tegangan yang benar.

Bila langkah awal atau persiapan sudah kita lakukan tetapi ponsel masih bermasalah maka dapat dilakukan penggantian komponen sesuai kerusakan yang dialami oleh ponsel tersebut.
1. Signal lemah, lakukan penggantian pada IC PA, karena komponen ini berfungsi sebagai penguat.
2. Signal naik turun, dapat terjadi karena VCO sudah lemah, fungsi referensi nya sudah terabaikan.
3. Signal pada lokasi tertentu, gantilah IC PA nya, karena pasti memakai IC yang tidak orisinil, atau akibat penggantian antena nya.
4. Signal 5 detik, terjadi kerusakan pada IC CPU, bisa karena ponsel jatuh, namun bila bukan karena jatuh anda dapat melakukan flashing eeprom virgin, sehingga ponsel jadi normal kembali.
5. No. Signal, pada ponsel jatuh lebih banyak kerusakan pada IC Audio, fungsi konverternya tidak berhasil.
6. Signal 112 only, merupakan signal hanya dari IC RF, anda bisa mengganti IC PA karena sudah tidak fungsi lagi.
7. Signal drop, ini diakibatkan karena IC PA, walau IC PA sendiri masih berfungsi tapi pemakian arus yang sangat tinggi sekali, bisa mencapai 600 mA.
8. Signal semu, indikator tampak baik dan penuh, tapi tidak bisa melakukan panggilan, lebih banyak dikarenakan Antena, fungsi penghubung yang terputus.
9. Signal sim tertentu, dikarena program atau SW bisa dilakukan clear SP Lock dan bisa juga akibat penggantian IC PA tidak presisi atau IC PA tidak ori.

10.kerusakan signal bisa terjadi dari kesalahan software,yg disebabkan dari

a.FILE PM kurang bagus
b.file tuning gak bagus [cdma]
c.juga bisa disebabkan dari FITUR UI SETTING pada bagian fitur box,yg gak digunakan pada saat kita melangkah ke sofware.

maka kesimpulan dari system kerja ponsel bila ada kasus signal kita harus teliti pada bagian software,yaitu;pm,tun cdma,ui setting,

dan bila sudah di analisa oleh software dan masih tetep no signal barulah kita melangkah ke hardware,yg sudah disebutkan diatas langkah2 penanganannya.

moga bermampaat silahkan di tambain kalau ada yg kurang

By : Azisah Cell Uttang

KODE LCD HP CHINA

LCD 6300 CINA .......... FPC4328A-V1
LCD 6500 CINA .......... DFT-60248-03 v01

LCD Anycall GC668 .......... 145713-A
Anycall LCD T728 .......... TFT8K-2132-FPC-A1-E

LCD ASIAFONE 108 .......... 2001803
LCD ASIAFONE 303 .......... TFT8K1480FPC-A1-E
LCD ASIAFONE 306 .......... SAT 22009 A16B
LCD ASIAFONE 701 .......... D133CPT
LCD BB i900 .......... YT20F34GIA-FPC-A

LCD BEYOND B 505 .......... TFT8K-1499 FPC
LCD BEYOND B 530 / 818 GSTAR .......... TFT8K1569FPC-A1-E
LCD BEYOND B 555/STARTECH st21 .......... FPC C14MVGU-1-01
LCD BEYOND B 600 .......... FPC ST020B6C-D30VERI
LCD BEYOND B 620 .......... HT 020-699
LCD BEYOND B 68 .......... ART22F3605 Q
LCD BEYOND B 710/SPIRIT 77 .......... FPC-ST024C6CD20-VER1
LCD BEYOND B 818 / B 618 .......... 8K1201
LCD BEYOND B 868 .......... TFT8K1287FPC-B2-E
LCD BEYOND B 9000 .......... TFT8K-3309FPC-A1-E
LCD BEYOND B 999i .......... FPC-S95339-v01
LCD BEYOND B510/SWAHOO 1103/ST55/MY G 200
LCD BEYOND B720 .......... FPCST024C6CD-Noo

LCD CB80 CROSS .......... WD04569A
LCD CB90 CROSS .......... WD 04583 AFIS
LCD GG51 CROSS .......... YL8674
LCD GG53 CROSS .......... WD604BF
LCD GG66 CROSS .......... JYD G6096 SA
LCD GG77 CROSS .......... JFP-60278-01
LCD GG777 CROSS .......... YT028C08SB
LCD GG79 CROSS .......... YL88H5MLA
LCD CSL Blueberry .......... FPC-G240 T40-185 C V00
LCD DEZZ0 D800 .......... TFT8K3288 FPC-A1-E

LCD D-ONE 289 .......... FPC 4219J-V1 BF
LCD D-ONE 758 .......... GA JYD 200-0119 FPC-A
LCD D-ONE 768 .......... TFT8K3503 FPC-A1-E
LCD D-ONE DG558/TAXCO VX1 .......... T-0079
LCD D-ONE DG568 .......... FPC-T24JHSO1
LCD D-ONE DG578 .......... YL9737MLA-AO
LCD D-ONE DG638 .......... GA JYD 200-0119 FPC-A
LCD D-ONE DG829/ZTC303 .......... 8K1038

LCD E66 CINA .......... FPC-Y8021 V02
LCD E71 CINA .......... TFT8K3339-A1-E
LCD E71 CINA .......... KTFT2400-100
LCD E90 CINA .......... TFT 8K1569FPC-A1-E
LCD EDLINE 8900 .......... YDT240000
LCD ELZIRO .......... KT220AA-033A-V1
ESIA LCD Warna .......... WD-X1008V7

LCD eTouch 303 .......... ART20F1701S
LCD eTouch 505 .......... WTD WD 04569 B
LCD eTouch BB 626 .......... TFT8K-3262 FPC-A1-E
LCD E66 eTouch BB .......... TFT 8K3277 FPC-A2-E
LCD eTouch E606/GSTAR 988/VODASTAR 228 .......... 8K 3277
LCD eTouch TD830 .......... TFT8K-1556-FPC-A1-E

LCD GSTAR 138
LCD GSTAR 168 .......... TSF8H0508FPC-A2-E
LCD GSTAR 238 .......... YM177-016B
LCD GSTAR 333
LCD GSTAR 368 .......... FPC-K200QFE-V8-01
LCD GSTAR 388 .......... YT2406CIA-FPC-A
LCD GSTAR 889/VODASTAR V288 .......... FPC1A0029
LCD GSTAR 899 .......... TM022-KDZ00
LCD 28 GT .......... Gog-1264-FPC-A1

LCD GVONE 530 .......... TSF8-H048S FPC-A1-E
LCD GVONE 620 .......... DMT 0597 FPC-A
LCD GVONE 808/TAXCO DM90 .......... FPCS95261
LCD GVONE 920 .......... TFT8K-3483-FPC-A1-E

LCD ST79/TAXCO H36/STARTECH HITECH DM78
LCD HITECH H38 .......... TFT8K1486FPC-A1-E
LCD HITECH h39/MY-G 660 .......... TFT8K1277FPC-A1
LCD HITECH H61/N96 CINA .......... TFT8K 1270 FPC-B1-E

LCD HT A30 .......... TFT8K2510FPC-A1-E
LCD HT G10/IMO 369/NEXCOM N69 .......... FPC2003701090922
LCD HT G10/VITELL V717 .......... KT200AA-027A
LCD HT G19 .......... ART 22F3702 Q CIF
HT LCD G30/BEYOND B85/E71 CINA / G91 Mito .......... TFT8K2469FPC-A1-E
LCD HT G31
LCD HT G32 .......... TFT8K2719FPC-A1-E
LCD HT G33 .......... S2222-0090
LCD HT M12/M21

IMO LCD 189/TAXCO W2/TIGER 338 .......... FPC2001802
IMO LCD 200 .......... 8H0484
IMO LCD 369 .......... FPC1773604
IMO LCD 819 .......... TFT8K 8717C-VO-CI
LCD IMO 9000 .......... TFT8K3327FPC-A1-E

LCD C2000 imobile
LCD C6000 imobile .......... TFT8K1358FPC-A1-E
LCD imobile i101 .......... FP-00509-04
LCD imobile i202 .......... FPC-T18DES33VOF
I315 LCD imobile
LCD imobile i510 .......... WD-F1212V7
LCD imobile i611

LCD I-PHONE 1711 .......... TFT8K-1711-FPC-A1-E
LCD I-PHONE 228 .......... FPC429/F-V1

LCD TI-MOBILE S707
TI-MOBILE LCD X607 .......... LT8179-01

LCD I-TU 8868 .......... TFT8K1670FPC-A1-E
LCD-TU 8878/IMO aku G911/MAXTRON 185/ZTE 777 .......... YT22F88CIB-FPC-A
LCD I-TU 8888 .......... JYD-GC200-0277 FPC-B

LCD KTOUCH A5118/B2200 .......... TSF8H0598FPC-A1-E
LCD KTOUCH A650/A615 .......... CT024TN02 M1-E
LCD KTOUCH A933/TOCALL T220 .......... TFT8K1296FPC-A1-E
LCD KTOUCH B830 .......... FPC4069AG-V
LCD KTOUCH D175 .......... TFT8K0943FPC-A1-E
LCD KTOUCH D177 FPC826A-V0
LCD KTOUCH D186 .......... TFT8K1253FPC-A1-E
LCD KTOUCH D770 .......... FPC4312E
LCD KTOUCH DT-08 .......... TFT8K1546FPC-A1-E
LCD KTOUCH E60 .......... PN 145074D
LCD H699 KTOUCH .......... TFT8K-3394-FPC-A1-E
LCD H888 KTOUCH .......... FPC8585N-V0-C
LCD H999 KTOUCH .......... 8K3859
KTOUCH V310 LCD .......... FPC8537
KTOUCH V908 LCD .......... TFT8K 1069 FPC-A1-E

LCD LEXUS 1108 .......... T177CHI-8
LCD LEXUS 2108 .......... FPC-242-4
LEXUS LCD 8011/BEYOND 868/N99 CINA .......... YT28F03MHA-FPC-C
LCD LEXUS L16 .......... FPC-Y80575 v01
LCD LEXUS L61/SKYPHONE 868 .......... FPC240-28
LCD LEXUS L88 .......... 8K3601
LCD MAXTRON 198 .......... T026QVT003

LCD Mito 2000/V708/HT G11/HT G18 .......... ART 20F 3707
LCD Mito 2108 .......... FPC242-4-V
LCD Mito 298/MY G600 .......... DMT0311FPC-B1
LCD Mito 800 .......... KD9718-128
LCD Mito 8100/LEXUS L18 .......... YT22F68 GIA-FPC-A
LCD Mito 8200 .......... GA240-0293
LCD Mito 737 838/VITELL .......... TFT8K 3248 FPC-A1-E
LCD Mito BB 189 .......... FPC2001802
LCD Mito BB 302
Mito LCD C6000 .......... TFT8K1358FPC-A1-E

LCD MIXCON BB M88 .......... TFT8K0706FPC-A1-E
LCD MIXCON BB S388 .......... TFT8K3278FPC-A1-E
LCD MIXCON BB S500 .......... FPC-51-ROHS0846
LCD MIXCON BB S908 .......... YT24F96CHD-FPC-A

LCD MY-G 600 .......... DMT0311FPC-B1
LCD MY-G 630 .......... TFT8K1208FPC-A1-E
LCD MY-G 638 .......... TFT-8K0679-A2-E
LCD MY-G 810/ST 59
LCD MY-G 880 .......... YDE FPC24T495-A1

LCD N70 .......... CINA TFT 4511
LCD N73 .......... CINA OPFPCT0566-V1
LCD N77 .......... CINA TFT8K1480FPC-A1-E
LCD N82 .......... CINA TFT8K 0561 FPC
LCD N95 8G CINA Soket
LCD N95 .......... CINA TSF805D (B)
LCD N96 .......... CINA KLLCMTFT2807-VOA
LCD N96 .......... Solder FPC-FTP280PO4N-OO
LCD N97 .......... CINA FPC-FTM300D072-00
LCD N97 .......... CINA X1300344P B

LCD NEXCOM NC69
LCD NEXCOM NC99 .......... 8K3495

LCD C951 NEXIAN .......... TFT8K3666FPC-A1-E
LCD NEXIAN G381/G501/G503 .......... FPC248
LCD NEXIAN G505 .......... FPC24239
LCD NEXIAN G522 ORI .......... TFT8K3369FPC-A1-E
LCD M10/VITELL G700/HT NEXIAN 288 .......... TSF8H-0478 FPC
LCD NEXIAN G788 .......... FPC8717
LCD NEXIAN G801 .......... FPC2065-1-AO
LCD NEXIAN G868 .......... TFT8K 3561FPC-A1-C
LCD NEXIAN G900/G922 .......... TFT8K2885FPC-A1-E
LCD NEXIAN G912 .......... TFT8K 2689 FPC-A1-E
LCD NEXIAN G923 .......... TFT8K3454 FPC-A1-E
NEXIAN LCD T788 .......... 1540003380
NEXIAN LCD T901 .......... 8K4703
LCD SPC C1000 BOSS .......... JYD GB220-0220 FPC-A
STARTECH LCD ST55/BEYOND B510

LCD SWAHOO S1102
LCD SWAHOO S890 .......... TFT8K-1962 FPC

LCD Taxco DM70 .......... FPC4219J-V1
LCD Taxco DM77 .......... FPC-FTM3000O03Z-00
LCD Taxco DM90
LCD Taxco TX60 .......... FPC-C177 VHV-2-B2
LCD Taxco TX65 .......... DMT0304
LCD Taxco W2 .......... FPC-200180209 1111 FGD
LCD TiPhone T67/D-ONE 739/TV3000 .......... 8K2352
LCD TITAN Q58 .......... 2003507

TOCALL LCD T1266
LCD TOCALL T210
LCD TOCALL T323 .......... G240T37TD-053
LCD TOCALL T550/BB CINA C9000 .......... TFT8K3327FPC-A1-E
TV LCD C1000 .......... WTD T171M

Vitell LCD 710 .......... JYD GB220-0218 FPC-A
LCD Vitell 717/HT G10 .......... KT200AA-027A
LCD V708 Vitell BB .......... LT 20F 3707
Vitell LCD T90 .......... TFT8K2898
Vitell V222 LCD .......... FPC-S92027A-1
LCD VODASTAR V888

LCD ZTE 1688 .......... TSF8H0485FPC-A1-E
LCD ZTE C335 .......... FPC 4506 A-V2

Minggu, 27 Maret 2011

Nokia New Update Universal, Flash, F Bus Cable Finder 2011

Nokia New Cable Finder + Model Picture
Nokia Universal Cable Finder + Model Picture
Nokia F Bus Cable Finder + Model Picture


Photobucket


DOWNLOAD

Kamis, 17 Februari 2011

China Phone Format Method

China Phone Format Method

Working For Which Problem:
1. Dead Phone
2. Restart Phone (with sim/without sim)
3. With Sim Phone Is Restart
4. Ringer Not Work
5. Mic Not Work
6. Bluetooth Not Work
7. Keypad Not Work
8. Phone Hang (Phone on but no incomeing/no outgoing/key not work)
9. Camera Hang
10. With MemoryCard Phone Not Power On
11. With Sim Card Phone Not Power On
12. Insert Sim
13. Emergency (network problem)
14. Call Hearing Spker not work.
15. Late Power On
16. Though u found any new solution by format add here, i found this.
(All Are Tested By Me)
these problems solved by format but its not true they allawes solved by format, so.....

Before Format!!!
Remember, before format allways readback ur phone current flash file, because sometimes after format previous on phone not power on, though not power on after format reflash ur phone with readback flash file (though ur CPU is MT6226BA, don't forgate Decypted ur readback flash file otherwise ur phone is dead still)

Format Address:
Recommanded Address : 0x00E00000-0x00200000 (it work for me for allawes)
16M FLASH: first address(Hex) 0x00E50000;format(Hex) 0x001A0000
08M FLASH: first address(Hex) 0x00700000;length(Hex) 0x00100000.
04M FLASH: first address(Hex) 0x003F0000;length(Hex) 0x00010000

JUST COPAS from : http://www.kbgsm.com/showthread.php?37723-China-Phone-Format-Method

Rabu, 16 Februari 2011

UFC PINOUT v5.7

Photobucket

DOWNLOAD

Hosting Gratis...Daftar yuuu

JOIN DISINI...IKUTI UPDATE TERBARU

 

Copyright © 2009 by TRIK SERVICE PONSEL