Database Develop

ADB logcat setup, etc.

I've Google'd the topic and all the comes up are my own post in the Dev sections where I asked how to create/get a logcat. I can "adb logcat" to a text file, then it shows "waiting for device". Now what's the procedure or setup on the S7 end? I've turned On adb debugging options in the S7. Can/ls this done by USB? The "adb devices" command while plugged into the USB shows nothing. I can connect in Fastboot mode and "adb devices" shows nothing also. Or is more of the Android SDK package needed for this?

Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Did you install the adb drivers?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, since I've never used adb commands in the past, maybe not! Are they installed from a EXE file or in a INF fashion?

I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.

giveen said:
I love you man
http://forum.xda-developers.com/showthread.php?t=1484406
Download and extract, boot up device, make sure ADB is turned on device, then plug it into the computer, go to My Computer > Manage > Device Management, you should see something pop up with a yellow triangle, install the driver, it will ask you for the location point it to where you extracted the download at.
Click to expand...
Click to collapse
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??

wptski said:
I may have never really installed ADB drivers, only Fastboot months ago. I feel like a real noobie again! Thinking that I missed the ADB drivers somehow I found that post on my own but take a look at the link. See anything missing??
Click to expand...
Click to collapse
Um....no?
http://d-h.st/592

giveen said:
Um....no?
http://d-h.st/592
Click to expand...
Click to collapse
Yep, that's a link to the page but where's a link to actual file download? I think the third comment on the page mentions this.
If I'm not missing the driver files, I wonder if it might be that I NVflashed CM10 again but didn't allow it to reboot before restoring a TWRP backup?

All the old links to files have been changed since the DNS problems but I found a link to the old files at StreakDroid and the DNS issued is fixed. Download, unzipped, nothing looks any different to what I already have. I still tried the package anyway and it still can't find it's driver. Next I'm going to NVflash CM10 again and let it boot up fully and try it then before restoring my TWRP backup.

I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.

jamezz98 said:
I had the same problem the other day when i flashed mine to CM10.
In the end the procedure which worked for me was to unplug the usb cable from my laptop.
Press the small button to hard power off the device.
Boot the device to CM10 again.
Plug the device in to a different USB port.
Then i went in to device manager and found a "dell" device which i right clicked then update drivers and pointed to the folder where i had the adb drivers downloaded to. It found them and installed the devices as an adbx device.
Then i unplugged from usb again and plugged it back in. At this point i ran the logcat command and it started logging.
Click to expand...
Click to collapse
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??

wptski said:
I tried exactly as you outlined and it still didn't find the needed drivers. Funny as it shows a "B10B" as the unknown device and in the two WIN32 INF files that is a Dell parameter ID.
I may try my TWRP backup to ICS-B4 again before I NVflash again sometime today.
EDIT:
Restored my TWRP ICS-B4 backup but it can't find its drivers either and I tried swapping ports also. One thing though, instead of "B10B" showing up in "Other Devices", I get "Android". An NVflash is next, maybe a TWRP backup breaks ADB??
Click to expand...
Click to collapse
Its because I was testing some things out in init.streak7.usb.rc

giveen said:
Its because I was testing some things out in init.streak7.usb.rc
Click to expand...
Click to collapse
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.

wptski said:
Ah, what do you mean? ADB isn't going to work? It didn't work after another NVflash and allowed to boot up.
Click to expand...
Click to collapse
It works just fine.

I'm stumped!

Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!

wptski said:
Got it! I had use the pick device option route which led to Android to ADB Interface or ADB Composite Interface. I selected the non-composite option, used those same files again and it installed the proper drivers. I have no idea and don't really care. What a PITA!
Click to expand...
Click to collapse
Restored my ICS-B4 backup, ran into the exact same issue and used the same solution to install the ADB drivers.

[Q] ADB Sideload isn't working for me!

Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!

Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.

Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??

You need HTC drivers , if you didn't install HTC SYNC, open "virtual CD", that appears at connection of phone with PC and you will see folders with drivers for different OS.

