s5380 needed resurrection file - GSM-Forum

sukizg · 08-18-2012, 11:46

Hi there , i just need s5380 dll resurrection file,thank you in advance

sukizg · 08-18-2012, 11:54

Connecting to the target...OK
Set I/O Voltage reads as 2.80V, TCK Frequency is RTCK

Following devices are found on the JTAG chain:
Device on TAP #0: ID = 0x07B3617F, IR Length = 0x05 bits
Device on TAP #1: ID = 0x07B3617F, IR Length = 0x05 bits
Total IR length: 0x000A bits

BABAK NURI · 08-23-2012, 23:52

Hi
please download dump file from riff-tracker..Then write dump file

sukizg · 08-24-2012, 08:45

[IMG]

[/IMG]

another problem here...
not able to recognized flash chip size...it is 512 mb so i used this data lenght, problem is still here is this hardware issue???
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung S5360 V1.0.4443.1900]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - CORRECT!
Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz
Settings Code: 0x2401060E000000000000000020000000

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: 0x0000/0xFFFF

ERROR: Cannot Automatically Determine the Selected FLASH1 Chip's size. Terminating.

sukizg · 08-24-2012, 09:56

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung S5360 V1.0.4443.1900]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - CORRECT!
Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz
Settings Code: 0x31010600000000000000000020000000

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: 0x0000/0xFFFF

Writting FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF
ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000000000000

BABAK NURI · 08-24-2012, 13:48

Hi sukizg
----
Plesae Check Connection...Also Power and Usb Cable

sukizg · 08-24-2012, 16:18

al checked Sir here are logs :

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung S5360 V1.0.4443.1900]

Connecting to the target...OK
Set I/O Voltage reads as 3.00V, TCK Frequency is 1 MHz

Following devices are found on the JTAG chain:
Device on TAP #0: ID = 0x07B3617F, IR Length = 0x05 bits
Device on TAP #1: ID = 0x07B3617F, IR Length = 0x05 bits
Total IR length: 0x000A bits

when i try to ERASE I GET THIS

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung S5360 V1.0.4443.1900]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - CORRECT!
Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz
Settings Code: 0x0901060000000000000000001FFFFFFF

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: 0x0000/0xFFFF

Looking for the RIFF BOX DCCLoader USB Interface Port...FAILED
The DCCLoader USB Interface is not found. Communication continues over the DCC Interface

Erasing FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF...ERROR
WARNING: Erasing Error (0x30) at 0x000000000000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000040000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000080000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000000C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000100000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000140000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000180000 is Ignored. Erase continues.
ERROR: Erase failed with Error Code: 0x30. Terminating at 0x0000001C0000

BABAK NURI · 08-24-2012, 23:18

Hi
Plaese deselect "DCC Loader USB Interface"
Speed at max or 6Mhz
Remove USB Cable form phone
Hold and Keep Power On Key
Press "Erase",and select "Ignore" if you see again

sukizg · 08-25-2012, 10:08

thank you Sir , i really respect your work, but no use:
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.33, JTAG Manager Version: 1.44
Selected Resurrector: [Samsung S5360 V1.0.4443.1900]

Connecting to the dead body...OK
Detected dead body ID: 0x07B3617F - IGNORED!
Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz
Settings Code: 0x01010600000000000000000020000000

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: 0x0000/0xFFFF

Erasing FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF...ERROR
WARNING: Erasing Error (0x30) at 0x000000000000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000040000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000080000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000000C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000100000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000140000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000180000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000001C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000200000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000240000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000280000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000002C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000300000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000340000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000380000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000003C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000400000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000440000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000480000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000004C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000500000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000540000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000580000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000005C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000600000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000640000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000680000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000006C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000700000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000740000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000780000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000007C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000800000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000840000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000880000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000008C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000900000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000940000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000980000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000009C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000A00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000A40000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000A80000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000AC0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000B00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000B40000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000B80000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000BC0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000C00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000C40000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000C80000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000CC0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000D00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000D40000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000D80000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000DC0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000E00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000E40000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000E80000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000EC0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000F00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000F40000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000F80000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000000FC0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001000000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001040000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001080000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000010C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001100000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001140000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001180000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000011C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001200000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001240000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001280000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000012C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001300000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001340000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001380000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000013C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001400000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001440000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001480000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000014C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001500000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001540000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001580000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000015C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001600000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001640000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001680000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000016C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001700000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001740000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001780000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x0000017C0000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001800000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001840000 is Ignored. Erase continues.
WARNING: Erasing Error (0x30) at 0x000001880000 is Ignored. Erase continues.
Failed to Send the ERASE command.

sukizg · 10-19-2012, 04:51

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.45
Selected Resurrector: [Samsung S5380D V1.0.4669.16283]
Restarting target (nRST Low then High)...OK

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

Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...FAILED
ERROR: Failed due to multiple communication errors. Terminating at 0x000000000000

