Related
I have a droid x2, and im using the same computer I used for my fascinate/charge. I themed on my fasc/charge and adb worked fine, I could push pull remount, you name it. Now with this x2 everything but adb pull doesnt work. I am rooted, im running a custom rom, I have all the updated drivers, My paths are correct cuz im using the same computer, everytime I adb push I get permission denied, and if I go to adb remount I get Operation not permitted. Im not sure what the problem is.
Uninstall drivers, install easytether/pdanet drivers, plug phone in and let install. Try the micro sd adaptor that came with the phone.
Possible fix
I ran in to a Bionic where even the drivers from Moto and the ADB related ones ALL INSTALLED EVERYTHING was good adb devices picked up the phone but anytime I tried to push or pull I got permission denied. I even tried running adb shell then su then running adb push still to no avail.
MY QUICK FIX...
I rebooted the phone in to recovery adb reboot recovery [if it will take the command].
WAIT as it will need to install drivers again when recovery loads [I am using the official Open Source CWR].
Those all installed again with no issues.
Then you need to go to either mounts and storage or advanced>mounts and storage [forgert off hand]. I chose to mount EVERYTHING, but you prolly only need the sdcard-ext [top option not bottom USB mount]
Then when I ran adb push low and behold it went through with no issues.
Once that was done I restarted [this time bootloader per pathsaver steps] and proceeded to flash via RSD.
When this completes and I am able to test I will see how it reacts when I load in to OS after re-flash [via default RSD image not a custom ROM] and I get everything running.
problem
I can not istaliram, where can I find a detailed explanation?
**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:
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 have a Moto G xt1033 with no operating system.
I can recognize the device using fastboot devices and adb devices. (drivers are installed properly)
CWM recovery is installed properly.
There's no operating system and the sdcard is empty.
When I try to use the command adb push to get the rom.zip into the sd card (or data/media folder) it just won't work, it will give me a 'protocol failure' after a couple of seconds.
When I try to use the command adb sideload it will immediately crash (at 2%) and give me the error: failed to write data 'protocol fault <no status>'.
I've also tried to install a stock rom using flashing through fastboot, but it also failed.
Anyone has any idea of how I can save this phone?
It sounds like something is not right with your ADB / Fastboot setup. What operating system is on the PC / Laptop?
You might want to try reinstalling ADB:
http://forum.xda-developers.com/showthread.php?t=2317790
Alternatively, a quick way to get access to Recovery Mode ADB is to use Linux, either as a LiveCD or full install. The command to install ADB / Fastboot on Ubuntu is:
sudo apt-get install android-tools-adb android-tools-fastboot
Thanks for the tips, my computer's OS is Windows 7, but the problem was related to my computer's front USB ports, all 6 of them. As soon as I connected to one of my back USB port it worked.. Most likely because my front ports are 2.0 and the back ones 3.0. Never thought it would make a difference in this case, kinda feel stupid for having wasted so much time looking for a solution when it was so simple.
Thanks for the reply anyway @lost101.
XT1032
Am experiencing the same problem,
unable to sideload/push stock rom gets stuck on push at 31%
Recovery CMW, able to boot into recovery
getvar=all, i don't even have imei shown in that!
pls help me fix it...
Thanks a load in advance
As soon as I select 'ADB sideload' on TWRP, the phone is no longer recognized by the desktop computer nor ADB.exe...
But when I select cancel, the device is then recognized. This is version 3.3.1-0
Edit: It seems to only logical solution is to use 'adb push [image_name] /sdcard/.'
Hello. I am trying to use rootmyvalet.apk to root my phone. I am extremely confused on how to do this.
Here are the steps on how to do it...
The Second way (app way):
1)Push the su binary to /data/local/tmp using adb push su /data/local/tmp
2)Push the roothandler binary to /data/local/tmp using adb push roothandler /data/local/tmp
3)Set the roothandler binary permission using adb shell chmod 0755 /data/local/tmp/roothandler
4)Push the installsu.sh script to /data/local/tmp using adb push installsu.sh /data/local/tmp
5)Set the installsu.sh script the execution permission using adb shell chmod 0755 /data/local/tmp/installsu.sh
6)Install the APK using adb install RootMyValet.apk. If that does not work then type the full path to the apk. E.G. adb install /path/to/apk/app.apk
Start the app on the device, hit the button that says "Push SU Binary"
Wait about a minute
Enjoy your root!
If root fails, try rebooting the device
Which of the steps have you taken so far? Where did you get to in that list?
KodyChristianson said:
Which of the steps have you taken so far? Where did you get to in that list?
Click to expand...
Click to collapse
Sadly enough, I am stuck on step one. I'm probably going to need help on every single step.
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
KodyChristianson said:
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
Click to expand...
Click to collapse
1) To install the drivers, I use connect to PC right?
2) To run the command adb push su /data/local/tmp , do I use command prompt?
Use the "package" which is at the start of the guide linked above.
KodyChristianson said:
Use the "package" which is at the start of the guide linked above.
Click to expand...
Click to collapse
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
CurtisNHL1 said:
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
Click to expand...
Click to collapse
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
KodyChristianson said:
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
Click to expand...
Click to collapse
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
CurtisNHL1 said:
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
Click to expand...
Click to collapse
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
KodyChristianson said:
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
Click to expand...
Click to collapse
Believe it or not, the information you told me here just saved my ass. I recently bought a phone that could be rooted and got it stuck in a boot loop. Thank you so much!