ZAP Glider Micro SD HC 8GB, unknown translator

[edbrandt]

I managed to copy raw data from a dead ZAP Glider Micro SD HC 8GB, but I did not sucess in recovering the data. File headers are detected, but I did not succeed in building image - TS has tried, but the required translator is not available in utility (yet).

Anyone have any idea how to recover data from the card, that TS or I did not already think off?

All help appreciated.


Card details: $ECDED9CA - 58420000 K9ABG08UAx8 [SDR] [Page: 8640 bytes (16 sectors). Block Size: 3072 sectors (192 pages)] (x8)

IMG_1897.JPG (567.73 KiB) Viewed 11099 times

IMG_1899.JPG (1.88 MiB) Viewed 11099 times

IMG_1918.JPG (12.71 KiB) Viewed 11099 times

Thank you
-Espen

[AJ2008]

If limitations are with PC3000 Flash, do you have options to try other software for it?

[edbrandt]

That is probably one solution AJ2008, any suggestion which (affordable) software that might support this chip?

[AJ2008]

If you can upload entire dump (complete PC3000 Flash task folder will be fine) then I can parse it through software I have here to check it for you.

[edbrandt]

Thanks AJ2008. I'll PM you with details.

-Espen

[AJ2008]

Last 40% (approx) of image shows pattern 'E0 E0 E0' like is not read correctly. Actual data areas contain lots of '00' for nearly every other byte. there are no obvious structures I can see on it.

Within FE, no layouts are found meaning no ECC map is found.
within VNR software, bitmap view looks poor with mostly empty areas, no structures such as SA markers, nothing is identifiable.

For me, this looks like there is some problem with the configuration the chip was read with.

I will email with more details on it.

[jerema]

I got the the same problem, Same chip, noname MicroSD card 8GB.
I had to turn VCC to 2.3V on spider board, then I could read the chip dump. But no ECC.

I ask the TS, but Filipp tells me: "it's AU controller chip case and it can be solved only by Translator - we have no translator for monolithic AU-cases.
secondary - utility hasn't ECC polynome for this case, I've tried to add it manually but ECC errors doesn't correcting..."

Is there a solution available ?

Thanks

[edbrandt]

Well.. I have now read and re-read the chip about 20 times with various VCC setting, and right now chip ID is detected 3.3V (which it wasn't before) - but the data in the dumps doesn't seem to change to the better. Still no ECC.

Really not sure where to go from here..

-Espen

[AJ2008]

Select page designer view, and scroll to around 50% of dump then post screenshot of how it looks

[edbrandt]

Here you are... This was read at 3.3V

zap-glider.PNG (22.16 KiB) Viewed 10983 times

[edbrandt]

Source of the postAU controller chip case

Can anyone elaborate on what a AU controller chip is, and how it differs from other controllers? Thanks

[AJ2008]

The memory is not stored as it is in traditional storage devices, and the allocation of the data in addition to ECC parameters and XOR patterns are all determined by specific configuration of the controller. Different controllers have different methods of doing the same task and each need to be treated accordingly.

I am not sure that your read is a good one, even at this new 3.3V read. The page designer view shows 'noise' that represents how data is stored, and in your case it looks 'wrong'. If the configuration of the chip is good, then the chip itself must have some errors, but in any case I think the read you have is not right.

I am not an expert in such situations, maybe there is someone here who can help more or can point out something I missed or got wrong, but for me it seems like this is not recoverable with the dumps taken already.