|
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 | Search | Today's Posts | Mark Forums Read |
| LinkBack | Thread Tools | Display Modes |
02-01-2016, 12:28 | #1 (permalink) |
Junior Member Join Date: Nov 2013 Location: Bandar E Abbas - IRAN
Posts: 1
Member: 2057556 Status: Offline Thanks Meter: 0 | I9100 32GB dead boot problem Help me to solve this problem. Here is my log Code: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.56 Selected Resurrector: [Samsung I9100 V1.0.4850.415] Connecting to the dead body...OK Detected dead body ID: 0x4BA00477 - CORRECT! Set I/O Voltage reads as 2.81V, TCK Frequency is 8 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 (VZL00M, 0x000774000000 Bytes = 29.81 GB) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (VZL00M, 0x000000080000 Bytes = 0.50 MB) No Resurrection Data is available for the eMMC Chip with Capacity = 29.81GB WARNING!!! Using 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. |
Bookmarks |
Thread Tools | |
Display Modes | |
| |
|