error will repair s5360 with easyjitag - GSM-Forum

shnory · 01-20-2014, 17:39

Repair File ver. : Easy Repair for Mfg: SAMSUNG Model: GT-S5360, Ver.: 1.00
Error loading information!
Easy-Repair file load OK!
Using EasyRepair Mode...
Checking repair data...
EasyJtag Suite ver.: 1.0.98.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-S5360 Config ver.:1.00
I/O Level set to : 3000 mV
Box S/N: ********* ,FW Ver.: 01.48
Connecting to Target...
JTAG device: BCM21553
CPU IDCODE : 0x07B3617F Mfg.: 0x0bf, Part: 0x7b36, Ver.: 0x0
CPU Manufacturer: SST/Broadcom , CPU Name: BCM21553
Halting CPU...
Using EasyRepair Mode...
Checking repair data...
EasyJtag Suite ver.: 1.0.98.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-S5360 Config ver.:1.00
I/O Level set to : 3000 mV
Box S/N: 1************ ,FW Ver.: 01.48
Connecting to Target...
Done with error(s)...
Using EasyRepair Mode...
Checking repair data...
EasyJtag Suite ver.: 1.0.98.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-S5360 Config ver.:1.00
I/O Level set to : 3000 mV
Box S/N: *************,FW Ver.: 01.48
Connecting to Target...
Done with error(s)...
Using EasyRepair Mode...
Checking repair data...
EasyJtag Suite ver.: 1.0.98.0 started.
Operating system ver.: Windows XP (build 2600, Service Pack 3).
For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device.
Initialising: SAMSUNG GT-S5360 Config ver.:1.00
I/O Level set to : 3000 mV
Box S/N: ************,FW Ver.: 01.48
Connecting to Target...
JTAG device: BCM21553
CPU IDCODE : 0x07B3617F Mfg.: 0x0bf, Part: 0x7b36, Ver.: 0x0
CPU Manufacturer: SST/Broadcom , CPU Name: BCM21553
Halting CPU...
Initialize hardware...
Starting target communication...
Detecting nand memory parameters ...
NAND flash device ID:00EC:0050 'NAND 512MB 1.8V 16-bit (Samsung)' found
NAND geometry: Blocks:00000800, Page size:4096 bytes , Block size:64 pages
NAND Writing BCM_BOOT...
NAND Write OK! Elapsed time: 2.046875s (128.977 KiB/s)
NAND Writing SBL1...
Packet length too large: 0xFFFFFFFF
Unknown DCC answer /PROTOCOL/
Failed writing file SBL1.BIN to NAND flash 0 at offset 0x00080000 code# -253
NAND Writing SBL2...
Packet length too large: 0xFFFFFFFF
Unknown DCC answer /PROTOCOL/
Failed writing file SBL2.BIN to NAND flash 0 at offset 0x00240000 code# -253
NAND Writing PIT...
Packet length too large: 0xFFFFFFFF
Unknown DCC answer /PROTOCOL/
Failed writing file PIT.BIN to NAND flash 0 at offset 0x00440000 code# -253
NAND Writing UPCH...
Packet length too large: 0xFFFFFFFF
Unknown DCC answer /PROTOCOL/
Failed writing file UPCH.BIN to NAND flash 0 at offset 0x1FF00000 code# -253
All Done.
Error. Please select init first.

=============================================
thats what happend whiout connecting usb cable to the phone
when i connect its never connct and give me Done with error(s)...

lunno · 01-21-2014, 20:42

double check the wire solders and use Usb cable, don't forget the battery.

shnory · 01-24-2014, 18:13