Thanks, mate. I already fixed the problem but I forgot to update this thread. You are right, I did not have the proper drivers, so I downloaded and installed HTC Sync Manager and then everything went great.

I had the same problem last night trying to flash my first rom ever, but thankfully i had a usb otg cable that I used to put the rom zip in my flash drive and flash it into the phone

TarekElsakka said:
Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!
Click to expand...
Click to collapse
Just get the all in one tool, ins;tall the relevant drivers and then go to recovery and select sideload a rom, go to the all in one toolkit and select sideload a rom, then choose the rom, simples
Sent from my Transformer Prime TF201 using xda premium

Thanks, guys. I ordered an OTG USB cable this morning just to avoid any future problems.

ADB

hi
im trying to use ADB to delete some bloatware off of my phone, but im having troubles doing so because it cannot find my device. ive tried updating the drivers for it through Device Manager but the phone is not listed there. however, it shows up in My Computer and i am able to transfer files onto it.
are there any other solutions or possible fix for this?
thanks.

I'm new here so I can't post links. I was having the same problem with the Adb version I was using with my old phone (mostly getting "device offline" errors).
Google "15 seconds Adb". Its an up-to-date installer that weights almost nothing and includes all the necesary drivers.
Deleted Whats New with no problem.

julianf92 said:
I'm new here so I can't post links. I was having the same problem with the Adb version I was using with my old phone (mostly getting "device offline" errors).
Google "15 seconds Adb". Its an up-to-date installer that weights almost nothing and includes all the necesary drivers.
Deleted Whats New with no problem.
Click to expand...
Click to collapse
ive tried it but it gave me an error message saying "ERROR: Invalid command line parameter '****\Desktop\adb-installer.log'."
edit: it said it installed all the drivers but my device is still not showing up

aznpiggy said:
ive tried it but it gave me an error message saying "ERROR: Invalid command line parameter '****\Desktop\adb-installer.log'."
edit: it said it installed all the drivers but my device is still not showing up
Click to expand...
Click to collapse
Do you have USB debugging enabled?

Michealtbh said:
Do you have USB debugging enabled?
Click to expand...
Click to collapse
yes i do
my computer is able to recognize my nexus 5 so idk whats going on

Have you installed the three things that come with the installer? (Adb+fastboot+drivers)?
Also: have you installed the propietary Sony software for Xperia interaction (can't remember the name, probably Xperia Connect or something like that) ? Maybe that has some drivers that you need.
I asume you also have installed the Google USB drivers installed (use 32 bit version, NOT 64).
I'm just naming all these because I had all of them already installed before I downloaded 15 seconds adb, so maybe they interact somehow and that's why it works for me.
Also make sure you are using latest version of everything.
Edit: did you get on your phone the debugging alert when you connected it?
Edit 2: please post what commands you enter into the cmd.

julianf92 said:
Have you installed the three things that come with the installer? (Adb+fastboot+drivers)?
Also: have you installed the propietary Sony software for Xperia interaction (can't remember the name, probably Xperia Connect or something like that) ? Maybe that has some drivers that you need.
I asume you also have installed the Google USB drivers installed (use 32 bit version, NOT 64).
I'm just naming all these because I had all of them already installed before I downloaded 15 seconds adb, so maybe they interact somehow and that's why it works for me.
Also make sure you are using latest version of everything.
Edit: did you get on your phone the debugging alert when you connected it?
Edit 2: please post what commands you enter into the cmd.
Click to expand...
Click to collapse
i turned on a setting on the phone where it installs a software that organizes all the media files for your phone
right before i was about to install the software, i noticed that my computer started recognizing my device
everything started working like it should since
thanks for your help
edit: i didnt and still havent installed the file managing software lol idk why it started to work

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?

@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Thanks for the reply. Unfortunately that seems to have done nothing

I'd go w/ uninstall all other drivers first, change cables and see what happens.

Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.

morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?

cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...

efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.

OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.

morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk

FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.

Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.

Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?

Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?

Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.

Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.

Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452

Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.

Question Windows driver problem for Pixel 7 for adb and fastboot? [SOLVED]

Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?

laticola said:
Longtime reader, firsttime caller. I've read as much as I can and searched for a solution, but haven't found one yet.
I have a new Pixel 7 and am trying to install LineageOS following the official instructions. I've successfully worked through the initial steps through flashing custom recovery. However, when I start on installing LineageOS from recovery, I run into a problem that after the factory reset I'm unable to sideload LineageOS because adb doesn't recognize the phone. (I can still see it in fastboot, but not with adb.)
I believe that this is a driver problem, because the phone shows up in Device Manager with a triangle.
I initially installed the drivers from here. After I discovered the problem, I also tried the universal drivers from here. Neither of these has seemed to work.
What would you suggest for what I should try next?
Click to expand...
Click to collapse
You should download the official Google drivers.

elong7681 said:
You should download the official Google drivers.
Click to expand...
Click to collapse
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?

laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Which version of platform-tools do you have? You should only be using v33.03. I would also encourage you to use the Pixel Flasher Thread 'PixelFlasher for Google Pixel 7 Support Thread.' https://forum.xda-developers.com/t/pixelflasher-for-google-pixel-7-support-thread.4505289/

laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
I suggest you follow the advice I gave and the other member ended up doing quoted below from another thread (his experience is fairly similar to yours and/or achieving the same things would get to the same end result -- might be worth reading through the whole thing) -- it seemed to work out for him...
simplepinoi177 said:
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Click to expand...
Click to collapse
GodieDan said:
SOLVED! thanks especially to @simplepinoi177 for cracking the case!
In case someone has this same problem in the future, here's the solution:
1. Open device manager and locate the misbehaving driver. If it's not obvious, plug and unplug the USB cable and watch for the appearing and disappearing entry.
2. Right-click the driver > click properties from the drop-down menu > select the driver tab > driver details
3. To be safe, use the snipping tool or something to take a picture of the file directories. Before you change anything in a system file it's always good to keep a record of how things were, but also you'll need to know the directories for the next step.
4. Unplug the device from the computer. As the directory list vanishes, use the screenshot to locate the .dll files.
5. Again to be safe, don't just delete the .dll files; instead just cut and paste into a backup folder somewhere. Also save the screenshot of the directories in the same folder, so you will know where to put them back if you need to. I didn't, and who knows, maybe I could be overcautious, but best practices and whatnot
6. Open device manager and again plug your android in. This time the driver will probably have a different name. Locate it as you did in step 1.
7. Right-click and select "uninstall device." Tick the box and say OK
8. Unplug the phone and reboot the phone and the computer both
9. Plug it back in
I have also determined the cause of my problem: Drive Booster, a program designed to automatically update drivers. It's not an unsafe program, but it is bad at installing the correct driver. I uninstalled it.
Thanks again!
Click to expand...
Click to collapse

laticola said:
I believe that I did that, but I just tried it again. I downloaded the driver package from here. I then installed them following these instructions. The result is the same: my device shows up in fastboot (if I type 'fastboot devices' I see it, and it shows up in Device Manager), but if I boot into recovery it doesn't show up - 'adb devices' show nothing, and it's not visible in Device Manager.
Is there another driver set that I should try? Or is there something else I can do to make progress with fastboot working?
Click to expand...
Click to collapse
Why do you think fastboot and recovery are the same? I haven't been in recovery for a bit but fastboot is available once connected to the computer but is recovery mode supposed to as well? Don't make me go into recovery mode please. But I thought recovery mode was device only.

I'm using platform tools v34.0.1, and I worked through the steps simplepinoi177 suggested for the drivers. I then discovered that my problem was something very basic: I was mistakenly using files for a Pixel 7 Pro instead of a Pixel 7 (my actual device). Once I flashed the correct boot, dbto, and recovery for my device, I was fine.
Apologies for the error, and thanks so much for the help. You all rock! And I will read up on Pixel Flasher.