I9100 error resurrection... - GSM-Forum

NSerN · 03-01-2012, 17:46

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.30, JTAG Manager Version: 1.38
Selected Resurrector: [Samsung i9100]

Connecting to the dead body...OK
Detected dead body ID: 0x4BA00477 - CORRECT!
Set I/O Voltage reads as 2.80V, 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/0x0001 (000000, 0x0200000000 Bytes)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (000000, 0x0000100000 Bytes)

Flashing the dead body...
WARNING: Programming Error (0x25) at 0x0000000000 is handled as Cut Excess.
ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000)

It's HW problem?
Flash ID detected correctly or not? in other posts i see:
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0001 (VYL00M, 0x03AB400000 Bytes)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x0000080000 Bytes)

**legija** · 03-01-2012, 19:09

Something wrong with phone HW, could be eMMC it self, or maybe power supply chip.

noamlab · 03-09-2012, 15:38

Quote:

Originally Posted by legija

Something wrong with phone HW, could be eMMC it self, or maybe power supply chip.

can u sen pictcher were is the chip?

03-01-2012, 17:46	#1 (permalink)
NSerN No Life Poster Join Date: Jan 2002 Location: Russia Posts: 704 Member: 8599 Status: Offline Thanks Meter: 3	I9100 error resurrection... Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.30, JTAG Manager Version: 1.38 Selected Resurrector: [Samsung i9100] Connecting to the dead body...OK Detected dead body ID: 0x4BA00477 - CORRECT! Set I/O Voltage reads as 2.80V, 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/0x0001 (000000, 0x0200000000 Bytes) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (000000, 0x0000100000 Bytes) Flashing the dead body... WARNING: Programming Error (0x25) at 0x0000000000 is handled as Cut Excess. ERROR: DCC Loader has reported Error Code = 0x3E (0x007FFF <> 0x010000) It's HW problem? Flash ID detected correctly or not? in other posts i see: Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0001 (VYL00M, 0x03AB400000 Bytes) Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0001 (VYL00M, 0x0000080000 Bytes)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
where to find a working program all they have some errors ??	fondas	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	12-12-2012 13:26
My 5110 v5.11 have a strange error.., it resets it self every 60second	luuk	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	24	08-11-2006 15:29
Avoid 3 times error code in Nokia 6185	X-plot	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	05-08-2000 20:24
The multiple errors of Winlock ... ???	Genata	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	09-20-1999 19:12
error (1002) simlock3.dll winopen	fondas	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	08-28-1999 15:57

03-01-2012, 19:09	#2 (permalink)
legija Product Manager Join Date: Apr 2006 Age: 55 Posts: 5,746 Member: 256342 Status: Offline Sonork: None Thanks Meter: 28,276	Something wrong with phone HW, could be eMMC it self, or maybe power supply chip.