Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
February 8th, 2024, 6:38
Its a WD 8TB Hitachi Architect drive , initial problem was patient pcb is dead and doesn't spin, tried fixing pcb dint help, its micro rom and has 2 roms , drive was already returned by another data recovery lab, as they are not able to read the rom and dint have rom reader as its T2 uson rom, they have removed both the rom but i have a doubt whether they placed the rom in same position(rom 1 and 2) , i tried swapping the rom in donor pcb drive comes ready in pc3k with full id but no sector access we cant backup resources as its not supported model, then i returned the donor rom in donor pcb again its same problem drives come ready with full id but no sector access initially the donor was fine i interswapped the donor rom i.e, rom 1 and rom 2 still same problem, so i have bought a t2 rom uson reader read roms of both donor and patient drive and have the backup, in order to find solution i have got another donor removed both roms and took backup and fixed the same rom same position in donor 1 pcb to check whether the pcb has encryption now donor 2 drive has sector access with donor 2 rom and donor 1 pcb, all i have found is that when the rom is inter changed that is rom 1 and rom 2 of patient or donor 1 the rom value gets modified,i got this conclusion with donor 2 roms as i dint interswap the donor 2 rom and have the initial rom back now i have attached patient roms i dint know which 1 is left and right and donor rom left and right and also unmodified (was not interswapped) donor 2 rom left and right kindly help me fix the patient rom i am also attaching the pcb number and pcb as well
What am trying to say finally is that interswapped roms of both patient and donor 1 value gets modified whereas donor 2 both which is not interswapped does not gets modified and works fine i wanted some 1 who can help me fix patient rom using donor 2 rom as reference
- Attachments
-
- DONOR 2.rar
- bot rom of donor 2
- (1.62 MiB) Downloaded 114 times
-
- DONOR 1.rar
- both roms of donor 1
- (1.62 MiB) Downloaded 115 times
-
- PATIENT.rar
- both roms of patient
- (1.62 MiB) Downloaded 116 times
-
-
-
-
February 8th, 2024, 13:10
Is there are problem with the "." key on your keyboard?
February 8th, 2024, 15:41
ROMs 1 and 2 differ in 4 modules.
February 9th, 2024, 2:11
Hi fzabkar are you talking about the patient rom or the donor 2
Can i have your e mail id pls
February 9th, 2024, 12:39
jamesrajesh007 wrote:Hi fzabkar are you talking about the patient rom or the donor 2
It's the same result for all ROMs.
jamesrajesh007 wrote:Can i have your e mail id pls
I prefer to keep the conversation public.
February 9th, 2024, 13:59
This is a comparison of the patient and donor #2 ROMs.
February 9th, 2024, 14:39
Your patient PCB is native:
- Code:
Parsing information in MINQ CP 0x83 and HIN1 / HIN2 CPs 0x99 / 0x9A ...
HDD serial number = VYJ70KSM <---
Date of manufacture = week 25 of 2023
HDD part number = 2W11034
PCB part number (sticker) = 0F43494 <---
Media Disk Definition = MediaDiskDefinit
Motor Serial Number = R0218L
Flex Assembly Serial Number = A4A1RE12
Actuator Serial Number = A4A1RE12
Device Enclosure Serial Number = DESerialNumber00
Card Serial Number (sticker) = 3231635 <---
Card Assembly Part Number = 0F43494
World Wide Name = 5000CCA0C6DF5FC1 <---
Microcode version (HIN1) = X9E0
Firmware version (HIN1) = 85_00A85
PUIS flag (HIN1) = disabled (0x00)
Microcode version (HIN2) = X9E0
Firmware version (HIN2) = 85_00A85
PUIS flag (HIN2) = disabled (0x00)
Supported Inquiry VPD pages = 0x0 0x3 0x80 0x83 0x86 0x87 0x88 0x8A 0x8D 0x90 0x91 0xB0 0xB1 0xB2 0xD1 0xD2 0xE1 0xE2 0xE3
- Patient_PCB_sticker.jpg (7.87 KiB) Viewed 3037 times
February 9th, 2024, 15:55
- Code:
Compare PATIENT\CPs_01 and DONOR 2\ROM 1 RIGHT\CPs_00
Filename Comparison result
--------- -------------------------- ---------------------------------------------------------------------------------------------
FSVS Folders are different
CP_81.bin Binary files are different table of modules with 96-bit hashes
CP_83.bin Binary files are different MINQ - Inquiry info
CP_84.bin Binary files are different FCHN - Read/Write CHaNnel parameters (https://www.hddoracle.com/viewtopic.php?p=23986#p23986)
CP_85.bin Binary files are different ?
CP_87.bin Binary files are different FSVS - adaptives
CP_88.bin Binary files are different FAEP - head related adaptives (https://www.hddoracle.com/viewtopic.php?p=23987#p23987)
CP_89.bin Binary files are different FIMG - head related adaptives (https://www.hddoracle.com/viewtopic.php?p=23991#p23991)
CP_8A.bin Binary files are different FCRD - PCB (card) related info
CP_98.bin Binary files are different FSEC - 64-byte key/hash/signature
CP_9F.bin Binary files are different ?
CP_A0.bin Text files are different ?
CP_A3.bin Binary files are different ?
February 9th, 2024, 19:14
Is this your PCB (p/n 0B41785)?
https://i.ebayimg.com/images/g/6uUAAOSwZGBkTO7T/s-l1600.pngSimilar problem ...
https://forum.hddguru.com/viewtopic.php?p=304264#p304264Had a HDD go bad again due to power shortage. Purchased a new one via Amazon just as they came back into stock. I replaced BOTH the bios chips, the drive spins up and disk is detected but can gain no access and says 0 bytes out of 6tb.
February 10th, 2024, 2:24
Yes my pcb number is 004-0B41785
February 10th, 2024, 2:25
February 10th, 2024, 2:33
I think you may have two problems.
That other thread would suggest that the MCU has a key that is matched to the firmware, plus your experience with donor #1 suggests that interchanging the ROM positions causes some kind of corruption.
I could help you to repair the patient PCB if you could provide a detailed photo.
February 10th, 2024, 2:51
fzabkar wrote:I think you may have two problems.
That other thread would suggest that the MCU has a key that is matched to the firmware, plus your experience with donor #1 suggests that interchanging the ROM positions causes some kind of corruption.
I could help you to repair the patient PCB if you could provide a detailed photo.
sure sir am sending the patient pcb and also am sure these pcbs are not mcu encrypted as i installed donor 2 roms in donor 1 pcb and i can get sector access and no encryption
February 10th, 2024, 3:47
pls find the pcb am sure fixing the patient pcb wont help bcoz the rom value is modified only way is to fix the modified rom to get the sector access ( donor 1 rom was also interswapped thats y am not able to get access of donor 1 sectors due to modified rom even if i install donor 1 rom in donor 1 pcb) but donor 2 works fine in donor 1 pcb as it was not interswapped and rom was not modified that shows the mcu is not encrypted
- Attachments
-
- i have tried fixing diodes from donor pcb but dint help so removed back
-
February 10th, 2024, 4:45
Mate, if you can't write legibly, then I'm done with this thread.
February 10th, 2024, 7:04
Hi fzabkar all i am trying to say is that patient 2 roms(left and right) if its by mistake was not placed in donor pcb in same order (i.e, left rom in left position and right rom is right position) the rom gets modified on its own after we power on the drive , this s 1st scenario , i came to know abt this after i did that mistake in donor 1 here donor 1 means FIRST donor serial number (VYHST1NM) after trying in swapping roms. As swaping roms dint help me fix I bought a T2 rom reader and read the roms(left & right) of both patient and donor 1(FIRST donor S/N VYHST1NM).In order to find what was the exact problem i have bought another donor here donor 2 means second donor(S/N : VYHVYSLM) i removed roms of second donor and read left rom and right rom and dint mixed it as i now know it should be kept in same order i fixed the second donor rom in FIRST donor pcb and second donor works fine with no encryption and sector is accessible. This clearly tells us that pcb is not mcu encryption now i want a solution that using second donor roms(left and right)as reference is there a way to fix the modified patient rom(left and right).
Now is this Legible
February 11th, 2024, 17:22
What voltages do you measure at Vx and Vy?
- TVS_diodes.jpg (35.72 KiB) Viewed 2740 times
February 11th, 2024, 23:15
CPs extracted from patient and donor ROMs.
To verify the position of each ROM, note that one of the ROMs contains "EPOD" in CP 0xA0 while the other contains "CRTC" in the same CP.
- Attachments
-
- CPs_ROM2-Left_Donor2.7z
- (831.73 KiB) Downloaded 113 times
-
- CPs_ROM1-Right_Donor2.7z
- (832.05 KiB) Downloaded 110 times
-
- CPs_ROM2_donor1.7z
- (832.14 KiB) Downloaded 110 times
-
- CPs_ROM1_donor1.7z
- (827.16 KiB) Downloaded 114 times
-
- CPs_ROM2_patient.7z
- (831.53 KiB) Downloaded 112 times
-
- CPs_ROM1_patient.7z
- (832.19 KiB) Downloaded 114 times
February 15th, 2024, 0:59
Any updates?
Do you have a multimeter? Do you need help to measure the voltages?
Here is another HGST model that has a single ROM with two mostly identical halves. Essentially it combines your ROMs 1 and 2 into a single ROM. You can compare the differences between each half against the differences between your ROMs 1 and 2.
https://www.hddoracle.com/viewtopic.php?p=20172#p20172
February 15th, 2024, 2:27
fzabkar wrote:What voltages do you measure at Vx and Vy?
TVS_diodes.jpg
Vx measures 5v and Vy measures 12v
Powered by phpBB © phpBB Group.