Extracting WD ROYL modules from track dumps

[pbzcbf...@gmail.com]

Has anyone written a tool to extract WD ROYL modules from track dumps?

Does this feature already exist in pro tools? I'm not talking about searching for a specific module number. I want to extract all modules, both known and unknown.

[pbzcbf...@gmail.com]

I tried reading by ID over the full range (01 to FFFF) in WDMarvel and it looks like it will finish in 40 minutes. I don't understand what it's doing, but a full track dump followed by a file scan shouldn't take more than a few minutes. :-?

[t...@desertdatarecovery.com]

PC3K does allow it. Couple of pics attached. I have ever used it for unknown mods but looks like it does find nested modules as well.

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/8ba9d813-6956-4f78-8cc7-3bc48022595dn%40googlegroups.com.

[pbzcbf...@gmail.com]

Thanks. I'm now a little confused.

It seems to me that there are 3 ways to retrieve SA modules.

1. If the module exists in the DIR (module 01), the DIR will tell us the module's SA address and size, and the firmware can then retrieve the module by reading the appropriate number of sectors at this address (ABA).

2. Send a VSC that requests X sectors from module ID 0xnnnn. This VSC does not have an SA address as one of its parameters. I presume this method is what Ace calls "reading by ID". Obviously this means that the firmware must know where this module is located.

3. Carve the module out the tracks or out of the SA regions.

I notice in previous threads that module 0x129 does not exist in the DIR of Charger models. However, Ace is able to retrieve it "by ID". If the firmware is not looking in the DIR for module 0x129, then how does it know where it is?

[t...@desertdatarecovery.com]

Yes that is interesting. I just ran the search again that I posted to include nested modules and 129 was still not found. It can only be found by ID. To get access to the SA via USB you need to change 1A2 in the ROM, so maybe 129 is part of the boot up process and is found via the ROM or MCU?

 

Tim Homer - Lead Engineer

Desert Data Recovery

t...@desertdatarecovery.com

www.desertdatarecovery.com

 

From: datarecovery...@googlegroups.com <datarecovery...@googlegroups.com> On Behalf Of pbzcbf...@gmail.com
Sent: Saturday, January 29, 2022 2:50 PM
To: DataRecoveryCertification <datarecovery...@googlegroups.com>

--

Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/e1f784e4-3fcf-4edf-ac48-d860f1fef521n%40googlegroups.com.

[pbzcbf...@gmail.com]

I decompressed all the segments in the ROM, but was able to find only one compressed ROYL module, namely 0xDDDD.