Samsung B5722 flashing problem. - GSM-Forum

Edgars 777 · 07-31-2012, 23:33

Hello! I have a problem with the Samsung B5722 firmware flashing.
At the client said: power down by itself and can no longer turn on.
Checked visually under the microscope flashing chips, it seems that there is no problem.
Tried flashing the firmware with UFS and different firmwares, but the master MCU flashing failed. Tried only slave MCU and TFS, writing ok. Read full flash without any problems.
I tried with OneNAND downloader, by DirectCom, but nothing happens. How can you help me? I have only HWK box and USB cable.

Here is a log file.

MCU File: B5722XXJK3_Master.cla CRC32: 872A54DC
TFS File: B5722XXJK3_Master.tfs CRC32: E843D574
CFG File: B5722XXJK3_Master.cfg 190443 byte(s)
CSC File: B5722OXEJK1.csc CRC32: 04750DD1
CCF File: B5722OXEJK1.ccf 28096 byte(s)
MCU File: B5722XXJK3_Slave.clas CRC32: 63E18FA8
TFS File: B5722XXJK3_Slave.tfs CRC32: 03812417
CFG File: B5722XXJK3_Slave.cfg 1005 byte(s)
BBID: 3DF8696018
MCU Id: 3B11, PNX6508/13/16/17
Preloader Ok, 460800 Baud
Flashloader Ok
FLASH Id: 00EC2206000100000034, Samsung KAP29WG00M [NAND 1G]
NAND Format Complete, Time: 00:13
File CRC: 0x872A54DC
Warning, Bad Cks: 0xB4 <> 0xF6, at: 0x00000000
Warning, Bad Cks: 0xB4 <> 0x89, at: 0x00020000
Warning, Bad Cks: 0xB4 <> 0x3F, at: 0x00040000
Warning, Bad Cks: 0xB4 <> 0xB2, at: 0x00060000
Warning, Bad Cks: 0xB4 <> 0x1D, at: 0x00080000
Warning, Bad Cks: 0xB4 <> 0x4A, at: 0x000A0000
Warning, Bad Cks: 0xB4 <> 0x4B, at: 0x000C0000
Warning, Bad Cks: 0xB4 <> 0x08, at: 0x000E0000
Warning, Bad Cks: 0xB4 <> 0xF9, at: 0x00100000
Warning, Bad Cks: 0xB4 <> 0x99, at: 0x00120000
Warning, Bad Cks: 0xB4 <> 0xC2, at: 0x00140000
Warning, Bad Cks: 0xB4 <> 0x48, at: 0x00160000
Warning, Bad Cks: 0xB4 <> 0x73, at: 0x00180000
Warning, Bad Cks: 0xB4 <> 0x6B, at: 0x001A0000
Warning, Bad Cks: 0xB4 <> 0x30, at: 0x001C0000
Warning, Bad Cks: 0xB4 <> 0x3E, at: 0x001E0000
Warning, Bad Cks: 0xB4 <> 0xAD, at: 0x00200000
Warning, Bad Cks: 0xB4 <> 0x89, at: 0x00220000
Warning, Bad Cks: 0xB4 <> 0x4C, at: 0x00240000
Warning, Bad Cks: 0xB4 <> 0x8F, at: 0x00260000
Warning, Bad Cks: 0xB4 <> 0x23, at: 0x00280000
Warning, Bad Cks: 0xB4 <> 0x62, at: 0x002A0000
Warning, Bad Cks: 0xB4 <> 0x5D, at: 0x002C0000
Warning, Bad Cks: 0xB4 <> 0xAA, at: 0x002E0000
Bad Cks Response: 2, 0xB4EC
MCU Write Failed, at: 0x00300000

Edgars 777 · 08-01-2012, 21:46

Does anyone has faced such problems when reading and erasing on this model is ok, but can not record the master chip? Waiting for a solution? I am using E210 RJ45 cable.