dragancexz · 11-26-2012, 13:44

your problem is in the wrong model, in picture that you upload, you tryin to resurect s5360 with dump of s5380d, first check the model what you want to resurect.

Also I need a dump for ordinary s5380.dll for riff , Is there any can help me?

samsung s5380 dead boot, not solve with s5380d resurect

muxdan · 12-19-2012, 19:57

s5380 flash sildikten sonra repair boot yapamadım..
ne yaptıysam olmadı .
son çare dll. dosyalarını indirdim ve s7250d.dll dosyası ile repair boot yapabildim.
yapmayanlar için paylaşmak istedim

muxdan · 12-19-2012, 19:57

I could not repair boot s5380 flash after deleting ..
what I do not.
dll is a last resort. repair boot files with the file I downloaded and s7250d.dll could do.
I wanted to share for those who are not

shofiqul36 · 12-26-2012, 16:41

samsung s5380 resurection ok but not download mode on

tikuh · 12-26-2012, 17:51

try desolder, check point, try res using full charge battery..

08-18-2012, 11:46	#1 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	s5380 needed resurrection file Hi there , i just need s5380 dll resurrection file,thank you in advance

08-24-2012, 08:45	#4 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	[IMG][/IMG] another problem here... not able to recognized flash chip size...it is 512 mb so i used this data lenght, problem is still here is this hardware issue??? Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [Samsung S5360 V1.0.4443.1900] Connecting to the dead body...OK Detected dead body ID: 0x07B3617F - CORRECT! Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz Settings Code: 0x2401060E000000000000000020000000 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: 0x0000/0xFFFF ERROR: Cannot Automatically Determine the Selected FLASH1 Chip's size. Terminating. Last edited by sukizg; 08-24-2012 at 08:51.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
need ericsson 88 cable	migdamas	Old Ericsson Phones & Sony Phones	2	03-24-2017 16:24
Need software upgrade for Nokia 5110	ptkrf	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	30	02-24-2016 10:21
needed pinout for carkit(N61xx)	mobileinfo	Nokia Hardware & Hardware Repair	2	07-23-2013 02:41
Eeprom dump lost, help needed.	CAMILO	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	6	11-29-2010 19:04
need eeprom photo????	mobileinfo	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	05-26-1999 11:35

08-18-2012, 11:54	#2 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	Connecting to the target...OK Set I/O Voltage reads as 2.80V, TCK Frequency is RTCK Following devices are found on the JTAG chain: Device on TAP #0: ID = 0x07B3617F, IR Length = 0x05 bits Device on TAP #1: ID = 0x07B3617F, IR Length = 0x05 bits Total IR length: 0x000A bits

08-23-2012, 23:52	#3 (permalink)
BABAK NURI Product Supporter Join Date: Mar 2005 Location: Tehran.IR Age: 43 Posts: 7,259 Member: 131131 Status: Offline Sonork: 100.1606847 Thanks Meter: 4,475	Hi please download dump file from riff-tracker..Then write dump file

08-24-2012, 09:56	#5 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [Samsung S5360 V1.0.4443.1900] Connecting to the dead body...OK Detected dead body ID: 0x07B3617F - CORRECT! Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz Settings Code: 0x31010600000000000000000020000000 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: 0x0000/0xFFFF Writting FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...FAILED ERROR: Failed due to multiple communication errors. Terminating at 0x000000000000

08-24-2012, 13:48	#6 (permalink)
BABAK NURI Product Supporter Join Date: Mar 2005 Location: Tehran.IR Age: 43 Posts: 7,259 Member: 131131 Status: Offline Sonork: 100.1606847 Thanks Meter: 4,475	Hi sukizg ---- Plesae Check Connection...Also Power and Usb Cable

08-24-2012, 16:18	#7 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	al checked Sir here are logs : Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [Samsung S5360 V1.0.4443.1900] Connecting to the target...OK Set I/O Voltage reads as 3.00V, TCK Frequency is 1 MHz Following devices are found on the JTAG chain: Device on TAP #0: ID = 0x07B3617F, IR Length = 0x05 bits Device on TAP #1: ID = 0x07B3617F, IR Length = 0x05 bits Total IR length: 0x000A bits when i try to ERASE I GET THIS Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [Samsung S5360 V1.0.4443.1900] Connecting to the dead body...OK Detected dead body ID: 0x07B3617F - CORRECT! Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz Settings Code: 0x0901060000000000000000001FFFFFFF 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: 0x0000/0xFFFF Looking for the RIFF BOX DCCLoader USB Interface Port...FAILED The DCCLoader USB Interface is not found. Communication continues over the DCC Interface Erasing FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF...ERROR WARNING: Erasing Error (0x30) at 0x000000000000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000040000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000080000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000000C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000100000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000140000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000180000 is Ignored. Erase continues. ERROR: Erase failed with Error Code: 0x30. Terminating at 0x0000001C0000

