Develop Bugs

[Q] ADB shell error 'adb error device not found'

Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.

I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2

Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250

no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff

getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff

Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3

[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.

Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff

[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.

Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff

[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app

pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722

Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks

NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250

Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps

[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL

I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050

This involves unnecessarily deleting the contents of the internal sdcard.
The following method works 99% of the time, albeit in linux only:
1: reboot into recovery & do a mount usb storage (no mount sdcard)
this will just present your internal storage as a mass storage device to the system
2: do a
fsck.vfat /dev/sdX or /dev/ubX (whatever it gets detected as) - you can find out via (dmesg|tail)
Analogically, you can fix your data partition if it got corrupted.
You need to do it from recovery since not all roms have the fsck binaries available:
from recovery (copy - paste, unless you know what you're doing):
umount /cache
for x in {2,3,5}, do fsck.ext4 -fyD /dev/block/mmcblk0p1$x;sync;done;clear;echo done

XsMagical said:
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.

movadoevo8 said:
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
Click to expand...
Click to collapse
what is your base number and hboot ?normally the sdcard thing is fixed long time ago

One-X-master said:
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
Click to expand...
Click to collapse
How do i locate the Hboot number is that the serial# if so here it is HT265W300361

movadoevo8 said:
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
Click to expand...
Click to collapse
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there

One-X-master said:
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
Click to expand...
Click to collapse
hboot = 1.14.0002

movadoevo8 said:
hboot = 1.14.0002
Click to expand...
Click to collapse
do you have the one xl? try to update it to latest base

One-X-master said:
do you have the one xl? try to update it to latest base
Click to expand...
Click to collapse
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.

movadoevo8 said:
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
Click to expand...
Click to collapse
can you not mount adb sideload and flash through that ?

I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2

markb63 said:
can you not mount adb sideload and flash through that ?
Click to expand...
Click to collapse
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
One-X-master said:
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.

movadoevo8 said:
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
Click to expand...
Click to collapse
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!

markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?

movadoevo8 said:
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
Click to expand...
Click to collapse
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?

markb63 said:
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
Click to expand...
Click to collapse
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.

movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours

movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2

One-X-master said:
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I'm setting this up on my windows 7 machine, now I think i had an issue once on win 8. Updates to follow, thanks.

markb63 said:
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
Click to expand...
Click to collapse

gnex toolkit problem

hello
i'm not new to the forum and the phones but i'm a noob when it comes to root.
i'm trying to install gnex toolkit: http://forum.xda-developers.com/showthread.php?t=1614827
and i'm trying to install adb and fastboot and am following this steps:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
but itried everything in the last link but i cannot see my devices when i do in command adb devices.
i tried with the program usbdeview and i can see my device but the link says i have to see the adb driver but it's not there. i installed al the thing it said i needed from the android sdk but i cannot get my phone connected who is in usb debugging mode by the way
So can someone please help me. i really want to unlock or root my phone.

Please keep the questions in the Q&A section. Development is reserved for only dev related items. :highfive:

put on your big boy pants and follow this:
http://forum.xda-developers.com/showthread.php?t=1529058

Zepius said:
put on your big boy pants and follow this:
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
it doesn't work: every time i try adb devices in command it just says list of devices atached and then nothing underneath?
and i followed every step

nielsvg said:
it doesn't work: every time i try adb devices in command it just says list of devices atached and then nothing underneath?
and i followed every step
Click to expand...
Click to collapse
Is usb debugging on on the GNex?

yes debugging is on

i restarted my laptop and now when i do adb devices it says:
*daemon not running. starting it now on port 5037*
*daemon started succesfully*
List of devices attached
but then nothing anymore. just a new commandline

uninstall your drivers and use the ones from the guide i linked.

Zepius said:
uninstall your drivers and use the ones from the guide i linked.
Click to expand...
Click to collapse
i did an uninstall and installed the adb for dummies but everytime i trie adb devices it doesnt list any device

nielsvg said:
i did an uninstall and installed the adb for dummies but everytime i trie adb devices it doesnt list any device
Click to expand...
Click to collapse
Use the 1wayjonny's drivers from here. Uninstall all the other drivers, including any hidden drivers, boot your phone normally with USB Debugging enabled in dev settings. Then install the driver manually, i.e., unzip it to a location, then right click on the device in device manager, and install, but don't select auto, select "you choose" (or whatever it is called), and then select "select from a list" and "have disk", and browse to the location where you unzipped the drivers.

efrant said:
Use the 1wayjonny's drivers from here. Uninstall all the other drivers, including any hidden drivers, boot your phone normally with USB Debugging enabled in dev settings. Then install the driver manually, i.e., unzip it to a location, then right click on the device in device manager, and install, but don't select auto, select "you choose" (or whatever it is called), and then select "select from a list" and "have disk", and browse to the location where you unzipped the drivers.
Click to expand...
Click to collapse
tried it but when i try to install the drivers manually but it says that there are no new or better drivers? and i installed the old drivers first

I would uninstall all drivers first. Reboot. Then reinstall the drivers efrant told you.
Sent from my i9250

bk201doesntexist said:
I would uninstall all drivers first. Reboot. Then reinstall the drivers efrant told you.
Sent from my i9250
Click to expand...
Click to collapse
and how can i easily uninstall them?

Google? Windows forum?
Sent from my i9250

bk201doesntexist said:
Google? Windows forum?
Sent from my i9250
Click to expand...
Click to collapse
so i finally got to see my device with adb devices
but now i'm scared to do something wrong and brik my device or something

...use a toolkit. //sarcasm
http://forum.xda-developers.com/showthread.php?t=1812959
Sent from my i9250

bk201doesntexist said:
...use a toolkit. //sarcasm
http://forum.xda-developers.com/showthread.php?t=1812959
Sent from my i9250
Click to expand...
Click to collapse
i'm using the toolkit
but i restart my pc and try adb devices and my device is listed.
then i start gnex toolkit and try to make an entire backup and then it just keeps saying waiting adb
and nothing
then i try the command adb devices again and my device is not listed anymore.

bk201doesntexist said:
...use a toolkit. //sarcasm
Click to expand...
Click to collapse
nielsvg said:
i'm using the toolkit
Click to expand...
Click to collapse
Even when you explicitly state the sarcasm.........
OP: Don't use the toolkit. Go to the thread bk201doesntexist linked and learn to do it properly.

Cilraaz said:
Even when you explicitly state the sarcasm.........
OP: Don't use the toolkit. Go to the thread bk201doesntexist linked and learn to do it properly.
Click to expand...
Click to collapse
cant just anyone do it for me with teamviewer or something?

nielsvg said:
cant just anyone do it for me with teamviewer or something?
Click to expand...
Click to collapse
Tell me how to use team viewer, and I'll help you.

Cant get fastboot to work!

I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?

Digital signature of the driver or wrong drivers is the problem

joedoctor said:
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Click to expand...
Click to collapse
u are not saying mutch about how u are trying to enter fastboot
u do know the phone must be turn into fastboot right ?

...
same here, done everything i can...

mockneygeeza said:
same here, done everything i can...
Click to expand...
Click to collapse
to get fastboot to work u need to reboot the phone into fastboot

-fluffy- said:
to get fastboot to work u need to reboot the phone into fastboot
Click to expand...
Click to collapse
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol

moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
I'm going to try the above, it's never too late ?

moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers

-fluffy- said:
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
Click to expand...
Click to collapse
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.

moeq123 said:
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
Click to expand...
Click to collapse
im on windows 10 also an my adb devices also show nothing but i can still flash recovery an all

Question Pixel 6 pro drivers

Okay I got a problem I just got mine finally today in the mail. my Windows 10 recognizes it in ADB but as soon as I go to fastboot no matter what I do it's like it doesn't see the drivers anymore. Anybody have an idea how to get around this so I can unlock the bootloader?
Edit:. Nevermind I finally found a driver package that worked. What a deal

Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb

You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools

DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?

Flippy125 said:
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
I finally figured it out. Found the right drivers. Took me forever

DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked

mac796 said:
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
Click to expand...
Click to collapse
Please could you share the driver pack that worked for you?

Then just let us know which driver you installed so that the Pixel 6 was recognized. And a download link wouldn't be bad either - that helps others with the same problem.

Try Download Minimal ADB and Fastboot Tool it should work
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
After you install it ensure you update SDK Platform Tools the file name " ADB "
/c/adb

cd993 said:
Please could you share the driver pack that worked for you?
Click to expand...
Click to collapse
Yet Another Universal ADB Driver Package and adbupdater for Windows
I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before. While at it I added those two tools usually used, that is adb and fastboot. Based on batch scripts, so it's open source. Self Signed, not...
forum.xda-developers.com

Sorry took me a bit to find it again

mac796 said:
Sorry took me a bit to find it again
Click to expand...
Click to collapse
Thanks will give this a try later on!

On Windows 11 the official r13 Google USB Driver pack worked - but only after booting into an alternative mode that allows unsigned drivers. For some reason Google's drivers are not signed, and Win11, with TPM+SecureBoot refuses to load those drivers in normal mode.

cd993 said:
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Click to expand...
Click to collapse
It sounds like you're talking about accessing the phone's storage via MTP. When you plug the phone into the computer, you may need to choose the new notification regarding charging and switch it to the mode to be able to access the storage. Probably defaults to "Charging this device via USB", and you need to click on it and select something like "File transfer/ Android Auto". This won't require any new Windows drivers.
Please correct me if you're not talking about accessing the phone's storage.

mac796 said:
I finally figured it out. Found the right drivers. Took me forever
Click to expand...
Click to collapse
Would you mind saying WHICH drivers? Thanks...

wsalopek said:
Would you mind saying WHICH drivers? Thanks...
Click to expand...
Click to collapse
I posted it in this thread. Read it. There's a link

mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
OK...thanks...got it.

mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
wsalopek said:
OK...thanks...got it.
Click to expand...
Click to collapse
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.

roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).

My problem ended up being that my USB Hub went bad... Was getting Yellow Exclamation in Device Manager and an error when going into Fastboot. Once I plugged directly into the PC, no issues. New hub ordered!