i did all of that and no way
customer take it back he came to me every 30 minute (:

01-20-2014, 17:39	#1 (permalink)
shnory Major Poster Join Date: Nov 2006 Location: egypt Age: 45 Posts: 46 Member: 391263 Status: Offline Thanks Meter: 3	error will repair s5360 with easyjitag Repair File ver. : Easy Repair for Mfg: SAMSUNG Model: GT-S5360, Ver.: 1.00 Error loading information! Easy-Repair file load OK! Using EasyRepair Mode... Checking repair data... EasyJtag Suite ver.: 1.0.98.0 started. Operating system ver.: Windows XP (build 2600, Service Pack 3). For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device. Initialising: SAMSUNG GT-S5360 Config ver.:1.00 I/O Level set to : 3000 mV Box S/N: ******* ,FW Ver.: 01.48 Connecting to Target... JTAG device: BCM21553 CPU IDCODE : 0x07B3617F Mfg.: 0x0bf, Part: 0x7b36, Ver.: 0x0 CPU Manufacturer: SST/Broadcom , CPU Name: BCM21553 Halting CPU... Using EasyRepair Mode... Checking repair data... EasyJtag Suite ver.: 1.0.98.0 started. Operating system ver.: Windows XP (build 2600, Service Pack 3). For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device. Initialising: SAMSUNG GT-S5360 Config ver.:1.00 I/O Level set to : 3000 mV Box S/N: 1******** ,FW Ver.: 01.48 Connecting to Target... Done with error(s)... Using EasyRepair Mode... Checking repair data... EasyJtag Suite ver.: 1.0.98.0 started. Operating system ver.: Windows XP (build 2600, Service Pack 3). For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device. Initialising: SAMSUNG GT-S5360 Config ver.:1.00 I/O Level set to : 3000 mV Box S/N: *********,FW Ver.: 01.48 Connecting to Target... Done with error(s)... Using EasyRepair Mode... Checking repair data... EasyJtag Suite ver.: 1.0.98.0 started. Operating system ver.: Windows XP (build 2600, Service Pack 3). For support and updates visit EasyJtag , just better ? - New powerful JTAG unbrick device. Initialising: SAMSUNG GT-S5360 Config ver.:1.00 I/O Level set to : 3000 mV Box S/N: *********,FW Ver.: 01.48 Connecting to Target... JTAG device: BCM21553 CPU IDCODE : 0x07B3617F Mfg.: 0x0bf, Part: 0x7b36, Ver.: 0x0 CPU Manufacturer: SST/Broadcom , CPU Name: BCM21553 Halting CPU... Initialize hardware... Starting target communication... Detecting nand memory parameters ... NAND flash device ID:00EC:0050 'NAND 512MB 1.8V 16-bit (Samsung)' found NAND geometry: Blocks:00000800, Page size:4096 bytes , Block size:64 pages NAND Writing BCM_BOOT... NAND Write OK! Elapsed time: 2.046875s (128.977 KiB/s) NAND Writing SBL1... Packet length too large: 0xFFFFFFFF Unknown DCC answer /PROTOCOL/ Failed writing file SBL1.BIN to NAND flash 0 at offset 0x00080000 code# -253 NAND Writing SBL2... Packet length too large: 0xFFFFFFFF Unknown DCC answer /PROTOCOL/ Failed writing file SBL2.BIN to NAND flash 0 at offset 0x00240000 code# -253 NAND Writing PIT... Packet length too large: 0xFFFFFFFF Unknown DCC answer /PROTOCOL/ Failed writing file PIT.BIN to NAND flash 0 at offset 0x00440000 code# -253 NAND Writing UPCH... Packet length too large: 0xFFFFFFFF Unknown DCC answer /PROTOCOL/ Failed writing file UPCH.BIN to NAND flash 0 at offset 0x1FF00000 code# -253 All Done. Error. Please select init first. ============================================= thats what happend whiout connecting usb cable to the phone when i connect its never connct and give me Done with error(s)... Last edited by shnory; 01-20-2014 at 17:46.*

01-21-2014, 20:42	#2 (permalink)
lunno Freak Poster Join Date: Dec 2012 Location: Brazil Posts: 216 Member: 1859706 Status: Offline Sonork: 100.1648492 Thanks Meter: 28	double check the wire solders and use Usb cable, don't forget the battery.

01-24-2014, 18:13	#3 (permalink)
shnory Major Poster Join Date: Nov 2006 Location: egypt Age: 45 Posts: 46 Member: 391263 Status: Offline Thanks Meter: 3	i did all of that and no way customer take it back he came to me every 30 minute (: