|
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 |
12-31-2013, 14:51 | #1 (permalink) |
Freak Poster Join Date: Feb 2008
Posts: 359
Member: 714291 Status: Offline Thanks Meter: 39 | Samsung n7000: Error on resurrection Am trying to resurrect samsung N7000 but getting programming error see the log below pls give me a good lead on reviving my phone open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.55 Selected Resurrector: [Samsung N7000 V1.0.4860.58267] Connecting to the dead body...OK Detected dead body ID: 0x4BA00477 - CORRECT! Set I/O Voltage reads as 2.79V, TCK Frequency is 4 MHz 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: 0x0015/0x0100 (VYL00M, 0x0003AB400000 Bytes = 14.68 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (VYL00M, 0x000000080000 Bytes = 0.50 MB) Selected Resurrection Data for the eMMC Chip with Capacity = 14.68GB Flashing the dead body... WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000004000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000008000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000000C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000010000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000014000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000018000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000001C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000020000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000024000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000028000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000002C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000030000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000034000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000038000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000003C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001800000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001804000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001808000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000180C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001810000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001814000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001818000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000181C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001820000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001824000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001828000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000182C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001830000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001834000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001838000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000183C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001840000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001844000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001848000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000184C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001850000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001854000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001858000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000185C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001860000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001864000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001868000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000186C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001870000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001874000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001878000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000187C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001880000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001884000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001888000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000188C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001890000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001894000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001898000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00000189C000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018A0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018A4000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018A8000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018AC000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018B0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018B4000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018B8000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018BC000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018C0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000018C4000 is handled as Cut Excess. ERROR: Forced to Terminate. Terminated at 0x0000018C8000 Thanx! |
01-01-2014, 11:30 | #3 (permalink) |
Freak Poster Join Date: Oct 2007
Posts: 334
Member: 619957 Status: Offline Thanks Meter: 50 | Error code 0x25 Returned by the DCC Loader when it fails to program part of flash memory. This is not an abnormal situation for NAND memories – bad blocks and pages are sometimes appear due to specific NAND memory’s technology. User shall select how to handle block program error in the JTAG Manager – for this user must be familiar with bad blocks handling techniques in general. |
Bookmarks |
| |
|