**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 RECOVERYfirst, 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 RECOVERYboot 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 RECOVERYboot 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 RECOVERYnow 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'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers
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
Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.
FuzzyMeep Two said:
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.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.
Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
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
alisdairjk said:
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
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.
Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.
Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:
Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:
Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.
Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.
Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?
Amazing app. thank you so much :good:
FuzzyMeep Two said:
**UPDATE**
NEW VERSION
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.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel:
I just bought a used 64GB HTC One which came rooted. It has several backups on it and tons of folders/files which have consumed half of the storage space. I want to wipe the device so it's like new and I have a fresh build to start with.
Before I mess anything up trying to wipe the device, I want to copy everything over to my PC so I can always restore things if needed. I tried exploring the device and copying the files while the phone was on but Windows sat there forever calculating the time to copy. I'm not even sure if I can copy everything while the device is on since some files may be in use.
Because of this, I thought I read that you can connect through USB by rebooting into the bootloader (white screen which says HBOOT ... is this bootloader?). My plan is to reboot into the bootloader screen, connect USB, copy the files, boot into recovery (TWRP), wipe the entire device, and restore/flash a stock AT&T image; however, the phone never says HBOOT USB PLUG when I plug in the USB cable!!
I installed HTC Sync which recognized the device and installed the drivers (shows up in device manager without any exclamations). I then uninstalled the software. After booting into the bootloader, if I plug the USB cable in, nothing happens; however, when I hit the power button to select FASTBOOT, it changes screens, I hear the device connected sound on Windows, and the device changes from FASTBOOT to FASTBOOT USB.
In the Windows device manager I see Android USB Devices - My HTC. I tried selecting My HTC, update driver software, browse my computer, selecting the Android-USB-Drivers, and it said the best drivers were already installed. I tried to manually select the driver and use have disk to browse the drivers and I get a message saying, "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems" (I have Windows Vista 32 bit OS). If I hit the power button again and switch back to BOOTLOADER, I hear the windows device disconnected sound and I only see HBOOT.
Is there a reason why it will connect to the PC under FASTBOOT but not under BOOTLOADER? How come I cannot switch drivers ... I thought I read the HTC Sync drivers don't allow the device to connect in HBOOT which is why I'm trying to update them. Do I even need to be in bootloader to copy the device contents or can I copy it all while the device is on? Lastly, do I need to get this connection working prior to wiping the device and trying to flash/restore an image in case I need to move some files back from the PC to the device (not trying to brick the device and not be able to connect it to the PC to transfer files)?
I tried selecting My HTC, updating the drivers to the Android-USB-Driver
Forgot to include these images ... I noticed I have S-On ... do I need S-Off in order to get HBOOT USB PLUG?
Followed a video on Youtube to do S-Off and eliminate tampered with. Still not able to get HBOOT USB PLUG.
DISCLAIMER: Iam NOT responsible if something happens to your phone.
Problem Description:
When I connect my HTC Explorer to PC using Data Cable NOTHING HAPPENS ,It Just CHARGES and the Menu doesn't open up.
Even When I tried USB Tethering by going into setings Manually .It says "Unable to Turn On" .I can no longer transfer files from phone to PC .
Have you tried
1. Reinstalling HTC Sync and Drivers
2. Rebooting and Hard Reset
3. Flashing Custom ROM's
4. Using Different Data Cables
But still NO LUCK !!!
First Let's Check Whether it's a Hardware Problem (NOT NECESSARY)
1. Go into Bootloader and then to Fastboot Menu
2. Connect your Phone to PC
3. Now the Phone should Read as "Fastboot USB"
4. Try this Fastboot Command "FASTBOOT DEVICES"
5. If your Phone is Shown in the list ,It's Just a Software Problem and Continue Reading this thread
.If not ,then it's mostly a Hardware Issue
Solution:
1. Download PDANet on your phone (NOT THE APK) (This is for USB Tethering)
2. Connect your Phone using Data cable with Windows Logged On (Nothing will happen)
3. Restart your PC (DONT remove your Phone)
4. As soon as PC starts up ,you'll see the Menu on your Phone that used to appear (You'll see Disk Drive,USB Tetheing....)
5. Make Sure USB Debugging is ON
6. When you're logged into Windows, Select Disk Drive from the Menu on your phone
7. Wait and you're Memory Card will be recoginsed on PC
8. Open PDAnet.exe from Memory Card and Install
USB Tethering will now work (If still not working ,go into settings->wireless and networks->mobile networks->access point names and try changing access point ,then try PDANet again)
This WORKED for me ,:good:
So Next time ,Follow Step 2,3,4 and 5
Then After you log on, Choose Anything you want from Menu on Phone.
I doubt USB Tethering will work directly .But you can use it from PDANet.:good:
Is it possible? I tried a couple of methods but it always ended up with the "error: device not found". My solution was to put it in the sdcard and spare it from any kind of wipe but i'm a curious person and i'd like to hear more opinions. Long story short is it possible to run a .zip file from the bootloader/recovery without booting the Phone first to enable the USB debugging?
It's possible in recovery on Linux. I've done it in Ubuntu. I can't do it in WinXP, but maybe it's possible in newer versions of Windows.
My logic is: you can always use fastboot commands when in bootloader. But adb commands in recovery require the device to be recognized. This is a bit of a pain in the *ss because mostly Windows doesn't install the drivers correctly when you are in recovery mode. In your device tree it is recognized as a unknown device and you have to install the motorola drivers manually. Then you can use adb to push pull files i guess.
I've confirmed ADB push works in TWRP Recovery (probably others), on a PC running Windows 7.
I was trying to install a couple of different custom roms on my phone. I have TWRP as the recovery tool. I tried a rom called ATT Buckeye and it seems to have bricked the phone. I don't have any other roms copied to the internal storage to try to flash them. I can reset to factory defaults both through holding the volume and power down and through TWRP, but I'm not able to start into a system. The only thing I can do is boot into TWRP 2.7.0.0
I saw that I can copy files using ADB, but it says "device not found" when I am connected and run adb shell. I have the drivers from LG's website installed, but there is a yellow exclamation mark on it in device manager. I found a thread where it says that I should be able to get the drivers from the Android developer SDK. I also found the individual download for Google USB drivers. In both cases, Windows isn't able to find any drivers in the USB drivers folder. I'm not sure what else I can do to revive my phone. At this point, I'd like to just get it working again any way possible.
I used this to fix my phone http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Then I was able to load Cloudy G2 http://forum.xda-developers.com/showthread.php?t=2783192
Good to go