[TOOL] ADB Data Recovery (recover data from a phone with broken screen)

Search This thread

ossarotte

New member
May 16, 2008
4
0
object not exist

i connect the samsung i9070 nad when i run adb devices that return
Code:
C:\Android\platform-tools>adb devices
List of devices attached
705CD4E6FCBECC154EC9FA6C5D068D5 device
i run recover data (2.0) but whe i try for recover an error message occurs

Code:
C:\Android\platform-tools>adb -d pull sdcard/DCIM/ C:\RecoveredData
remote object 'sdcard/DCIM/' does not exist
Premere un tasto per continuare . . .

this phone have no root or debug mode....

any solution for fix and recover??
 

FuzzyMeep Two

Senior Member
Feb 21, 2012
119
318
Southern NH
If you're having issues...

For anyone having issues...

If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB

SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERY​
first, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING

SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERY​
boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program

SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERY​
boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program


SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERY​
now things get complicated...


*The following is paraphrased from this site

1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page

2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode

[FASTBOOT]​
3. Connect your device to your computer via USB and wait till you see the PC recognize the device

to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices

you will see a list of connected devices. if not, something went wrong.

4. Launch Command Prompt and type the following commands;

cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img

5. Wait for the process to finish.

6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program

[RECOVERY MODE (SAMSUNG)]​
USE THE INSTRUCTIONS ON THIS PAGE

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program


HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
 
  • Like
Reactions: Abdullah Akbar

FuzzyMeep Two

Senior Member
Feb 21, 2012
119
318
Southern NH
i connect the samsung i9070 nad when i run adb devices that return
Code:
C:\Android\platform-tools>adb devices
List of devices attached
705CD4E6FCBECC154EC9FA6C5D068D5 device
i run recover data (2.0) but whe i try for recover an error message occurs

Code:
C:\Android\platform-tools>adb -d pull sdcard/DCIM/ C:\RecoveredData
remote object 'sdcard/DCIM/' does not exist
Premere un tasto per continuare . . .

this phone have no root or debug mode....

any solution for fix and recover??

try recovering the whole sd card. (adb -d pull sdcard/ C:\RecoveredData)
it seems like your pictures are saved in a different location. or the root of the sd card is not named "sdcard"
 

FuzzyMeep Two

Senior Member
Feb 21, 2012
119
318
Southern NH
It was made using a Samsung. Some phones save their photos in a different location. If you have issues, pull the whole SD card then find your pictures.
 

cristina2014

New member
Nov 12, 2014
3
0
how to recover lost data from android

Please do not worry now! Actually, all you lose the data is still on your Android phone or Android SD card. You can not find lost again without the file recovery tool. The only way is to use a data recovery software for Android so you can retrieve lost data from your mobile phone Android. Before trying to use some software similar function, but the effect is not ideal, through friend introduction later I used the Android Data Recovery software is sharing today.
 

Albercook

Member
Mar 14, 2015
8
0
Malware?

Comodo Security comes up with the following error when I try to run RecoverData(2).exe
It calls it
TrojWare.Win32.Refroso.bj
 

FuzzyMeep Two

Senior Member
Feb 21, 2012
119
318
Southern NH
Comodo Security comes up with the following error when I try to run RecoverData(2).exe
It calls it
TrojWare.Win32.Refroso.bj
I assure you there is no virus. It is just a batch script compiled to EXE.

This has happened to other programs before, it is a false alarm
http://xdaforums.com/showthread.php?t=1489879

This has almost 10,000 downloads, and this is the first time anyone has posted an issue regarding virus scan. Did you figure it out.
 

Y4M1

Member
Mar 31, 2011
28
2
Hi, I have a problem with my friend's Samsung GT-i9505. She managed to break the screen and digitizer, and now she wants me to recover the data from the phone. She has locked the phone with some sort of a password so kies 3 won't let me back up the data. I can't tell weather I'm in download mode or any other state of the phone, does download mode have any special color of LED light above the screen? I'm running out of options, can't see the phone while typing "adb devices" in cmd line. HELP?! ;-;
 

uzairali82

New member
Aug 20, 2015
2
0
Hi, i have a problem with my Nexus5, it stucks in boot animation and not booting up. I need to recover the data (as there is no backup :( ) but its not rooted and debug option is also disabled. I am going through the instructions but when i tried to write recovery its showing below message.

Code:
C:\Android\sdk\platform-tools>fastboot.exe flash recovery d:\recovery-nexus5.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11308 KB)...
OKAY [  0.550s]
writing 'recovery'...
FAILED (remote: not supported in locked device)
finished. total time: 0.656s

I need to recover the images, as it contains my kids pictures.
 

hiteshonline

Senior Member
Aug 20, 2015
64
12
Chicago
**UPDATE**
NEW VERSION

THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.

Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.







For anyone having issues...

If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB

SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERY​
first, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING

SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERY​
boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program

SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERY​
boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program


SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERY​
now things get complicated...


*The following is paraphrased from this site

1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page

2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode

[FASTBOOT]​
3. Connect your device to your computer via USB and wait till you see the PC recognize the device

to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices

you will see a list of connected devices. if not, something went wrong.

4. Launch Command Prompt and type the following commands;

cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img

5. Wait for the process to finish.

6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program

