Ive been planning to get sample map files to him, but I've been too busy. Maybe you can do it, if you have a chance.

_________________
Luke
Recovery Force Data Recovery

I will try tomorrow to get two sample maps, one in old format (Mrt 21101) which works with UFS Explorer, and a second identical sample map in new format (Mrt 21111) so that Iurii will be able to compare them and probably find how to implement it in next UFS versions.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Hi guys

After testing the new version (2.1.11)from MRT I found this:

-If , when creating a new task in DE, you choose Map Type-> Binary file , the Head map is wrong, only one head is added to the map no matter how many heads the drive has...Tested on WD and Seagate drives. Another MRT BIG BUG added to the software.

-If, when creating a new task in DE, you choose Map Type->List of Ranges, the head map is build correctly but, this type of map/task cannot be open by UFS Explorer (it's the same for a DE task created with PC3000)...Not MRT fault.

So we have to wait until MRT will repair what they broke in the software or for Iurii to add to UFS Explorer the ability to open a task created with List of Ranges map type.

Rgds

_________________
www.datasave.ro

Did you report the issues to MRT? I don't have a lot of faith that they will listen, but we can't blame them if they don't know about it.

_________________
Luke
Recovery Force Data Recovery

This is a quote from their update log:

"Aug.4th, 2025
MRT 2.1.11.1 New Package Update Content:
1. Fixed the issue of dividing all the bitmap into head 0 in WD cases"

We are on version 2.1.11.2 and the problem is still there.....I think they already know about the problem, but......

_________________
www.datasave.ro

YES, you're right. There is the bug as you reported and it hasn't been correct yet by MRT... is still there also in 2.1.11.2 version.
I've noticed that this buggy binary map in latest MRT versions is double sized compared to previous versions as 2.1.10.1, example for 1 TB hdd which has 1.953.525.168 LBAs it should build "Mrt Data Explorer.Map" file in 1.953.525.168 bytes size but it creates 3.907.050.336 bytes map file.
If you open it with hex editor, you should expect to have only 00 bytes inside (until you keep squares all white) but you will see that it has 00 FF from begin to the middle and 00 00 since the middle (HEX 74706DB0) to end.

I modified it by deleting the 1st half to convert the map file in 1.953.525.168 bytes size with all 00.
But here comes again the issue, when you reload the task, MRT changes the map file again into 3.907.050.336 bytes (but this time it keeps all 00).
However, that's not okay, so i give up!

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Those FF's are added to support more than 8 heads (until 256 in theory)...and because of that the problems began.....they screwed up all the map file and the task also .

That's why I reverted to 2.1.10.x version and I will use that until they resolve the problem.....
Anyway, it would be nice if Iurii could add support for List of ranges map type (It's used by both MRT and PC3000).

Rgds

_________________
www.datasave.ro

Oh ok, then the double size is normal for new version.
I will wait that MRT fix the issue before i try again to replicate same map between both versions for comparing purpose.
In list of ranges i was not able to modify manually the map, i simply don't understand it. So, it is necessary to clone the drive again and get the same map as i got when i cloned the drive in Mrt 21101, but i don't have that patient drive anymore.
I could manually change the map from a new one to get identical as the one created in previous version but i can't replicate (Reading successfull but null), (Seagate 241A) and (sEDU) because DE doesn't gave the function.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

in binary mode would be easy to insert (Reading successfull but null), (Seagate 241A) and (sEDU) by just working on binary file in a hex editor.
You just have to assigne this values, example:

On HEAD 0
AZZURRE (Reading successfull but NULL) --------------> [HEX 0A]
CYAN (Seagate 241A) --------------> [HEX 0B]
TURQUESE BLUE (sEDU) --------------> [HEX 0C]

On HEAD 1
AZZURRE (Reading successfull but NULL) --------------> [HEX 1A]
CYAN (Seagate 241A) --------------> [HEX 1B]
TURQUESE BLUE (sEDU) --------------> [HEX 1C]

The offset you need to change in hex editor are simple to find in binary mode, example if you have to modify the map from green (Reading successfull) to CYAN (Seagate 241A) at LBA 100.000 (which in head map could be on head 1), you just need to go on offset 186A0 and modify byte "11" in "1B"... at least in old mrt version, but in last version would not hard to modify that.
The question is how to manually modify in hex "list of reanges" map?
Or, can MRT implement the function to mark map with (Reading successfull but null), (Seagate 241A) and (sEDU) ?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

What's new in version 10.16:

* File system transformation: added support of 'MongaStorage' container type on Promise Apollo NAS;
* For ZFS file system:
- Added special tool to open the file system at a specific recent transaction to potentially access recently deleted data without a scan;
- Option to search (scan) for file system transactions that are not available through 'uberblock' references;
- Quick scan of individual transactions to perform a 'virtual repair' of minor consistency issues caused by overwriting;
* Microsoft Storage Spaces: Fixed issue with data mapping calculation on multi-tier spaces;
* Fixed bug with adaptive reconstruction of RAID10/1E;
* Added basic support of RAID metadata created by ASMedia ASM1xxxR chips;
* HFS+ scan: fixed issue in Journal analysis procedure that can cause excessive memory use and even crash in some scenarios;
* Refactored code of ZFS access module to fix a 'ZFS access' bug in Linux software version caused by incorrect code optimization by gcc compiler.

What's new in version 10.17:

* Added experimental 'read' support of EnCase 'Logical Evidence' files (L01/Lx01);*
* Added basic/experimental support of VBK backups;
- Also added support of VIB (delta) files and applying these deltas to the base backup;
* EnCase E01 format:
- Added extraction of the source device name and serial number;
- Support of 'virtually unlimited' number of image file segments (support for extensions sequence according to both EnCase and FTK Imager formats);
* EnCase Ex01 format:
- Fixed issue with invalid size and added extraction of the source device name and serial number;
- Added support of extraction and verification of SHA256 and SHA512 hashes;
- Support of 'virtually unlimited' number of image file segments (support for extensions sequence according to the EnCase format);
* AFF4 support: fixed some ZIP64 compatibility issues and also added implementation of LZ4 compression;
* Applying delta files to base (snapshot) virtual disks: added an option to select a base storage (snapshot) of a different size to support resize scenario;
* Refactored code of 'blake2b' implementation that caused incorrect code optimization by compiler under macOS (affected functionality of LUKS2 decryption);
* In file system transformation tool: added 'Convert to a photo library' tool to convert any source folder with photos to a 'Photo library' of a fixed structure by using the file metadata;
* Added support of a couple of variations of HighPoint RocketRAID metadata;
* Making disk image in EnCase format:
- Image File segment extension sequence is extended according to the EnCase format;
- Added 'header2' section to preserve the source storage name and serial number;
* Fixed issue with proper ATA disk addressable capacity detection when disks with size over 2TB are reduced to below 2TB with HPA/DCO;
* Fixed issues reading WOF-compressed files on NTFS file system when default DATA attribute not present.

What's new in version 10.18:

* Added the possibility to decrypt a specific APFS volume to the Explorer context menu;
* APFS file system: added a tool for direct quick access to APFS transactions (generations) to potentially access recently deleted files or volumes without a scan;
- Also added support of search for older ('lost') transaction;
* Added a function to save/restore the list of found transactions for both ZFS and APFS;
* Fixed issue with support of larger VBK files;
* When scan is resumed from SSDB file, added possibility to save automatically another SSDB from the continued scan, including periodic SSDB backups;
* RAID metadata support: added one more variation of SilImage RAID metadata;
* Microsoft Storage Spaces:
- Fixed issue with support of cache volumes with sector size 4KB;
- Added support of volume metadata version 17 (Win11 25H2);
* Support of archives:
- Added support of LZMA2 decompression;
- Added read support of .xz archives;
- Added read support of .xar archives;
* In the embedded file viewer:
- Added preview of newly supported types of archives;
- Added extraction of preview picture for 3MF and F3D model formats;
- Also fixed a couple of issues with proper displaying of texts (such as 'Error', 'Loading...' etc.);
* NTFS file system scan:
- Fixed issue that prevented running a full 'quick' scan in some scenarios;
- Updated transaction log (journal) analysis procedure for better recovery of deleted files in some scenarios;
* FAT/FAT32 scan: updated for better file system structure recovery in some scenarios.

What's new in version 10.19:

* Access and search for transactions (checkpoints) is now also added for ReFS (version 3.x) file system;
* Advanced version of 'Check and assign file name extensions' is now added to the 'Transform file system files' tool with a possibility to configure raw recovery rules use;
* Tool to open NTFS restore points (shadow copies) is now added to the 'Transform file system files' tool;
- Also added support of shadow copies on ReFS file system;
* Microsoft Storage Spaces:
- Added support of adaptive reconstruction on dual-redundancy parity volumes (dual XOR, 4-10 columns in rotation);
- Fixed issue with opening cache for cached volumes in some scenarios;
* ExFAT file system scan:
- Fixed issue with skipping some files when they were renamed/moved to a different location (now, 'deleted link' object is * recovered at the old location);
- Reworked procedure of detection and reconstruction of lost/damaged file system;
* FAT/FAT32 file system scan: when object is moved or renamed, the software also attempts to create a 'deleted link' in the old location or with the old name.

What's new in version 10.20:

* Added support of encrypted volumes on OpenZFS file system ('datto' scheme);
- Implemented support of paswords and plain decryption keys via the same passwords entry dialogue;
* VBK/VIB support: added support of scenario with free form structure of actual backup components in the archive (subfolders, etc.);
* AFF4 images: added support of 'open file as a disk image' function for this format;
- Also fixed issue with support of images with 'snappy' compression;
* Fixed issues with MS Data Deduplication support (applicable to metadata version 2, Windows Server 2016);
* Data access on ZFS file system: complete rework of data access procedure for better support of mirror metadata (for better error tolerance);
* ReFS3 file system: fixed problem reading sparse files (with unallocated segments);
* A couple of fixes to F2FS file system scan;
* Fixed crash bug on indexing of HFS+ file system with specific damage to the 'Catalog File';
* Added several built-in rules to raw recovery;
* Update to embedded file viewer (some camera raw formats, documents and video 'quick previews').

Hello
We have a WD 1 TB desktop hard disk having win10 x64 & My SQL based software. Unfortunately hard disks health has remained 7% & is in failing state.
It is showing Bitlocker (in stand by mode) .We have tried R-studio but it doesn't identify correct partition size & is asking for bitlocker key.
Same is with Hasleo Bitlocker recovery.
However UFS explorer has correctly identified partition (353GB) and has decrypted volume as well. Since my sql data size is large trial version cannot save it so we don't know anything about file integrity.
I want to know which UFS / Recovery explorer will be suitable for us. Being an IT company we are looking for a perpetual license for our internal use.
Product SKU's are confusing as developer has cleverly distributed main features in different version & ensured that no single product will be having all functions
So essentially you will be forced to buy UFS explorer Professional + UFS explorer Technician if you want a complete solution .
Pls. suggest us a product which will be having all essential functions --1) Imaging 2) Decryption 3) LVM /Raid dynamic disk support. It will be affordable and perpetual ( we may update in future if required)

UFS Explorer Professional is enough for what you need.

_________________
www.datasave.ro

I know a trick to save big files (above 768 KB) with UFS Explorer trial version (but is a very annoying method).
I'm not talking about crack, which is illegal and i don't even know if exist for this sw.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

It's a company with the funds and desire to buy a license. But yeah, let's fuck Iurii and colleagues and tell people how to use their products for free. Why not, huh? /s

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

Its too too costly for anyone

I am not comparing two products which are completely different and I know everyone has his right to quote pricing but here R-studio Technician is costing $80 while UFS pro $700
By simple math
@ $700 pricing -- aprox sale per month -100 licenses = $ 70000
@ $200 pricing -- Aprox sale per month - 10000 licenses = $ 2000000