ROM content regenaration fail

[redseaksa]

Hi,
I got WD32000AAJS-00l7a0 with PCB problem (error status) .
I used donor PCB same model ,after Loading from HDD(load management) with low speed SA Access Method I got the LBA =0 head =3 .
What I done :1-Backup module 0102,0103,0105,0107 and 0109 (Low-Speed SA-Access Method)
2-Generate ROM using the upper modules.
3-After rester I got PCB status error .
3-After reset status (PCB) with HD Doctor for WD v6.0.
status (Error) with HD Doctor for WD v5.0
Pls any Advice

[Amarbir[CDR-Labs]]

very interesting ,
what does salvation say on this .as you have a clear copy of the modules rom generation should be done .assuming there is no bug in the software.i have done this in many drives but even i am paused with one issue as i have posted that

[pcimage]

Check your original PCB, does it have ROM @ U12?

And check the contents of the mods you copied off, do any contain the words "NOT INIT"?

[Tawfeek]

your native pcb is 1590 with rom and the one your replaced maybe have rom (U12) ? if the one you replace have rom you can't generate rom with salvation tools from modules . you have to swap the U12 from the original pcb to the donor pcb or flah the U12 ic with programmer

[einstein9]

your native pcb is 1590 with rom and the one your replaced maybe have rom (U12) ? if the one you replace have rom you can't generate rom with salvation tools from modules . you have to swap the U12 from the original pcb to the donor pcb or flah the U12 ic with programmer

[pcimage]

your native pcb is 1590 with rom and the one your replaced maybe have rom (U12) ? if the one you replace have rom you can't generate rom with salvation tools from modules . you have to swap the U12 from the original pcb to the donor pcb or flah the U12 ic with programmer

Just what I was hinting at, without "spoon feeding"

[Amarbir[CDR-Labs]]

your native pcb is 1590 with rom and the one your replaced maybe have rom (U12) ? if the one you replace have rom you can't generate rom with salvation tools from modules . you have to swap the U12 from the original pcb to the donor pcb or flah the U12 ic with programmer

Just what I was hinting at, without "spoon feeding"

Sean ,
Haa Haa What a Clarification .Help Me Also in the Rom Case ,Its Posted Here Itself

[Tawfeek]

your native pcb is 1590 with rom and the one your replaced maybe have rom (U12) ? if the one you replace have rom you can't generate rom with salvation tools from modules . you have to swap the U12 from the original pcb to the donor pcb or flah the U12 ic with programmer

Just what I was hinting at, without "spoon feeding"

you are all right on this one . some times i become Emotional

[Tawfeek]

your native pcb is 1590 with rom and the one your replaced maybe have rom (U12) ? if the one you replace have rom you can't generate rom with salvation tools from modules . you have to swap the U12 from the original pcb to the donor pcb or flah the U12 ic with programmer

you totally right . it's all about the fishing not about the fish

[fzabkar]

I notice that in other forums people are reporting that some ROYL drives don't have MOD 107, and that this prevents SD's tool from rebuilding the ROM. Assuming the other MODs are OK, then AFAICS it should be possible to reconstruct the ROM image using the MOD 0B data embedded within MOD 109, near the end, just before MOD 0A. In fact I believe that I could do it by hand. If that's too difficult for you, then you could easily convert ROM MOD 0B to SA MOD 107 by recomputing its length and checksum bytes, and then padding the sector with zeros. I could do that for you as well.

[fzabkar]

Here is an example where several MODs are "NOT INIT":
http://files.hddguru.com/download/Non-P ... 0472370.7z