Hello,
I had WD20NMVW-11C3NS2 with USB Interface PCB 2060-800041. Changed to compatible 2060-800022. After connecting It comes to Ready State but gets to BSY on HDD ID. I Have tried Isolating head contacts from PCB but it remains BSY only.
Please provide Read Channel points which to short to get to SA access.
thank you all
READ Channel 0n 2060-800022 PCB
Moderator: Maxim_TS
- murtazabawa
- Newbie
- Posts: 21
- Joined: 03.08.16
- Reputation: 1 / (13)
- DataMedics
- Advanced user
- Posts: 619
- Joined: 14.12.15
- Reputation: 18 / (177)
Re: READ Channel 0n 2060-800022 PCB
Just block SA access in ROM then upload LDR. That'll get you SA access.
- murtazabawa
- Newbie
- Posts: 21
- Joined: 03.08.16
- Reputation: 1 / (13)
Re: READ Channel 0n 2060-800022 PCB
Thanks DataMedics for your reply,
But how can I block SA access in ROM without getting into the utility.
Autodetect does not work. I have 6.1x version, will I be able to solve it in this version.
Quick help would be greatly appreciated as client has some episodes which has to go on air.
But how can I block SA access in ROM without getting into the utility.
Autodetect does not work. I have 6.1x version, will I be able to solve it in this version.
Quick help would be greatly appreciated as client has some episodes which has to go on air.
Re: READ Channel 0n 2060-800022 PCB
Strange that you can't enter utility with head isolation. That should work as long as the PCB is good. Make certain you're entering utility in kernel mode. Of course, remember to copy the patient ROM to donor board. If it still doesn't work then you should try a different donor. By the way, what is the original problem with the patient drive? Sometimes terminal access with original PCB can solve some simple issues.
- DataMedics
- Advanced user
- Posts: 619
- Joined: 14.12.15
- Reputation: 18 / (177)
Re: READ Channel 0n 2060-800022 PCB
Have you tried to read the ROM via boot rom code? You should be able to disable SA access that way if all else fails.
- Amarbir[CDR-Labs]
- Advanced user
- Posts: 784
- Joined: 03.08.09
- Reputation: 8 / (80)
Re: READ Channel 0n 2060-800022 PCB
Well,
I think he has not shifted patient ROM to donor SATA Board
I think he has not shifted patient ROM to donor SATA Board
Regards
Amarbir S Dhillon ,CDR Labs [ Chandigarh ,India ]
DataRecovery - The Affordable Way In India
Visit - > http://www.chandigarhdatarecovery.com My Facebook - > https://www.facebook.com/chandigarhdatarecovery
Amarbir S Dhillon ,CDR Labs [ Chandigarh ,India ]
DataRecovery - The Affordable Way In India
Visit - > http://www.chandigarhdatarecovery.com My Facebook - > https://www.facebook.com/chandigarhdatarecovery
Re: READ Channel 0n 2060-800022 PCB
Dear Sir
patient ROM to doner Pcb shiped but bsy ( only pcb ) contted hdd bsy hdd no Sping - usb pcb and hdd conteted hdd sping ?
patient ROM to doner Pcb shiped but bsy ( only pcb ) contted hdd bsy hdd no Sping - usb pcb and hdd conteted hdd sping ?
Best regards,
Vijayan MBA
Raminfotech Data Recovery
http://www.raminfotechdatarecovery.com
call 7092114411/22
sky:raminfotech.vijayan
whatup:9841983643 / 46
Vijayan MBA
Raminfotech Data Recovery
http://www.raminfotechdatarecovery.com
call 7092114411/22
sky:raminfotech.vijayan
whatup:9841983643 / 46
Re: READ Channel 0n 2060-800022 PCB
Does it get ready eventually if you connect just PCB for 15-30 mins?
Re: READ Channel 0n 2060-800022 PCB
Dear Sir
PCB LONG TIME WAIT CONNECT BUT BSY NOT COME TO READY HDD NOT SPING BUT CLINT HDD USB 3 BOAD CONNECT HDD SPING .
SATA PCB WITH CLINT ROM BUT HDD NOT SPING
, ONLY SATA BOARD CONNCET BSY KERNEL MODE WORKING SA BLACK AFTER HDD CONNECT NO SPING ?
USB 3 BOARD 2060-800041-003REV P1
SATA BOARD 2060-800041-002REV ( THIS SATA PCB 3 TB HDD ONE CASE SOLVED 100 % RECOVERY ]
PCB LONG TIME WAIT CONNECT BUT BSY NOT COME TO READY HDD NOT SPING BUT CLINT HDD USB 3 BOAD CONNECT HDD SPING .
SATA PCB WITH CLINT ROM BUT HDD NOT SPING
, ONLY SATA BOARD CONNCET BSY KERNEL MODE WORKING SA BLACK AFTER HDD CONNECT NO SPING ?
USB 3 BOARD 2060-800041-003REV P1
SATA BOARD 2060-800041-002REV ( THIS SATA PCB 3 TB HDD ONE CASE SOLVED 100 % RECOVERY ]
Best regards,
Vijayan MBA
Raminfotech Data Recovery
http://www.raminfotechdatarecovery.com
call 7092114411/22
sky:raminfotech.vijayan
whatup:9841983643 / 46
Vijayan MBA
Raminfotech Data Recovery
http://www.raminfotechdatarecovery.com
call 7092114411/22
sky:raminfotech.vijayan
whatup:9841983643 / 46
- DataMedics
- Advanced user
- Posts: 619
- Joined: 14.12.15
- Reputation: 18 / (177)
Re: READ Channel 0n 2060-800022 PCB
OK, so there seems to be an issue here relating to the PebbleB / Spyglass families. From what I understand, the difference relates to the size of the RAM on the PCB. So even though both families use the same 800022 PCB number, there's a slight revision between the two.
Re: READ Channel 0n 2060-800022 PCB
Thank you DataMedics, I have encountered the problem of RAM size difference between 800041 (USB) and 800022 (SATA) PCB.
I have a slow responding WDC WD40NMZW-11GX6S1, PCB 800041 with Nanya 1 Gb RAM. I found 800022 donor PCB with Samsung 512 Mb RAM. Move ROM from patient to donor, doesn't work - BSY and periodically blinks.
Perhaps there is a ROM patch to disable addressing upper RAM region?
I have a slow responding WDC WD40NMZW-11GX6S1, PCB 800041 with Nanya 1 Gb RAM. I found 800022 donor PCB with Samsung 512 Mb RAM. Move ROM from patient to donor, doesn't work - BSY and periodically blinks.
Perhaps there is a ROM patch to disable addressing upper RAM region?
Re: READ Channel 0n 2060-800022 PCB
Hello.
Is there any progress on this issue?
I'm having the exact same problem.
On 2060-800022 with patient ROM on it, patient WD40NMZW-11GX6S1 goes to BSY and just flashes.
I want to access the SA of WD40NMZW-11GX6S1 to solve the translator problem.
Do you have any ideas?
Is there any progress on this issue?
I'm having the exact same problem.
On 2060-800022 with patient ROM on it, patient WD40NMZW-11GX6S1 goes to BSY and just flashes.
I want to access the SA of WD40NMZW-11GX6S1 to solve the translator problem.
Do you have any ideas?
Who is online
Users browsing this forum: No registered users and 8 guests
