Samsung i5503 Problem!!!

[andyvikas]

I received one i5503,
Problem is that i am able to complete Resurrection, but unable to flash it with odin afterwards!!!

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

Connecting to the dead body...OK
Detected dead body ID: 0x203C10E1 - CORRECT!
Set I/O Voltage reads as 2.61V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at 8 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: 0x00EC/0x0050 (512MB)
Flashing the dead body...OK
Resurrection complete!

The following is the odin log..

Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.

it stops here!!! No further progress!!!

Can some one guide!!!

Thanks

[BABAK NURI]

Hi
You have a dl mode?
--------------
Also,You can repair via dump file

[andyvikas]

Earlier it was going into DL mode but after too many attempts now its showing no signs!!!

History:
Set was working well.
Flashed earlier with similar version, set worked correctly.
I tried upgrading Android version.

Here comes the problem!!
Set stuck on android logo which comes after Samsung Welcome screen!!
Tried flashing back to previous versions, but it didn't helped, set remained in same condition.

Decided to resurrect it, Here comes the above problem...
Now when i tried to Full erase it!! the following error i get

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

Connecting to the dead body...OK
Detected dead body ID: 0x203C10E1 - CORRECT!
Set I/O Voltage reads as 2.61V, TCK Frequency is RTCK
Adaptive Clocking RTCK Sampling is: [Sample at MAX]
Settings Code: 0x05010000000000000000000020000000

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/0x0050 (512MB)

Erasing FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF...OK
WARNING: Erasing Error (0x24) at 0x00000E080000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00000E080000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00000E080000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00000E080000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00000E080000 is Ignored. Erase continues.
WARNING: Erasing Error (0x24) at 0x00001A800000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00001A800000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00001A800000. Attempt to Repeat again.
WARNING: Erasing Error (0x24) at 0x00001A800000 is Ignored. Erase continues.
Completed in 00:00:25.281 (Average Transfer Rate: 20738.42 kB/s)

Flash chip is glue mounted!!
How to proceed further??

Thanks

[andyvikas]

OK got through FAQ

Error code 0x24

Now can we have a details on

Automatically Chose Bad Block Handling Method
Cut Excess
Overlap

Please can some one throw some light on above these methods for handling bad blocks!!

Is there exists any specific Technique using which few block can be marked as BAD & Hence can be skipped, so that the flash write can continue only on good blocks & i can get this set back to life??

Thanks