|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
04-15-2013, 10:43 | #1 (permalink) |
Insane Poster Join Date: Jul 2006 Age: 39
Posts: 95
Member: 314387 Status: Offline Thanks Meter: 7 | HTC Chacha can't repair boot Code: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [HTC ChaCha (PH0611000) V1.0.4745.47461] Connecting to the dead body...OK Detected dead body ID: 0x503C10E1 - CORRECT! Set I/O Voltage reads as 2.59V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at MAX] Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory...OK Starting communication with resurrector...OK Detected an Initialized FLASH1 Chip, ID: 0x00AD/0x55BC (512MB) Selected Resurrection Data for the NAND Chip with Page size = 2KB Flashing the dead body...OK WARNING: Programming Error (0x24) at 0x000002400000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000002440000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000002480000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000000000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000040000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000080000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000140000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000180000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x0000001C0000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000200000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000240000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000280000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x0000002C0000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000300000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x000000540000 is handled as Cut Excess. WARNING: Programming Error (0x24) at 0x0000024C0000 is handled as Cut Excess. Resurrection complete! |
04-15-2013, 11:07 | #2 (permalink) |
Product Manager Join Date: Apr 2006 Age: 55
Posts: 5,746
Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276 | Hi, This error is because DCC loader can't erase blocks in NAND. It could be due to some cold soldering on NAND chip, or any other HW problem. But, just in case, try rebooting Your PC and setting RTCK sampling to 1MHz, it may work. |
Bookmarks |
| |
|