Hi there,

I have one HM500JI with no terminal output at all.

PC3K & Acelabs gave a step by step tutorial for this but...

Let's go for hot swapping...

like another user,
1. Power on donor. Run the utility. Wait until initialization will complete,then put drive to sleep mode. - OK
2. Unscrew the PCB from donor and install it on patient drive.Screw the screws back. And perform recalibration. - OK
3. Wait until the drive will enter ready state, then read the modules from the drive except some "big capacity" log modules. -OK (I read all modules and save)
4. Power off donor PCB and swap it on donor HDA. - OK
5. Write all necessary modules(All of them - family is not in the list) from patient to donor drive .Then switch drive's Power off/on. - stop..

When switch drive's Power off/on then doner HDD is not ready.

It stay busy, and I have terminal output :


I try to check the modules integrity, but there are 148 of them...

can you help me ?

thanks

Bad procedure.
Imagine (i don't know if this is the case, but even so imagine) that the patient drive have bad modules on SA (Called MC on Samsung) and those bad modules cause the drive to lock on busy.
Now you do the hot swap and you copy all the modules to the donor, including the damaged ones. What do you think that will happend to the donor ? You will copy the problem of the damaged drive to the good one !!!

Are you willing to pay for remote (teamviewer) assistence ?

Regards.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Do you have an external eeprom programer ?
When you plug the defective drive does it spin ? Does it click ? Does it provide any info on pc3k log like bad ROM checksum or red letters with incorrect checksum for fips ?

And when you place the donor pcb on the damage drive without hot swap what message do you get on terminal ?

Most likely by now your donor is gone as well, unless you can restore its modules to it's original state. This might require another hot swap.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

also donor code on Rom/version of ROM is not the same as patient.

Now your donor have sa copy of patient.

Your log on donor might mean that drive can't start because the code on ROM is not compatible with MC code (that you copy from patient)...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

...or the overlay code that you copied from the patient from donor was damaged to start with. At any rate either because module was damaged or because it's not compatible with version of ROM the overlay code for the main program is not loading and your drive stays at bsy.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Does the original PCB spin up the drive? I'm assuming that it doesn't, in which case I could help you identify the voltage tets points, if you could upload a photo.

_________________
A backup a day keeps DR away.

I understand this, but it is not exactly the case : with patient PCB, no terminal output at all, and with donnor PCB, terminal as quoted.
I try not to pay for remote...



I don't have external programer

First when I plug patient HDD nothing happens. No spin, no click, no log.

Sadly, I don't record the log when I place donnor pcb on patient drive at first






So I have to search for another donnor to go further.

Thanks for this first help

Exactly, nothing with original PCB.

I will upload a photo in few hours.

thanks

If this drive is from a client of yours i STRONGLY advice you to outsource this project to a reputable data recovery firm, or at least seek remote assistence of someone with knowledge to fix the issue of the drive by teamviewer, if it's a firmware issue only.
At this rate you will end up messing the damaged drive further.
I also advice for you to buy some drives and practice first.
Moving modules randomly and count on "luck" is generaly a bad move in the data recovery field.
Also you might want to invest in some pc3k training.

Regards.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Dear Spildit,
I know how my mind is working.
If I let someone else fix the issue, I won't learn at all
I have to manage different parts of business, necessary to live, and practice some bad drive is a part of pc3k training.
And time is missing.
But, as you know, each cases are different and I already resolve cases like this, following the procedure. It is why I request help.

I am open minding, but what I need is tutorials, tips.

I think hddguru is a good forum because there are answers (unlike acelab forums), but the "outsource" answers are not the way I want to learn
(and, by the way, HDD Oracle forum is blacklisted by my nod32 AV)

anyway, thanks for your answers

Ok !
The good thing about teamviewer assistence is that you can view the other part fixing the issue and learn from it, that without the risk of damaging the drive.
Also practicing is indee very important but with test drives and not client ones !
Regarding nod32 blocking the HDDOracle, i'm aware of it. Some firmware tools are flagged by Av products as suspecious and also it's very easy as well to report a site as "bad" to those on-line site checking services. The HDD oracle is safe to use and free of virus, but simple way if you have any concearns regarding it is not to use it !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Here are some pictures of the PCB

Can you notice why I think this PCB is HS ?

The motor controller chip is obviously damaged, so PCB repair is probably not a realistic option. Have you tried the donor PCB on the patient drive?

I confess that I don't understand the reason behind copying the patient's SA modules to the donor. However, ISTM that "No Overlay code" means that the donor cannot locate the MOVLY001 module.

I have a general idea for resurrecting a PCB with a dead motor controller, provided that the MCU and its support devices are OK. It involves powering the board from external Vcore and Vio supplies, and validating the POK signal to the MCU. You should then by able to communicate with the MCU via its serial terminal interface.

_________________
A backup a day keeps DR away.

Instead of HOT Swap just replace the PCB with another one containing the same ROM code or adapt the drive MC to the ROM code on the PCB by copying the necessary overlay to it.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Bingo!

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

I can do this by teamviewer or whatever remote app you want to use.

Price is $75 USD (paypal) if i manage to make the drive work as it should.

If no data - no payment.

Regards.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

however, I need another donnor PCB.

Many Thanks for your help, I come back when I have one.

Spildit, I keep your offer in mind. I want to make a shot myself before. (But payment will be in Euro, i'm in France)

Most likely you can use the pcb from the donor that you have, assuming you didn't damage it's ROM code by writing to it.

Start by placing the donor pcb on the damaged drive and post a terminal log.

If you know the firmware version of the 2 ROMs you can either flash a new rom to the donor to match the patient or use the overlay of the donor (if you saved it) to write to patient and make it match Rom code version of donor pcb.

P.s. - I'm in Portugal, so i use Euros as well. Also accept Bitcoin.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

The terminal log on first post is donor PCB on damaged drive.

I have overlay 73 MOVLY001 from donnor
I have patient modules saved during failed hot swap
I have SA backup of donnor drive (ROM, Modules, Tracks)

I do not know patient firmware version, I know donnor one

How can I reflash donnor PCB if it stay busy ? (without another donnor board)

Ok, i was thinking that the log on the first post would be after you messed donor (donor with patient MC with donor pcb).

Try to esc on terminal and issue LE with donor pcb on patient drive to see if you can regain SA access. If it doesn't work the easy way is with hot swap, unless you want to play with burn.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.