XAMN - .UFD files?

Depends. if the UFD points to a physical extraction then you can just import the physical extraction. Otherwise I believe you need the UFDR file. the UFDR file is basically just a zipped up Extended XML file with attachments (pictures etc.)

Depends. if the UFD points to a physical extraction then you can just import the physical extraction. Otherwise I believe you need the UFDR file. the UFDR file is basically just a zipped up Extended XML file with attachments (pictures etc.)

This is true for importing extractions using XRY.
I'm talking about importing files via XAMN.

I don't use XAMN but the .UFD itself is just a text file, you can open it with notepad and give it a read, won't really have anything of value to load into XAMN which is why AmNe5iA suggested to load the actual image. It will contain extraction and file details at most.

The UFDR is an actual processed report which makes sense why XAMN ingests it. If they take .UFD files, it's likely used as a pointer to process the actual image in their processing engine as opposed to XAMN.

Hope that helps,
Jamie

XAMN does not import UFD file as they are pointers to extracted files/bin files. UFDR files can be imported, however the data will not have been decoded using XRY parsers. It will, however, be another tool to examine the data that was extracted using UFED.

If the device is directly supported with XRY then you can navigate to that profile and perform an import of a bin, zip etc. XRY will then decode the data using their parsers, potentially providing more data. If it is not directly supported then you can choose something such as an Android Generic profile etc depending on the make/model. Once completed you could then open it in XAMN for analysis.

A bin file can be imported directly into XAMN as well, however the data will not have been decoded.

My apologies for the late reply.