Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all
BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.
follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",
Related
I figured it out!
I'm having trouble getting my computer to recognize my phone as an ADB device. I have an HTC EVO, running cyanogen 6.1. I've downloaded the android SDK, as well as several of the SDK components (Google-usb-driver, platform-tools, and several APIs).
When I plug in my phone, my computer would not recognize it as an ADB device, so i removed the drivers from my computer and tried again. I attempted to manually install the drivers from the file (C:\android-sdk-windows\google-usb_driver) with no luck. I tried going into the amd64 file (I'm running windows 7, 64bit), but my computer would not recognize the drivers.
I'm new to all of this (this is my first post)- any and all help would be greatly appreciated
I am having the same problem with a HTC Hero (Sprint) tried everything but i can't get my pc to regocnize the adb driver
same thing with stratosphere.
I have the same problem with an unrooted samsung stratosphere. I need to install the adb drivers to use the smartdog remote web desktop through usb. The samsung usb drivers are already installed so it won't let me install the adb drivers. What can I do?
Funny I thought I was having problems with ADB cuz I'm on a Mac but it appears you Windows catz are SOL too...WTF is up with ADB not recognizing devices? Somebody should have a fix or some info on this, so frustrating, I just wanna root my damn devices!
had the same issue. here what I did and it worked:
- go to junefabric dot com
- download and install PDANet( 'cause it got adb usb driver in it)
- uninstall PDANet( if you have no use of it. don't worry, adb usb driver doesn't uninstall)
Hi, I'm having an extremly annoyning issue with my S8530. I can't seem to make Windows XP SP3 32-bit recognize properly my phone. I have install all the drivers I could find (old, new, from official site, from the undergorund of the internet) and it still gets stuck on detectic USB Serial Port giving just the message that something went wrong and it can't install driver (from auto-detecting devices from Windows). It did install Composit and Modem parts of the drivers but it allways stuck at that part no matter what driver I pre-install, how many restart I do to the PC, how many USB ports I keep chainging, how many USB cables I swap, how many restart I give to the phone. I'm starting going bananananananananananananananananananas.
Any ideeas are greatly apriciated.
Respect Ovidiu
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Renate NST said:
Are you trying to get the USB Mass Storage to work or the ADB over USB?
The normal Windows Mass Storage driver should work on anything.
If you are trying to get the ADB driver to work you may need to
add your VID/PID to the INF file for the ADB driver.
Click to expand...
Click to collapse
ADB over USB so I can make Kies recognize my phone, wich won't work in Mass Storage. And it should be plug and play (after installing Kies wich installs the drivers or by just intalling the drivers alone). I don't have other machines to trie with Windows 7 (wich allways worked before) and my current PC barelly handles 5 open tabs of Chrome so no Windows 7 options here.
Plug your phone into the Windows box.
Go to Device Manager and find under Properties the VID/PID.
Check the INF file for the ADB driver and see if your IDs are in there.
If not, make a section like all the other sections with your VID/PID in it.
Install the driver.
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).
I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try
I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You
Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable
By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..
@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com
@jwoegerbauer , you're funny guy...