07-31-2012, 23:33	#1 (permalink)
Edgars 777 Junior Member Join Date: Mar 2011 Location: Latvia Posts: 8 Member: 1535569 Status: Offline Thanks: 2 Thanked 0 Times in 0 Posts	Samsung B5722 flashing problem. Hello! I have a problem with the Samsung B5722 firmware flashing. At the client said: power down by itself and can no longer turn on. Checked visually under the microscope flashing chips, it seems that there is no problem. Tried flashing the firmware with UFS and different firmwares, but the master MCU flashing failed. Tried only slave MCU and TFS, writing ok. Read full flash without any problems. I tried with OneNAND downloader, by DirectCom, but nothing happens. How can you help me? I have only HWK box and USB cable. Here is a log file. MCU File: B5722XXJK3_Master.cla CRC32: 872A54DC TFS File: B5722XXJK3_Master.tfs CRC32: E843D574 CFG File: B5722XXJK3_Master.cfg 190443 byte(s) CSC File: B5722OXEJK1.csc CRC32: 04750DD1 CCF File: B5722OXEJK1.ccf 28096 byte(s) MCU File: B5722XXJK3_Slave.clas CRC32: 63E18FA8 TFS File: B5722XXJK3_Slave.tfs CRC32: 03812417 CFG File: B5722XXJK3_Slave.cfg 1005 byte(s) BBID: 3DF8696018 MCU Id: 3B11, PNX6508/13/16/17 Preloader Ok, 460800 Baud Flashloader Ok FLASH Id: 00EC2206000100000034, Samsung KAP29WG00M [NAND 1G] NAND Format Complete, Time: 00:13 File CRC: 0x872A54DC Warning, Bad Cks: 0xB4 <> 0xF6, at: 0x00000000 Warning, Bad Cks: 0xB4 <> 0x89, at: 0x00020000 Warning, Bad Cks: 0xB4 <> 0x3F, at: 0x00040000 Warning, Bad Cks: 0xB4 <> 0xB2, at: 0x00060000 Warning, Bad Cks: 0xB4 <> 0x1D, at: 0x00080000 Warning, Bad Cks: 0xB4 <> 0x4A, at: 0x000A0000 Warning, Bad Cks: 0xB4 <> 0x4B, at: 0x000C0000 Warning, Bad Cks: 0xB4 <> 0x08, at: 0x000E0000 Warning, Bad Cks: 0xB4 <> 0xF9, at: 0x00100000 Warning, Bad Cks: 0xB4 <> 0x99, at: 0x00120000 Warning, Bad Cks: 0xB4 <> 0xC2, at: 0x00140000 Warning, Bad Cks: 0xB4 <> 0x48, at: 0x00160000 Warning, Bad Cks: 0xB4 <> 0x73, at: 0x00180000 Warning, Bad Cks: 0xB4 <> 0x6B, at: 0x001A0000 Warning, Bad Cks: 0xB4 <> 0x30, at: 0x001C0000 Warning, Bad Cks: 0xB4 <> 0x3E, at: 0x001E0000 Warning, Bad Cks: 0xB4 <> 0xAD, at: 0x00200000 Warning, Bad Cks: 0xB4 <> 0x89, at: 0x00220000 Warning, Bad Cks: 0xB4 <> 0x4C, at: 0x00240000 Warning, Bad Cks: 0xB4 <> 0x8F, at: 0x00260000 Warning, Bad Cks: 0xB4 <> 0x23, at: 0x00280000 Warning, Bad Cks: 0xB4 <> 0x62, at: 0x002A0000 Warning, Bad Cks: 0xB4 <> 0x5D, at: 0x002C0000 Warning, Bad Cks: 0xB4 <> 0xAA, at: 0x002E0000 Bad Cks Response: 2, 0xB4EC MCU Write Failed, at: 0x00300000

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
thread	Thread Starter	Forum	Replies	Last Post
Sim card sleep mode problem with 6130	ratzfatz	Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L )	4	05-22-2012 11:13
Seeking for flash nokia 5110 old version (3 version) can exchange for new	Tomas	Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L )	7	11-17-2011 17:08
need to flash 6110	paulomt1	Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L )	0	08-16-1999 12:20
HELP: Problem with 5110	Xabi	Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L )	1	07-16-1999 00:44
5110 flash new software , need help	steve	Nokia Legacy Phones ( DCT-1 , DCT-2 , DCT-3 , DCT-L )	2	07-07-1999 12:27

08-01-2012, 21:46	#2 (permalink)
Edgars 777 Junior Member Join Date: Mar 2011 Location: Latvia Posts: 8 Member: 1535569 Status: Offline Thanks: 2 Thanked 0 Times in 0 Posts	Does anyone has faced such problems when reading and erasing on this model is ok, but can not record the master chip? Waiting for a solution? I am using E210 RJ45 cable.