|
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-06-2016, 12:17 | #1 (permalink) |
No Life Poster Join Date: May 2009 Location: spain
Posts: 2,991
Member: 1038811 Status: Offline Sonork: 100.1585462 Thanks Meter: 974 | i9205 resurrector error? I got the same error with both resurrectors, 442 and the other one. Code: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.56 Selected Package: [Samsung I9205 V4.4.2 V1.01 by <Babak Nuri>] Connecting to the dead body...OK Detected dead body ID: 0x308930E1 Set I/O Voltage reads as 1.79V, 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...FAILED ERROR: No response from the RIFF Box. |
04-06-2016, 17:04 | #3 (permalink) |
No Life Poster Join Date: May 2009 Location: spain
Posts: 2,991
Member: 1038811 Status: Offline Sonork: 100.1585462 Thanks Meter: 974 | Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.56 Selected Package: [Samsung I9205 V4.4.2 V1.01 by <Babak Nuri>] Connecting to the dead body...OK Detected dead body ID: 0x308930E1 Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at 9 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: 0x0045/0x0100 (SEM08G, 0x0001D2000000 Bytes = 7.28 GB) Detected an Initialized FLASH2 Chip, ID: 0x0045/0x0100 (SEM08G, 0x000000200000 Bytes = 2.00 MB) Flashing the dead body...ERROR ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK ERROR: Stopped due to multiple communication errors. Terminating at 0x0000003FA400 |
04-06-2016, 17:14 | #4 (permalink) |
No Life Poster Join Date: May 2009 Location: spain
Posts: 2,991
Member: 1038811 Status: Offline Sonork: 100.1585462 Thanks Meter: 974 | tried the emmc flash plugin Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.56 Selected Resurrector: [Samsung I9205 V1.0.5113.60621] Connecting to the dead body...OK Detected dead body ID: 0x308930E1 - CORRECT! Set I/O Voltage reads as 1.79V, TCK Frequency is RTCK Adaptive Clocking RTCK Sampling is: [Sample at 9 MHz] Settings Code: 0x0000000F000000000000000000000000 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: 0x0045/0x0100 (SEM08G, 0x0001D2000000 Bytes = 7.28 GB) Detected an Initialized FLASH2 Chip, ID: 0x0045/0x0100 (SEM08G, 0x000000200000 Bytes = 2.00 MB) Resuming write FLASH1 memory from 0x000004000000 to 0x00000401FFFF on 0x000004010000 ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK ERROR: Stopped due to multiple communication errors. Terminating at 0x000004010000 |
04-06-2016, 20:16 | #5 (permalink) |
No Life Poster Join Date: Jul 2012
Posts: 535
Member: 1783314 Status: Offline Sonork: 100.1620532 Thanks Meter: 127 | Try with even lower rtck like 2 or 4 Mhz. Also how was the phone bricked? What did the customer say happened to the phone? Sent from my SAMSUNG-SGH-I317 using Tapatalk |
Bookmarks |
| |
|