Hello

I have a case with a dead SD card. I found a solution on the AceLab Global Solution Center that could work but it use an hand made XOR.

Is there a way to extract XOR from the .SOL file ?

_________________
Lemmy

what was the XOR ref code?

595 from task_id=5047

For info Roman (from Ace Support) told me that's it's not supported yet but should be in the next release.

_________________
Lemmy

ah yes ... 2703 ... Its a dynamic XOR.. There will be many variants

in response to your question:

"Is there a way to extract XOR from the .SOL file ?"

The XOR KEY is not actually kept or stored in the .sol file.

It is encapsulated in the PC3000 resource library set. This is why we have to wait for the Stable version updates before the XOR key is available to use. It shouldn't be long now

Thank's for answering my question...
Lucky me, the job can wait.

Subject close.

_________________
Lemmy

Those custom made scramblers (XOR keys) made with bit errors (unsupported ECC), so they don't make lot of sense when it comes to data recovery, mostly for database statistics and controller analysis.

In many cases you can extract the scrambling pattern right from the dump with data. Very often block with LBN=0001 stores zeros (scrambled).
Boolean XOR operation works this way:
A xor 0 = A
For the block 0001 this "A" = scrambling pattern.
This is possible because nowadays distance between MBR and Boot record is more than 1 virtual block of NAND physical image (not 32/64 sectors).
Even if LBN0001 have some data (not zeros), it's possible to find several blocks where some pages filled with scrambled zeros.
Merging 3 or more (odd number) blocks through "Bit verificator" operation you can extract pure key.



Diagonal pattern is a virtual block with pure scrambling pattern (XOR key)

_________________
VISUAL NAND RECONSTRUCTOR. A big revolution in chip-off data recovery

SM2703 BLK=128 PG=17600 (1098x16+31)_00F602_XOR_SA
This xor, has xored markers. You cant use this way.