I'm having a very frustrating problem with my phone. I'm trying to get the files from my TitaniumBackup folder onto my harddrive. It shows the files, it connects fine. adb devices shows the device as active.
However, when it begins to copy files over, it'll copy a few files over, and then it will say that the attached device is not functioning. adb devices then says the device is offline. I have to unplug the phone and plug it back in to get it to be online again.
I get the same problem with the adb pull command.
I don't know what's wrong. I updated my USB driver to the latest (rev 10) and it is correctly showing ADB Composite Device in my Device Manager. I'm currently on a rooted Android 4.4.4.
If anyone knows how to fix this please let me know.
Nevermind, trying a different USB cable did the trick.
Related
When I try to run the spoof-cid. It says the following...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device.
Press any key to continue . . .
It is rooted, and it does have usb debugging enabled. Mildly frustrating to say the least.
Following instructions from Here http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Do you have ADB set up properly? you can check by running adb devices and see if your device gets listed. Also, you can go to your device manager and see if your phone shows up to check if your drivers are set up properly by looking for "myHTC" or "android device".
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA
OK so I am trying the new root method and was able to push all files to my device. The device is recognized and can start when booted into the system. However, when I put my device into download mode and checked to see what port the device was on I got an error message: ">reg query HKLM\hardware\devicemap\SERIALCOMM 'reg' is not recognized as an internal or external command, operable program or batch file." I then went to the original command prompt and punched in "adb.exe devices" and had no results. I went to my Device Manager and discovered that I had "Error 10: Device Could Not Start". I uninstalled and re installed the drivers, rebooted my phone into download mode, double checked that USB Debugging was active and that the phone was MTP data transfer. Manually reinstalled drivers and nothing seems to fix the issue.....I appreciate any help that is given
EDIT: I am trying to root 20F (Lollipop)
did you resolve the issue???
Not sure if this will work or not... But I've had some luck with the old LG drivers. Uninstall your current driver and give it a shot... http://www.multiupload.nl/XEY2YR3L0I Not sure if that link works. May have to find. Lg mobile driver 3.8.1. Will upload it myself if I ever get around to it..
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
I found somewhere on xda that the problem could be solved by mounting/unmountind sdcard, but I have no ideea hoe to do that
damndaniel0 said:
hi guys I need help to recover some personal photos I had saved on my device. The phone has a broken screen and touch so I cannot use a mouse or try to blindly unlock it, but it has been rooted and usb debugging is enabled; unfortunately my pc is not authorized by the phone and I have no way to authorize it through the pop up without a screen. I have searched around many forums to find a solution but it seems every time there was something wrong, so I need some help.
The solution that got me the nearest to a conclusion that I tried are:
using adb in custom recovery (which I do have) and trying commands like "adb pull /sdcard" which resulted in "pull: building file list... 0 files pulled. 0 files skipped.", I don't understand why it's unable to pull any file.
trying to authorize usb debugging for my pc through adb by "adb push adb_keys /data/misc/adb", adb_keys is the adbkey.pub file in the .android folder renamed. I can confirm i pushed them since "adb pull /data" pulled "data/adb/misc/adb_keys" as the only file, but I still don't have authorization
I'm not too literate in this kind of commands so please be patient but I really need help
RECAP OF MY PHONE STATUS
Xiaomi Mi 10 5G is the device
both screen and digitizer broken, I'm not able to see the screen or use touch (but I'm 100% sure the phone still works)
Android 12 rom (xiaomi.eu stable)
custom recovery available
rooted device
usb debugging enabled
no device authorized by the phone for usb debug
Click to expand...
Click to collapse
There is a way to do it, but it costs money
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
xXx yYy said:
@damndaniel0
If USB-MTP mode is enabled on phone - what should be default - then you can access all user-data stored in /storage/emulated/0 directory where among others photos are stored.
See also here:
MTP USB Device Driver Windows 10 64bit Driver | Device Drivers
MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for...
oemdrivers.com
Click to expand...
Click to collapse
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
iBowToAndroid said:
There is a way to do it, but it costs money
Click to expand...
Click to collapse
what would it be
damndaniel0 said:
If you mean simply to connect the phone through usb to pc, I cannot do that because MIUI asks everytime if I want to transfer photos, files or just charge with a pop up on screnn (which I obviously cannot do)
Click to expand...
Click to collapse
Not in system but in custom recovery (which you do have).
Timmmmaaahh! said:
Not in system but in custom recovery (which you do have).
Click to expand...
Click to collapse
Honestly I did not try, but I don't remember the phone directory showing up in windows file explorer after connecting the phone in recovery mode, I'll try againg when I'm home and I'll let you know
anyway I checked and no, I cannot access phone files
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
xXx yYy said:
In Recovery mode you should can run
Code:
adb devices
adb pull <LOCATION_OF_DATA_OF_INTEREST> <STORAGE_LOCATION_ON_PC>
Click to expand...
Click to collapse
unfortunately the result of this operation is always "pull: building file list... 0 files pulled. 0 files skipped". I tried already to pull form /sdcard, /storage, /data. Am I getting the location wrong?