Hi everyone. I have a somewhat unusual case involving a 2 GB microSD from which I’m unable to get good readings. I’ll attach some screenshots of the dump. I managed to identify WP, but the reading problem persists.

The Read ID I’m getting is EC D5 94 76 54.

While searching for information, I found that Arvika worked on what seems to be a very similar case. In his database, it appears as microSD #65, also 2 GB, Samsung, ID EC D5 94 76, controller EN2683, Page Structure 1075_26, and XOR FF09FD (DA) + GRID (full page).

There is also the following note:

“2x15, remove grid, make ECC, than XOR”

I have never worked with GRID (full page) before, so I’m not sure exactly how to identify or remove it. I’m hoping this may be what I’m missing and could explain why I’m unable to obtain a properly readable/interpretable dump.

Has anyone worked with this type of GRID in VNR, especially with the EN2683 controller, and could give me some guidance on how to identify and remove it?

Normal XOR uses a static linear key or a simple repeating pattern. A Grid XOR is a matrix-based scrambling method.
The specific byte applied to scramble a piece of data changes depending on its grid coordinates inside the chip architecture.
The key changes dynamically based on the Page Number (Y-axis), the Column / Byte Position inside the page (X-axis) and the Block or Bank ID (Z-axis)

It is Coordinate-Aware Transformation. The recovery software must generate or map a two-dimensional mathematical "grid" matching the hardware layout of the flash controller.

The software automatically shifts and calculates the XOR key dynamically as it moves down the rows (pages) and across the columns of the raw dump file to cleanly un-scramble the user data

I don't know how many tools support it