4 ms·
If USB Debugging is enabled, you should be fine. The first thing you'll need is Google's platform tools, as well as a compatible ADB driver for your device if
by AussieWog93 4y ago
If USB Debugging is enabled, you should be fine.
The first thing you'll need is Google's platform tools, as well as a compatible ADB driver for your device if you're on Windows.
Then, you can use `adb pull` to copy data from the phone's filesystem to Windows.
Edit: another commenter rightly pointed out that this might not work when your phone is locked.
A quick search found some really interesting tools in this thread here (srcpy especially seems amazing!):
https://stackoverflow.com/questions/29072501/how-to-unlock-android-phone-through-adb https://stackoverflow.com/questions/29072501/how-to-unlock-a...
- glitchc 4y agoSeconded, adb tools is the best way to recover files in this scenario. No need to replace the screen as others have suggested.
- francisduvivier 4y ago+1 for scrcpy https://github.com/Genymobile/scrcpy https://github.com/Genymobile/scrcpy
- dotancohen 4y agoI came to suggest scrcpy - I've successfully saved data off a locked phone with a broken screen using scrcpy.
- mahathu 4y agoUnfortunately, the phone seems to be in "charge only" instead of on MTP (media transfer protocol), i.e. it is not reachable via adb. Shame.
- Anon1096 4y agoAnother +1 for scrcpy, I've actually been in this exact situation before of having a functioning phone with a broken display/touchscreen, and was able to operate my phone through scrcpy until I got a replacement screen. Real lifesaver, amazing software.
- encryptluks2 4y agoTrue, but the chances of scrcpy being enabled on an Android device is limited and you also have to authenticate the computer connecting to the device from the device itself which most likely requires a touch screen. There may be a way to access the encrypted partition itself though using the hardware buttons, and then run a command to mount the encrypted partition.
- mahathu 4y agoscrpy (and adb in general) looks amazing! Unfortunately, ADB doesn't recognize my device yet ("no devices/emulators found"). I'll keep trying. Thanks for the answer.