problem flashing se w595 with a2uploader

hey! i have problem with a2 uploader ! when i try to flas pfone its stops and then shows up this log! ChipID:C900,EMP protocol:0401
PHONE STATE: "RETAIL"
FLASH CID: 0052
OTP LOCKED:1 CID:52 PAF:1 IMEI:35526403352550 CERT:RED
LDR:2008-07-23 12:02 CXC1250779_DB31XX_EXPLORER_LOADER_APP_SDRAM_R2A065
LDR CAPS:SYSTEM FLASH GDFS FILESYSTEM TA
LDR:2009-04-21 18:09 CXC1250843_DB31XX_CS_LOADER_ACC_SDRAM_R2A081
LDR CAPS:SYSTEM FLASH SIGNATURE AUTH
writing "D:\Documents and Settings\kasis\Desktop\radio\a22222222222\W595_R3E A037_FS_BALTIC_RED52.fbn"
ALLOWED DOMAINS:BLUE BROWN RED
MAXIMUM CID:52
Will flash 616 blocks...
block (843E0000/00010000) not accepted,error:3B
Elapsed:58 secs.

what is the answer of that problem? please help! i tried to flash with many FS files but always the same message comes up!

1 month earlier i flashed this pfone and all goes well and it worked but now i cant flash!

try moving the file into another drive partition and also try to flash both the MAIN, FS and custpack

try moving the file into another drive partition....... how to do that?

also try to flash both the MAIN, FS and custpack i also tried that and 1 month earlier i flashed phone with MAIN FS and CUSTpack and then all goes well!

also with this phone i have this problem hoope its helps you to find the answer! when i tried to connect phone to filesystem tool in a2 uploader the phone doesnt connect and after a long time when the program is tring to start file system shows this log
ChipID:C900,EMP protocol:0401
PHONE STATE: "RETAIL"
FLASH CID: 0052
OTP LOCKED:1 CID:52 PAF:1 IMEI:35526403352550 CERT:RED
LDR:2008-07-23 12:02 CXC1250779_DB31XX_EXPLORER_LOADER_APP_SDRAM_R2A065
LDR CAPS:SYSTEM FLASH GDFS FILESYSTEM TA
LDR:2009-04-21 18:09 CXC1250843_DB31XX_CS_LOADER_ACC_SDRAM_R2A081
LDR CAPS:SYSTEM FLASH SIGNATURE AUTH
[startFS] can't get NET header
Elapsed:313 secs.

Flash chip is damaged.Take the phone to some repair shop.

and there aro other ways to fix that?

Quote:

---

Originally Posted by kasens122

and there aro other ways to fix that?

---

No,it is hardware problem.

I also have the same problem :(