Samsung S5253 Dead Boot Repair Done But Show error on screen - GSM-Forum

GSMFEROZEPUR · 02-12-2014, 11:15

samsung s5253 dead boot repair done but show eeror on screen i flash it but same ,i m new user ,i need tested domp file $ write dump process

ChandruChiyyan · 02-13-2014, 07:03

What Error came on Display ? No need to write Dump.. post here Error detail's or screen shot .

.::EXTREME::. · 02-13-2014, 07:22

GUIDE

GSMFEROZEPUR · 02-13-2014, 07:29

This Error is show now (http://imageshack.com/a/img198/2659/z4ek.jpg)

ChandruChiyyan · 02-13-2014, 07:32

Did u tryed flash After resurrection ? Or follow extreme Brother Gived Correct way to Recover your phone Just Follow that ways

.

GSMFEROZEPUR · 02-13-2014, 07:33

i m already cheq this steps but same error mr. .::EXTREME::. ,but not sucess show this error http://imageshack.com/a/img198/2659/z4ek.jpg

ChandruChiyyan · 02-13-2014, 07:37

We are Recoved So many phone's That ways or u can contact me private I will try to solve Ur problem .

akhil_bbsr · 02-13-2014, 07:41

boss u need to full erase 3 times in jtag then do boot repair then then Re-flash

GSMFEROZEPUR · 02-13-2014, 12:06

Ho gya H bOSS tHANX To all,but now imei not active

akhil_bbsr · 02-17-2014, 08:24

use spt to do ur imei using modem port

a2zmobile_bhw · 04-19-2015, 07:33

getting error

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)

Erasing FLASH1 memory from 0x000000000000 to 0x00000FFFFFFF...OK
WARNING: Erasing Error (0x24) at 0x000002E00000 is Ignored. Erase continues.
WARNING: Erasing Error (0x24) at 0x0000060C0000 is Ignored. Erase continues.
Completed in 00:00:05.382 (Average Transfer Rate: 48707.54 kB/s)

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung S5250 V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x07926F0F - CORRECT!
Set I/O Voltage reads as 3.00V, 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 = 4KB

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

02-12-2014, 11:15	#1 (permalink)
GSMFEROZEPUR No Life Poster Join Date: Mar 2013 Location: India Age: 29 Posts: 971 Member: 1900418 Status: Offline Sonork: Not Available Yet Thanks Meter: 93	Samsung S5253 Dead Boot Repair Done But Show error on screen samsung s5253 dead boot repair done but show eeror on screen i flash it but same ,i m new user ,i need tested domp file $ write dump process

02-13-2014, 07:22	#3 (permalink)
.::EXTREME::. No Life Poster Join Date: Jul 2011 Location: ۞_ KERALA__۞_INDIA Posts: 3,352 Member: 1619462 Status: Offline Sonork: 100.1606509 Thanks Meter: 1,517	Only way to sucess!!! GUIDE

02-13-2014, 07:03	#2 (permalink)
ChandruChiyyan No Life Poster Join Date: Dec 2007 Location: tamilnadu,india Posts: 1,266 Member: 660093 Status: Offline Sonork: 100.1602344 Thanks Meter: 277	What Error came on Display ? No need to write Dump.. post here Error detail's or screen shot .

02-13-2014, 07:29	#4 (permalink)
GSMFEROZEPUR No Life Poster Join Date: Mar 2013 Location: India Age: 29 Posts: 971 Member: 1900418 Status: Offline Sonork: Not Available Yet Thanks Meter: 93	This Error is show now (http://imageshack.com/a/img198/2659/z4ek.jpg)

02-13-2014, 07:32	#5 (permalink)
ChandruChiyyan No Life Poster Join Date: Dec 2007 Location: tamilnadu,india Posts: 1,266 Member: 660093 Status: Offline Sonork: 100.1602344 Thanks Meter: 277	Did u tryed flash After resurrection ? Or follow extreme Brother Gived Correct way to Recover your phone Just Follow that ways .

02-13-2014, 07:33	#6 (permalink)
GSMFEROZEPUR No Life Poster Join Date: Mar 2013 Location: India Age: 29 Posts: 971 Member: 1900418 Status: Offline Sonork: Not Available Yet Thanks Meter: 93	i m already cheq this steps but same error mr. .::EXTREME::. ,but not sucess show this error http://imageshack.com/a/img198/2659/z4ek.jpg

02-13-2014, 07:37	#7 (permalink)
ChandruChiyyan No Life Poster Join Date: Dec 2007 Location: tamilnadu,india Posts: 1,266 Member: 660093 Status: Offline Sonork: 100.1602344 Thanks Meter: 277	We are Recoved So many phone's That ways or u can contact me private I will try to solve Ur problem .

02-13-2014, 07:41	#8 (permalink)
akhil_bbsr No Life Poster Join Date: May 2006 Location: MOBILE SOFTZONE BHUBANESWAR IN Posts: 3,509 Member: 271478 Status: Offline Sonork: 1590868 Thanks Meter: 1,070	boss u need to full erase 3 times in jtag then do boot repair then then Re-flash

02-13-2014, 12:06	#9 (permalink)
GSMFEROZEPUR No Life Poster Join Date: Mar 2013 Location: India Age: 29 Posts: 971 Member: 1900418 Status: Offline Sonork: Not Available Yet Thanks Meter: 93	Ho gya H bOSS tHANX To all,but now imei not active

02-17-2014, 08:24	#10 (permalink)
akhil_bbsr No Life Poster Join Date: May 2006 Location: MOBILE SOFTZONE BHUBANESWAR IN Posts: 3,509 Member: 271478 Status: Offline Sonork: 1590868 Thanks Meter: 1,070	use spt to do ur imei using modem port

04-19-2015, 07:33	#11 (permalink)
a2zmobile_bhw Banned Join Date: Aug 2011 Location: Bhairahawa_Nepal Posts: 573 Member: 1638066 Status: Offline Thanks Meter: 170	getting error 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) Erasing FLASH1 memory from 0x000000000000 to 0x00000FFFFFFF...OK WARNING: Erasing Error (0x24) at 0x000002E00000 is Ignored. Erase continues. WARNING: Erasing Error (0x24) at 0x0000060C0000 is Ignored. Erase continues. Completed in 00:00:05.382 (Average Transfer Rate: 48707.54 kB/s) Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.37, JTAG Manager Version: 1.56 Selected Resurrector: [Samsung S5250 V1.00] Connecting to the dead body...OK Detected dead body ID: 0x07926F0F - CORRECT! Set I/O Voltage reads as 3.00V, 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 = 4KB Flashing the dead body... ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...OK ERROR: DCC Loader has reported Error Code = 0x30 (0x000000). Trying to recover...OK ERROR: Stopped due to multiple communication errors. Terminating at 0x00001DD00000