Related
**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:
Hi All,
My GS3 has a broken screen, which displays nothing and accepts no touch input. It has an unlocked bootloader, rooted, and is running some version of CWR and a recent CM11 snapshot. The phone boots fine, is on my wifi, receives notifications, can accept Play Store app installs, etc. I figured, if I could connect over ADB, I could do a lot of neat things with the device (without replacing the screen). USB debugging is enabled, but the kicker is, I didn't "remember" my computer's RSA key, so I can't connect over ADB. I need to somehow bypass this.
Things I've thought of:
- If I could input a touch event/click, I could blindly click and hope I accepted the RSA key. With a mouse connected over USB OTG I could click, but the prompt disappears if the computer's USB cable is unplugged. I have a bluetooth mouse, but I've reflashed since the last time I paired it.
- I might be able to manually add the RSA key, by copying it from my computer and adding the line to /data/misc/adb/adb_keys. But then somehow I need to be able to write to /data. I think I might I be able to do that by booting into recovery and using adb to pull the file and push a modified one, but when I try (pull battery, hold volume up, home, power for several seconds) and connect it to my PC, nothing shows up when I run "adb devices".
- I've heard of flashing an "insecure boot image" that wouldn't ask for the RSA prompt. I wouldn't know where to start with that one and would need some hand-holding to get that done.
Does anyone have a suggestion?
Hi,
Try the second method, it should work.
i pulled the adb_keys from another phone that worked, same model.
then reboot into recovery twrp on the phone with broken screen and adb push the file to the location, reboot it and it worked.
Although this thread is really old, I came across the same problem. I used teamv*er to remote control my phone from the computer. My touch screen was non-responsive, but my lcd was still working...
I am in this same situation...
Verizon Note 3
Rooted
SafeStrap
Custom Rom (Jasmine I think)
A few days ago I broke my LCD (while in an otterbox and isn't the first time... GRRRRR.) So now I want to pull files and such from the phone using ADB or use the phone via USB with androidscreencast.jnlp (java applet) but I must have never accepted my RSA fingerprint prior to breaking the screen...
Anyone had any success bypassing the fingerprint or found another method to edit /data/misc/adb/adb_keys?
I can see the phonje via ADB...
[email protected]:~# adb devices
List of devices attached
63db4a57 unauthorized
...but with it being unauthorized I can't read/write...
Any suggestions? Thanks in advance.
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
voolandis said:
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
Click to expand...
Click to collapse
Well using adb commands is out of the question as usb debugging is not enabled. You might get somewhere by connecting a usb mouse or keyboard via otg.
voolandis said:
Hello guys, a friend of mine and I are trying to recover data from his S6 that has a broken screen and digitizer. Phone is recognized by Windows PC, but can't interact with it, since it has no USB debugging enabled. Is there any way to pull data from it? Repair is not an option, as friend is looking for an upgrade (S8 most likely).
Obviously, when connected to PC phone probably prompts for a type of connection, but as the situation states - I can't select anything, since screen is dead.
Any help?
Click to expand...
Click to collapse
Try rebooting your device into recovery, hook your phone upto your computer, and execute these commands in your terminal:
Code:
cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys
adb reboot
Wait for a while to let it boot, and execute
Code:
adb pull /sdcard/
If you didn't have USB debugging turned on, you can execute these commands after connecting your phone in recovery to your PC:
Code:
adb shell
cd /system/
echo "persist.service.adb.enable=1" >> build.prop
echo "persist.service.debuggable=1" >> build.prop
echo "persist.sys.usb.config=mtp,adb" >> build.prop
adb reboot
hope it works
LukeHammer said:
hey, buddy, I had the same problem with you last month, but I solve, I got the help from this post (recover data from broken Samsung screen), now I hope that can help you.:highfive:
Click to expand...
Click to collapse
Many thanks, but this thread is over a year and a half old.
voolandis said:
Many thanks, but this thread is over a year and a half old.
Click to expand...
Click to collapse
But you keep the link.
heidisteen said:
https://youtu.be/dnpTiYnp2A8
Click to expand...
Click to collapse
Does this helpful with my broken S5 ACTIVE?
Hello Everyone,
I would like to learn how to remove bloatware Apps from my Android phone.
I have tried using "ADB commands" but for some reason my computer doesn't recognize/find my Android phone when I connect it to it.
Please help.
Thanks in advance
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
petiolarissean said:
Download drivers for samsung and enabled adb developer option then type following "adb devices" press enter and should see serial number indicating phone connected via adb
Click to expand...
Click to collapse
Hello, and Thanks
I have done that exactly, but it still doesn't work.
And I can't figure out why is not working.
I have installed the Samsung driver, allowed the ADB function on my phone from "Developer Options" etc.
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Only to have mentioned it:
So-called bloatware typically is housed in Android's locations /system and/or /system/priv--apps what only can get accessed by Android's root-user after successfully mounted as RW.
James_Watson said:
In addition to the advices by petiolarissean , check whether the driver works well, please.
In the 'Devices Manager' of your Windows, check the driver for your Android phone.
If this doesn't work yet, change an usb cable and then try again.
Click to expand...
Click to collapse
Thanks for your help
I think I will buy a new USB cable and give it a try, hopefully it will work.
Have a nice day
Sorry late reply.I have like 5 different phone.Hard core modder.
This question help alot
Even though you csnt get adb working
Can you still move files from your phone to pc or computer.Or nothing ay all.Your answr will tell me your problem
I tried running the command - ADB devices, and it does not show my device, but when I run the command fastboot devices, then I can see my device.
I am using this to take a backup and remove the pattern from my phone as I forgot the pin here.
But most functionality is present with the ADB command.
A lot of posts have suggested checking if the USB Debugging option was on, and MTP is on, but since the phone is password locked, I am unable to check either of them.
Can you please help me out, as this phone has a lot of data that needs to be recovered?
Mija21 said:
I tried running the command - ADB devices, and it does not show my device, but when I run the command fastboot devices, then I can see my device.
I am using this to take a backup and remove the pattern from my phone as I forgot the pin here.
But most functionality is present with the ADB command.
A lot of posts have suggested checking if the USB Debugging option was on, and MTP is on, but since the phone is password locked, I am unable to check either of them.
Can you please help me out, as this phone has a lot of data that needs to be recovered?
Click to expand...
Click to collapse
I was able to get the ADB device detected by entering the recovery mode. Previously I was trying to run the command while in fastboot mode.
So I have now been able to get the ADB devices, but now I am getting device unauthorized, due to which I am unable to enter the shell.
Is there any way, where I can use ADB without clicking on the device for authorization.
Thank You in advance
If
Code:
adb devices
doesn't show your phone as connected then a connection couldn't get established. Point.
FYI: The major reason why you get "Unauthorized Error" is that you haven’t authorized your PC to recognize your device in ADB Mode. You probably haven't enabled the USB Debugging on your device and that is where you are getting the alphanumeric code. The "unauthorized message" is because you haven’t given your permissions to authorize this connection.
jwoegerbauer said:
If
Code:
adb devices
doesn't show your phone as connected then a connection couldn't get established. Point.
FYI: The major reason why you get "Unauthorized Error" is that you haven’t authorized your PC to recognize your device in ADB Mode. You probably haven't enabled the USB Debugging on your device and that is where you are getting the alphanumeric code. The "unauthorized message" is because you haven’t given your permissions to authorize this connection.
Click to expand...
Click to collapse
@jwoegerbauer That might be the case, but now there is no way to check and change or authorize as my device is locked and I do not remember the password. Is there any way I can bypass or get around this step.
Mija21 said:
@jwoegerbauer That might be the case, but now there is no way to check and change or authorize as my device is locked and I do not remember the password. Is there any way I can bypass or get around this step.
Click to expand...
Click to collapse
factory reset