loosed

Hot Tub Phone Repair


08:45pm | 10/15/2019
Daniel Tompkins

You shouldn't be allowed to have nice things when you forget your phone in your swimsuit pocket— not once, but twice! The first time was a Motorola Razr. I was swimming at my grandma's condo and came out of the pool with a dripping flip phone.

A couple of my friends' parents worked at Motorola, so somehow I got my hands on a lot of unique devices at an early age. One of my all-time favorites was the Motorola "MOTOROI" XT720, which featured Android 2.0 and a 720MHz mobile processor.

I ended up rooting this phone— and it's still running! Here's a review from 2010, when it was released:

huge 3.7 inch, high-definition WVGA (480x854) display, making it easy to view full page websites, videos, games, or photos.

Okay. This post is Hot Tub Phone Repair, not Hot Tub Time Machine. So I'll stop pondering the evolution of mobile technology and get to the point! I was on a business trip on the west coast when I completely drowned my Galaxy S7 in the hotel's hot tub.

This might have been my longest lasting phone— 3 years and not a scratch! But it didn't matter. That expensive OtterBox and "water resistant" label couldn't save this cellphone from getting blasted by a Jacuzzi jet for 50 minutes. It was bricked.🧱 🧱 🧱

Luckily one of my co-workers had the foresight to remove the MicroSD card. My first thought was to shake the water out at at his face like the pope waving an aspergillum on Easter.

Spoiler alert: I didn't fix the phone. 😞️ That's a misleading title... I did, however, manage to recover my photos from a corrupt SD card!

When I first put the SD card into my PC, I was met with a disappointing message from Windows:

Most people are aware of the fact that formatting removes all the device's data. So, obviously this is not what I was hoping for, but... Thank Poseidon! I tried another MicroSD adapter, and I was able to access files on the card.

I didn't really care about my apps, but I hadn't backed up my photos or videos for a year. I hate Google Photos and all that "cloud" bullshit, but now it was really biting me in the ass... If there's one thing you need to take away from this article, it's backup your photos

Even though I could see all my photos, almost all of them were corrupt! Reading the files directly from the card revealed horizontal strips and chunks of the image over a pixelated (green?) color. I tried to copy the images to my PC, but everything was trapped on the card.

A quick Google search led me to ddrescue. While this seems like an incredible recovery tool, it was unable to build a usable image from the SD card... 🤔️

The images were readable from the card, but weren't displaying correctly (or at all). I couldn't copy them onto my local machine... So, finally, I thought— perhaps I could recover the broken images by compiling them into a video?

In the past, I'd used ffmpeg to convert individual stills to a video file. After another quick search, I discovered that ffmpeg not only has built-in error detection on the input frames; but it will also automatically discard irrecoverably corrupt frames.

A post on StackOverflow gave me what I needed. The user had the "-err_detect aggressive" flag on an rtsp stream in an attempt to clean the incoming live footage.

Eureka! A simple ffmpeg command using the same error detection flag within the image directory managed to recover every photo into a video file!

ffmpeg -err_detect aggressive -fflags discardcorrupt -framerate 1 -pattern_type glob -i '*.jpg' -c:v libx264 -preset:v slow OUTPUT_VIDEO_NAME.avi

After that, I opened the video in Adobe Premiere and did a simple frame export to retrieve all the individual images! 😍️ Okay, I'll admit, this was a pretty unique situation...

Aside from that awful feeling of being without a device for a week, the last thing you want is to lose years of photos and memories. So, if any of you enjoy warm, bubbly tubs with your mobile devices, perhaps you can learn something from my experience. Of course, I hope you can all avoid this disaster with the occasional backup!


N O T E S

D I S C U S S I O N