View Single Post
Old 06-07-2012, 06:59   #6 (permalink)
.:MobileLife:.
No Life Poster
 
.:MobileLife:.'s Avatar
 
Join Date: Oct 2005
Location: iSiddeque
Age: 41
Posts: 2,009
Member: 188260
Status: Offline
Sonork: 100.1590438
Thanks Meter: 428
Quote:
Originally Posted by mr.omphonx View Post
go to tab dcc read/write

click erase flash after finish Resurrection again
ploading resurrector data into memory...OK
Starting communication with resurrector...OK

Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0040 (256MB)

Erasing FLASH1 memory from 0x000000000000 to 0x00000FFFFFFF...OK
WARNING: Erasing Error (0x24) at 0x000000060000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x000000060000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x000000060000 is Ignored. Erase continues.
WARNING: Erasing Error (0x24) at 0x0000000C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x24) at 0x000006440000 is Ignored. Erase continues.
WARNING: Erasing Error (0x24) at 0x00000DE20000 is Ignored. Erase continues.
WARNING: Erasing Error (0x24) at 0x00000E6C0000 is Ignored. Erase continues.
Completed in 00:00:32.666 (Average Transfer Rate: 8024.98 kB/s)

__________________________________________________ ________-

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.32, JTAG Manager Version: 1.43
Selected Resurrector: [Samsung C6712 V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x07926F0F - CORRECT!
Set I/O Voltage reads as 2.99V, 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: 0x00EC/0x0040 (256MB)
Selected Resurrection Data for the NAND Chip with Page size = 2KB

Flashing the dead body...OK
WARNING: Programming Error (0x24) at 0x000000060000 is handled as Cut Excess.
WARNING: Programming Error (0x24) at 0x0000000C0000 is handled as Cut Excess.
Resurrection complete!
  Reply With Quote
 
Page generated in 0.09405 seconds with 7 queries