Nexus one not ressurected - 0x22

[vazgsm]

hello,


i´ve got here a htc nexus one (pb99100), whose owner claimed it got dead during update, but it doesn´t get download mode, nor can I flash it with riff. connection was resoldered several times to make sure. resurrection finishes succesfully, but sometimes with error 0x22 (didn´t find in faq what´s that error), and in other operations this error appears a lot.

after resurrection phone does not start in download mode (checked main ribbon cable, its ok), and I can´t get to flash a dump on it.


resurrection goes fine:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [HTC Nexus V1.00]

Connecting to the dead body...OK
Detected dead body ID: 0x202400E1 - CORRECT!
Set I/O Voltage reads as 2.60V, 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/0x55BC (512MB)
Flashing the dead body...OK
Resurrection complete!

but if I select to write dump:

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [HTC Nexus V1.00]

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

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

Writting FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x000001000000

at first i thought it was bad soldering, and resoldered all connection 2 or 3 times, lowered rtck down to 200Hz, tried low tck, but error persists, and I´m starting to think there´s something wrong with its hardware, although I didn´t see anything. if was a wiring issue, it wouldn´t complete resurrection with sample at max without errors.

this 0x22 occurs in different ad*******, for instance, one time flashed it got error on 0x0000016A0000, but following try it got error in other ad*******, but not this one.

i´m trying again to write dump at 1MHz (18% so far), but that error is atacking again, don´t think that will be completed.

Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.34, JTAG Manager Version: 1.48
Selected Resurrector: [HTC Nexus V1.00]

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

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

Writting FLASH1 memory from 0x000000000000 to 0x00001FFFFFFF
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
WARNING: Programming Error (0x24) at 0x0000016C0000. Attempting to Repeat.
WARNING: Programming Error (0x24) at 0x0000016C0000 is Ignored.
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
WARNING: Programming Error (0x24) at 0x000002FE0000 is Ignored.
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x22 (0x000000). Trying to recover...OK

Can anyone provide an error description on what´s 0x22? And may I say, it´s NOT "FAILED


br