First off, if this post is more appropriate for another forum, I would appreciate being pointed to where it would be a better fit. I considered the developer forums but I wasn't sure which one would be best. That said...
I am trying to do data recovery on a Samsung Galaxy S5 that was accidentally factory wiped.
After extracting the image with dd shortly after the incident, I have had no luck in examining the image after several extensive attempts using a wide variety of tools. In truth, judging by the image, it seems that the vast majority of the drive is zeroed out.
However, a number of research projects have shown that Android phones tend not to be securely reformatted up through Android 4.x, and although this has improved over the last several Android versions (beginning with 4.3, if I recall correctly), it seems that it often boils down to correctly implementing the driver for the flash memory chip.
As such, I would like to know if anyone knows how reliable the kernel driver for Android 4.4.4 is in terms of secure deletion for the Galaxy S5 memory chip (KLMAG2GEAC). I've looked through the stock recovery source code, and it looks like it does everything expected of it down to an ioctl(), but after digging through the kernel, I've come to the drivers for MMC and can't make heads or tails of how well they function from just the source code alone (I'm also not a driver programmer, which doesn't help). This is especially so for the Samsung-specific code, since those files seem to be particularly poorly documented.
Does anyone have experience with the secure delete/TRIM functions of this chip, or data recovery when it does not seem to be possible from a direct dd-derived disk image? I'm pretty much out of ideas at this point, and although I want the data back, if it's impossible I'd rather know now so I can start using my phone again.
Thank you very much for any help.
I am trying to do data recovery on a Samsung Galaxy S5 that was accidentally factory wiped.
After extracting the image with dd shortly after the incident, I have had no luck in examining the image after several extensive attempts using a wide variety of tools. In truth, judging by the image, it seems that the vast majority of the drive is zeroed out.
However, a number of research projects have shown that Android phones tend not to be securely reformatted up through Android 4.x, and although this has improved over the last several Android versions (beginning with 4.3, if I recall correctly), it seems that it often boils down to correctly implementing the driver for the flash memory chip.
As such, I would like to know if anyone knows how reliable the kernel driver for Android 4.4.4 is in terms of secure deletion for the Galaxy S5 memory chip (KLMAG2GEAC). I've looked through the stock recovery source code, and it looks like it does everything expected of it down to an ioctl(), but after digging through the kernel, I've come to the drivers for MMC and can't make heads or tails of how well they function from just the source code alone (I'm also not a driver programmer, which doesn't help). This is especially so for the Samsung-specific code, since those files seem to be particularly poorly documented.
Does anyone have experience with the secure delete/TRIM functions of this chip, or data recovery when it does not seem to be possible from a direct dd-derived disk image? I'm pretty much out of ideas at this point, and although I want the data back, if it's impossible I'd rather know now so I can start using my phone again.
Thank you very much for any help.