[RECOVERY MODE (SAMSUNG)]​
USE THE INSTRUCTIONS ON THIS PAGE

Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices

The result should be something like

List of devices attached
051a4dd5 recovery
^^this number will be different for you

if you get a result on ADB devices, then you can use the program


HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.



Don't forget to hit "Thanks"

I just want to say thank you to you. No words.
 
  • Like
Reactions: FuzzyMeep Two

FuzzyMeep Two

Senior Member
Feb 21, 2012
119
318
Southern NH
It should. However, sometimes phone manufacturers use different folders for things like pictures. So, samsung may use SDCARD/DCIM, but HTC may use something like SDCARD/Pictures. This was made using the folder structure of a galaxy s2. The way around that is to just dump the whole internal SD card rather than using the individual folder selection.

You also do need ADB enabled, but the steps for how to do that should be covered in my first post.
 
  • Like
Reactions: occtec

juicyjuicy

New member
Oct 30, 2015
1
0
Hi, I've been trying to use this tool to get my files off my Samsung Galaxy S4 with screen and display broken. I've got the custom recovery loaded and my phone shows up in adb devices. However when i run the program nothing is pulled from the phone. I've tried to pull the whole sd card. If I try the DCIM it says it doesn't exist. It goes to the pulling and copying screen but doesn't pull any files.

Any ideas?

It's a Japanese model if that makes any difference, provided by NTT Docomo.
 
Last edited:

Andreus94

Senior Member
Jan 11, 2014
273
57
Hi! I have a galaxy s advance with the screen broken. I have not root or debug USB but I use temporary Cwm recovery to use adb. The problem is that sdcard is the external sd. I tried manually to search sdcard but sdcard doesn't appear on the list when I put the lb command. How can I recover my files if I don't see sdcard0? Is there a way to enable debug USB through adb and recovery? My only problem is the lockscreen that doesn't permit to manage mtp device
 
Last edited:

queetiano

Member
Nov 23, 2015
16
0
How to get lost /deleted data back .One of the best and fastest way to start your android device into recovery mode. If you lost data contacts/messages on android internal memory .When you need to recover ,you have to root your android device. If lost data from SD Card ,you can use Android Recovery software to recover data directly.

This seems a pretty nice option. thanks
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 58
    **UPDATE**
    NEW VERSION

    THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.

    Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
    ----------------------------------------------------------------------------------------------------------------
    Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.







    For anyone having issues...

    If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB

    SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERY​
    first, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
    HOW TO ENABLE USB DEBUGGING

    SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERY​
    boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
    HOW TO BOOT TO RECOVERY

    Once in custom recovery, connect the device to the PC.
    open CMD and enter the following commands;
    cd c:\android (this is your ADB path, c:\android is default)
    adb devices

    The result should be something like

    List of devices attached
    051a4dd5 recovery
    ^^this number will be different for you

    if you get a result on ADB devices, then you can use the program

    SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERY​
    boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
    HOW TO BOOT TO RECOVERY

    Once in custom recovery, connect the device to the PC.
    open CMD and enter the following commands;
    cd c:\android (this is your ADB path, c:\android is default)
    adb devices

    The result should be something like

    List of devices attached
    051a4dd5 recovery
    ^^this number will be different for you

    if you get a result on ADB devices, then you can use the program


    SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERY​
    now things get complicated...


    *The following is paraphrased from this site

    1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
    Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
    I recommend clockwork mod non touch from this page

    2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
    (most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
    how to boot to fastboot or download mode

    [FASTBOOT]​
    3. Connect your device to your computer via USB and wait till you see the PC recognize the device

    to check if your device is in fastboot and connected use CMD and enter the following commands;
    cd c:\android (this is your ADB path, c:\android is default)
    fastboot devices

    you will see a list of connected devices. if not, something went wrong.

    4. Launch Command Prompt and type the following commands;

    cd c:\android (this is your ADB path, c:\android is default)
    fastboot flash recovery c:\recovery.img

    5. Wait for the process to finish.

    6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
    HOW TO BOOT TO RECOVERY

    Once in custom recovery, connect the device to the PC.
    open CMD and enter the following commands;
    cd c:\android (this is your ADB path, c:\android is default)
    adb devices

    The result should be something like

    List of devices attached
    051a4dd5 recovery
    ^^this number will be different for you

    if you get a result on ADB devices, then you can use the program

    [RECOVERY MODE (SAMSUNG)]​
    USE THE INSTRUCTIONS ON THIS PAGE

    Once in custom recovery, connect the device to the PC.
    open CMD and enter the following commands;
    cd c:\android (this is your ADB path, c:\android is default)
    adb devices

    The result should be something like

    List of devices attached
    051a4dd5 recovery
    ^^this number will be different for you

    if you get a result on ADB devices, then you can use the program


    HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.



    Don't forget to hit "Thanks"
    2
    i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
    2
    Thank you!

    I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!

    :good:


    Thanks again!

    -th3r3isnospoon
    1
    Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.






    P.S. I apologize if i have posted this in the wrong place, if so please let me know.

    Really great stuff - so simple but so effective. Cheers and thanks.
    1
    Error msg

    Really great stuff - so simple but so effective. Cheers and thanks.

    When i run that tool, i get the error mesg: more than one device and emulator,
    I dont want to uninstall the emulator coz it was a headache getting it running
    How i procede to select the device to be used