08-24-2012, 23:18	#8 (permalink)
BABAK NURI Product Supporter Join Date: Mar 2005 Location: Tehran.IR Age: 43 Posts: 7,259 Member: 131131 Status: Offline Sonork: 100.1606847 Thanks Meter: 4,475	Hi Plaese deselect "DCC Loader USB Interface" Speed at max or 6Mhz Remove USB Cable form phone Hold and Keep Power On Key Press "Erase",and select "Ignore" if you see again

08-25-2012, 10:08	#9 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	thank you Sir , i really respect your work, but no use: Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.33, JTAG Manager Version: 1.44 Selected Resurrector: [Samsung S5360 V1.0.4443.1900] Connecting to the dead body...OK Detected dead body ID: 0x07B3617F - IGNORED! Set I/O Voltage reads as 3.01V, TCK Frequency is 1 MHz Settings Code: 0x01010600000000000000000020000000 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: 0x0000/0xFFFF Erasing FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF...ERROR WARNING: Erasing Error (0x30) at 0x000000000000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000040000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000080000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000000C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000100000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000140000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000180000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000001C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000200000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000240000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000280000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000002C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000300000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000340000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000380000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000003C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000400000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000440000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000480000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000004C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000500000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000540000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000580000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000005C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000600000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000640000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000680000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000006C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000700000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000740000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000780000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000007C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000800000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000840000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000880000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000008C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000900000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000940000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000980000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000009C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000A00000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000A40000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000A80000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000AC0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000B00000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000B40000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000B80000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000BC0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000C00000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000C40000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000C80000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000CC0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000D00000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000D40000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000D80000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000DC0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000E00000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000E40000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000E80000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000EC0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000F00000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000F40000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000F80000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000000FC0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001000000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001040000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001080000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000010C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001100000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001140000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001180000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000011C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001200000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001240000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001280000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000012C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001300000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001340000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001380000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000013C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001400000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001440000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001480000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000014C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001500000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001540000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001580000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000015C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001600000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001640000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001680000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000016C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001700000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001740000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001780000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x0000017C0000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001800000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001840000 is Ignored. Erase continues. WARNING: Erasing Error (0x30) at 0x000001880000 is Ignored. Erase continues. Failed to Send the ERASE command.

10-19-2012, 04:51	#10 (permalink)
sukizg Insane Poster Join Date: Aug 2008 Posts: 73 Member: 833123 Status: Offline Thanks Meter: 3	Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.45 Selected Resurrector: [Samsung S5380D V1.0.4669.16283] Restarting target (nRST Low then High)...OK Connecting to the dead body...OK Detected dead body ID: 0x07B3617F - CORRECT! Set I/O Voltage reads as 3.01V, TCK Frequency is 1 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: 0x0000/0xFFFF Selected Resurrection Data for the NAND Chip with Page size = 4KB Flashing the dead body... ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...FAILED ERROR: Failed due to multiple communication errors. Terminating at 0x000000000000

11-26-2012, 13:44	#11 (permalink)
dragancexz Junior Member Join Date: Mar 2008 Location: Serbia Posts: 4 Member: 731262 Status: Offline Thanks Meter: 0	your problem is in the wrong model, in picture that you upload, you tryin to resurect s5360 with dump of s5380d, first check the model what you want to resurect. Also I need a dump for ordinary s5380.dll for riff , Is there any can help me? samsung s5380 dead boot, not solve with s5380d resurect

12-19-2012, 19:57	#12 (permalink)
muxdan Junior Member Join Date: Oct 2006 Posts: 12 Member: 366143 Status: Offline Thanks Meter: 0	s5380 flash sildikten sonra repair boot yapamadım.. ne yaptıysam olmadı . son çare dll. dosyalarını indirdim ve s7250d.dll dosyası ile repair boot yapabildim. yapmayanlar için paylaşmak istedim

12-19-2012, 19:57	#13 (permalink)
muxdan Junior Member Join Date: Oct 2006 Posts: 12 Member: 366143 Status: Offline Thanks Meter: 0	I could not repair boot s5380 flash after deleting .. what I do not. dll is a last resort. repair boot files with the file I downloaded and s7250d.dll could do. I wanted to share for those who are not

12-26-2012, 16:41	#14 (permalink)
shofiqul36 Freak Poster Join Date: Feb 2012 Location: dhaka Age: 36 Posts: 211 Member: 1724593 Status: Offline Sonork: 100.1671528 Thanks Meter: 48	samsung s5380 resurection ok but not download mode on

12-26-2012, 17:51	#15 (permalink)
tikuh Insane Poster Join Date: Jul 2007 Posts: 84 Member: 538559 Status: Offline Thanks Meter: 6	try desolder, check point, try res using full charge battery..