I like to teach my users to read the screen and also why something goes wrong.
Other than a select few users, a little bit of extra time spent with communication goes a long way towards stopping repeat 'offences'.
Also means I only really get called for major stuff now so I can actually focus on projects.

Also when I implement a restriction I make sure to point out why, and because of who it was implemented.
Offloads a lot of resentment that would be pointed at you towards the culprit ;)

Well first things first, remove the memory card if its still in the phone and put it aside if you want to recover something from it.
This is to prevent you writing new stuff to it and possibly overwriting what may have been deleted.

Also depends on the erase procedure on the phone/camera.
Some models are nasty and actually do erase the data completely by overwriting it (not very common).

Use a card reader to access it rather than the phone/camera itself, manufacturers like to do all sorts of silly, inconsistent and annoying stuff.
Occasionally I have to do data recovery on cards (mostly retrieving deleted pictures) and most free data recovery programs should be able to retrieve files if they use sector scanning methods if undelete fails (key in the magic number/s and let it scan).

Depending on how much was written to the phone after the incident they should be able to atleast do a partial recovery.

A cats brain? Its as if he is deliberately trying to enslave humanity.

I signed up to say exactly this, add into that aluminium air batteries and a variety of other reactive metal air batteries.