Anyone Want This Case?

[data-medics]

So I've got a potential client with a case I don't really want, but seems to be willing to pay dearly for the data. It's a Microsoft surface with the soldered on SSD. They've already managed to boot it to Linux, but the SSD isn't readable at all.

Anyone got experience with these and want the case referral? I don't have time to re-invent the wheel for a case like this.

[fzabkar]

I don't have time to re-invent the wheel for a case like this.

Why not just tell the truth, ie that this job is outside your skill set?

[HaQue]

Tom-ah-to, tom-ay-to, I think it is pretty much what he said.

Surfaces vary between models - what model is it?

I think Pre Surface Pro3 they are fairly easy, but ones like Pro 6 use BGA SSD's (NVMe). Late model Surfaces use encryption & bitlocker can complicate things on any model.

I have some Pro 4's that appear to have the NAND either fill, or die. The machine reports No HDD, and chip off I haven't tried as yet. I don't have the time to re-invent the wheel either - or upskill.

[arvika]

We call this device: one time use. It works till broken, than it is usually unrepairable.
Few problems:
- disassembly the digitizer/screen without broken takes some time and expirience
- uncommon chip BGA-1620
- it is high probablility that SSD will be crypted as HaQue write.

[lcoughey]

I suggest you contact Mark at NANDoff data recovery in the UK - https://www.nandoff.com/

[data-medics]

Thanks for the suggestion Luke.

I think Fzabkar is just trying to be toxic here because I've been ignoring his attempt to draw me into a toxic discussion here on reddit: https://www.reddit.com/r/datarecovery/c ... on_to_fix/

I'm done feeding trolls this week.

[einstein9]

So I've got a potential client with a case I don't really want, but seems to be willing to pay dearly for the data. It's a Microsoft surface with the soldered on SSD. They've already managed to boot it to Linux, but the SSD isn't readable at all.

Anyone got experience with these and want the case referral? I don't have time to re-invent the wheel for a case like this.

_
Not visible in Linux because of another reason (not dead, had similar cases recently)

Just for the record here, I know a friend who developed his own "Direct mem. access" but am sure it has to be done on his Lab.