s5570i after resurrection from riff box still no power? - GSM-Forum

tadz · 11-16-2013, 15:41

her's the log file:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.51
Selected Resurrector: [Samsung S5570i V1.0.4476.11820]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - CORRECT!
Set I/O Voltage reads as 3.01V, TCK Frequency is 3 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: 0x00EC/0x0050 (512MB)
Selected Resurrection Data for the NAND Chip with Page size = 4KB

Flashing the dead body...OK
WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000040000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000080000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000000C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000100000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000140000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000000440000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001240000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001280000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000012C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001300000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001340000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001380000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000013C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001400000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001440000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001480000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000014C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001500000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001540000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x000001580000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x0000015C0000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF00000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF40000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FF80000 is handled as Cut Excess.
WARNING: Programming Error (0x25) at 0x00001FFC0000 is handled as Cut Excess.
Resurrection complete!

11-16-2013, 15:41	#1 (permalink)
tadz Insane Poster Join Date: Sep 2007 Location: jeddah Posts: 90 Member: 591475 Status: Offline Thanks Meter: 10	s5570i after resurrection from riff box still no power? her's the log file: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.51 Selected Resurrector: [Samsung S5570i V1.0.4476.11820] Connecting to the dead body...OK Detected dead body ID: 0x07B3617F - CORRECT! Set I/O Voltage reads as 3.01V, TCK Frequency is 3 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: 0x00EC/0x0050 (512MB) Selected Resurrection Data for the NAND Chip with Page size = 4KB Flashing the dead body...OK WARNING: Programming Error (0x25) at 0x000000000000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000040000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000080000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000000C0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000100000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000140000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000000440000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001240000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001280000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000012C0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001300000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001340000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001380000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000013C0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001400000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001440000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001480000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000014C0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001500000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001540000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x000001580000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x0000015C0000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00001FF00000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00001FF40000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00001FF80000 is handled as Cut Excess. WARNING: Programming Error (0x25) at 0x00001FFC0000 is handled as Cut Excess. Resurrection complete!