Database Develop

[Q] need help if someone can...

ok i tryied to use all in one tool and i want to flash to ics to my thrill but as far as i got is on the tool it goes to stage 2 but waiting for device stays there even after i do place to battery in it.. it acts all over again as if it cant find the driver for cosmo i think that is what it is called....but im running windows 7

When it says waiting on device try pulling out the usb and then plug it right back in. I use to have to do that, but if that doesn't work then it may be a driver issue.
Maybe start the tool and when it says waiting for omap4430 device, hold down vol+ and plug in your phone but don't let go of vol+. Pop in battery like normal and it should boot you into download mode. See if that helps get your LG Cosmo driver to install, though it should install as LGE CDMA USB SERIAL PORT. if that doesn't happen, as a last resort uninstall all LG mobile drivers, reboot cpu, download the files from step 1 and step 5 of this post---> http://forum.xda-developers.com/showthread.php?p=39269819 (bag of goodies and wkparks 1.21) Turn off your anti virus and windows defender before doing anything. Once thats done unzip the two files mentioned above. Run the omap flash installer and re install both Sets of LG mobile drivers in the bag of goodies package (second set will pop up a warning for unsigned drivers a few times; hit YES do it anyways, and then re install omap by directing the driver update to the windows drivers folder in the wkparks bootloader1.21 tool. Hopefully this helps.
Here is a much better explaination from drastic00's tutorial. Follow these steps to the T and you should be flashing in no time
" A) Uninstall any LG Drivers:
a1) Open Programs and Features through Control Panel
a2)Find any drivers called "LG United Mobile Driver." Right click and select Uninstall, let it work.
a3)Reboot your pc!
B) Be sure you disabled antivirus/Windows Defender, etc. before unpacking these files.
C) Install OMAP4430 by running "OMAPFlashInstaller."
NOTE: if you have Fastboot installed SKIP this step (if you don't know, you don't have it...), but DO link the driver as in f4.
D) Install the two LG Drivers in the “LG United Mobile Drivers” folder: These are “LGUnitedMobileDriver_S497CA20_WHQL_ML_Ver_1. 0” and “LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1. 0” The second one will warn it is unsigned, choose to install anyway (you will have to insist on this a few times here).
E)Reboot your pc!
F)Install PC/phone drivers:
f1)Shut down your phone. Remove external sd card, SIM card and battery.
f2) Open Device Manager from Control Panel
f3) Hold volume up on phone and connect to USB port. Keep holding volume up.
f4)Look for "OMAP4430" blinking on and off in Device Manager with a yellow question mark under "Other Devices." (You can let go of the phone). If you do not see it, look for "TI Boards" blinking in device manager and quickly open the arrow. Then uninstall that OMAP4430 (right click, check box to uninstall device and driver, confirm), disconnect phone and reconnect with volume up. Then...
f.4.1) You will need to 'catch' OMAP4430 (with yellow question mark) by right-clicking on it when it appears under "Other Devices." Choose "Update Driver Software."
f.4.2) Pick "Browse my computer for driver software." Then "Let me pick..."
f.4.3) Leave "All..." selected under Devices. Then "Have Disk."
f.4.4) Navigate to the omap4boot-for_optimus-v1.21 folder and choose "omap_winusb" in the usb_drv_windows folder.
f.4.5) Windows will warn the driver is unsigned. Install anyway. An OMAP4430 device should appear under the list of devices. Confirm the selection. Let the driver install.
f.4.6) Disconnect the phone and again reconnect with volume up held.
f5) You should see a popup at the bottom of your screen about drivers (the LG USB drivers) installing. (If you do not see it, disconnect phone, reboot your pc, and again connect it without battery while holding volume up). When you do see drivers installing, let go of the volume button. Click the popup to see the progress. Let it finish.
f6) Look for “LGE CDMA USB SERIAL PORT” in Device Manager. Right click on it and go to Properties
f7) Select the "Port Settings" tab and click 'Advanced'.
f8) Change 'COM Port Number:' to COM41. Click OK, then OK again.
f9) Disconnect your phone from the PC." (From drastic00's noob tutorial)
Sent from my LG-P925g using xda premium

need help, installing ota zip to my nexus 6

Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step

hendyanto said:
Hello guys,
i was following this article, from yahoo, i cannot post it
and reached the point of
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
but it says this in the cmd
device <null> NOT attached.
the phone is still connected, what do i do now?
please help
Click to expand...
Click to collapse
I was having the exact same problem last night, following the same instructions. I still could not figure out how to sideload the OTA, so I ended up just flashing the update and starting from fresh. Wish I had the answer for you.
Here was my thread asking pretty much the same thing: http://forum.xda-developers.com/nexus-6/help/disconnects-computer-entering-bootloader-t3230705

danarama said:
Where does it say this and at what point? Your phone is 100% stock then, correct? You set up adb correctly?
We'll need more information than supplied. You should walk us through step by step
Click to expand...
Click to collapse
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
The following ADB commands are for Windows machines. If you’re using a Mac, just add “./” before each command, for example: “./adb reboot bootloader”.
Assuming you device is already connected to your computer via USB and USB Debugging is enabled, you need to re-start it in fastboot mode. Follow one of the two methods below. Option A may be preferable because it’s another confirmation that your computer recognizes your Nexus device.
A) Type “adb reboot bootloader”
B) Turn your device off, then turn it back on while holding down the relevant key combinations for your device. For many devices it’s Volume Up + Volume Down + Power. You can see what your device’s key combinations are here.
The fastboot menu will appear and you should see Start in the top right. Press Volume Up till it changes to Recovery. Press the Power button to select it.
You will see an Android with a red exclamation point icon, press and hold the Power key, then press the Volume up key to show the Recovery Menu.
You will get a new menu. Navigate to apply update from adb and select it by pressing the Power button.
In the command window — make sure you are in the directory where ADB and Fastboot reside — type: “adb sideload [the full name of the file].zip” without the brackets around the file name.
The update will install and reach 100 percent.
Reboot and enjoy the latest version of Android Marshmallow.
Click to expand...
Click to collapse
(red arrow) and then the cmd says the null error, i am trying this now
I had the same problem. Turned MTP on and then it worked. You're told to turn it off but don't... Its in Settings-Storage-touch the ... Menu top right corner, USB settings and turn ON MTP mode. It worked well for me. I also used the Nexus Root Toolkit - makes things much easier!
Click to expand...
Click to collapse
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)

hendyanto said:
100% Stock, yes! 1 week old.
Yes i have set up ADB
I have followed the instruction until this part (i cannot post any link sorry, not authorized by xda)
(red arrow) and then the cmd says the null error, i am trying this now
My phone is able to rebooot (the options comes out sometimes after i did not do anything) and now optimising app (like it usually did after an OTA update)
Click to expand...
Click to collapse
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.

danarama said:
There are lots of additional steps in that guide and not always the simplest way of doing it.
First thing to do is boot into recovery.
- Turn off the phone.
- Hold volume down + power
- At the bootloader screen, use volume keys to navigate to recovery and press power to select#
- At the Red warning triangle, hold power then press volume up.
At this stage, type "adb devices" in your command prompt and see if it returns your serial number or not. If it does, you can follow the steps to use adb to flash the update.
Please note, the guide talks about USB debugging. This only works in android. Nothing you need to do needs to be done via android so this is nonsense. Also the MTP option only works in android, so setting this in settings as a fix is also nonsense.
Click to expand...
Click to collapse
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.

hendyanto said:
I cannot get my windows to detect the phone during recovery mode, it always disconnected at that point.
I'll try again when i have the time, thank you all.
Click to expand...
Click to collapse
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)

I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!

danarama said:
Could be a driver issue. You'll need to check device manager. Perhaps uninstall the existing drivers and let it auto detect.
Failing that, install the Naked driver from my adb and fastboot thread (Nexus 6 general > Sticky roll-up thread > Adb and fastboot. What is it?)
Click to expand...
Click to collapse
qwerty1gr said:
I had the same issue with you until i did the following: I used wugfresh's nexus utility. Then I downloaded the respective file from XDA and saved it in the same folder as the Wugfresh's tool. Restarted in Recovery mode and chose 'update from adb'. Connected the phone with the usb having USB debugging on from before going to recovery. Started the CMD window from Wugfresh's tool (Advanced Utilities -> Launch) and check that the phone is connected (I think "adb devices") . Then "adb sideload xxxx.zip" and waited for the process to finish.
Instruction here: androidpolice 2012/11/13/android-4-2-build-jop40c-rolling-out-to-the-nexus-7-now-manual-download-link-available/
You do not have to install the full Android utility. Just use wugfresh;s cmd screen. Good luck!
Click to expand...
Click to collapse
Thank you guys! But after this "happy"night, i woke up to the OTA for marshmallow arrived on my phone, so see you guys on the rooting section instead, Thank you thank you for the help

Fixed my LG G watch on Bootloader being recognized as an Android Bootloader Interface

Alright, so many or some have known that i had an sticky situation with my LG G watch whereby I couldn't get it to update it to a new Software Update.
But a plonker manifested inside it, it was that I couldn't even make my device recognizeable in the Bootloader menu or Fastboot menu. I will show you how to eradicate that son of a gun!
1. Plug in your LGGWATCHR into your computer in fastboot state
2. Go to control panel, then to hardware and sounds
3. Click Device Manager
4. Locate the name Android Device or similar
5. Here is the most distressing part.
5,1. Right click on the children of Android device and press properties
5,2. Go to Drivers and press Update Driver
5,3. Press Browse my computer for driver
5,4. You will be prompted a directory, instead press the button below it called 'Let me pick from a list of Drivers installed on my computer'
6. Now I was so stupid i couldn't even see this little checkbox right above the drivers for 3 weeks!. Alright for me and/or for you, you might only see a 'model' called
'Android Bootloader Interface'. Now, there should be a CHECKBOX above there STATING 'Show Compatible Drivers'.
7. Uncheck that and voila, you got ABD Sooner device. Press that and finish.
Please post your comment if you have any trouble!

dıd not work for me

Windows 10 Razer phone 2 driver problem.

Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5

raver445 said:
Hello everybody I was able to unlock the bootloader but when I put the phone in bootloader mode it doesn't even see the phone on the computer I've tried going to platform tools and command prompt and did ADB devices and it won't see it. it won't even see it in fastboot. I've tried the driver installation guide but it doesn't work. Can someone please help me? I am running Windows 10 64-bit on a Acer nitro 5
Click to expand...
Click to collapse
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?

Yes usb debug mode is on...

Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
I have even tried updating the drivers and it keeps saying it can't update it even if I use the manual update settings

Johnjobs13 said:
I had this issue myself when I tried unlocking. It seems when you type fastboot, CMD keeps using an older version. You will need to directly call /fastboot.exe, wherever the full path is, and have your Razer in bootloader mode (it took me an hour to figure out I already had it in bootloader mode), and hopefully it will find it.
TLDR: Make sure adb and fastboot are being executed from their actual paths and that they are the latest.
Also USB debugging is on? Did you check the notifications?
Click to expand...
Click to collapse
How can I get the drivers installed then? It's driving me crazy.

raver445 said:
How can I get the drivers installed then? It's driving me crazy.
Click to expand...
Click to collapse
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.

Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.

th3cavalry said:
Heres what I did:
1) Download https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
2) Extract to a folder in your desktop.
3) Go into the folder and look for android_winusb.inf
4) Right click it and choose install.
5) Press the windows button and X at the same time and choose device manager.
6) Plug the phone in and find the device in the device manager. It could be in a couple different device trees, so you'll have to find it.
7) Right click and choose update driver. Choose browse, then browse again, and find the folder on your desktop with the drivers. choose that same .inf file from earlier.
8) You'll have 3 different options. I've always had success with the ADB Composite driver.
Click to expand...
Click to collapse
I have just rebooted my computer I'll see how it works in just a moment but I don't know if it's going to see it or not. it is still not seeing it.

Gamesoul Master said:
I vaguely recall having the same issue, and fixed it by going into the Device Manager and installing a different driver for the phone. I can't remember exactly which one it was (I want to say it said something about fastboot). This was after booting into fastboot of course, since Windows uses a different driver for when it's in fastboot vs when it's booted normally.
Click to expand...
Click to collapse
So what can I do to fix this? It's driving me insane.

raver445 said:
So what can I do to fix this? It's driving me insane.
Click to expand...
Click to collapse
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?

celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
After I update it the software drivers for the computer it says Razer phone 2 but it doesn't work right. I tried doing one of those scripts to reflash to stock software and it doesn't do Jack squat it sits there waiting for device.

use samsungs usb driver installer and change adb driver to Samsung's version in device manager. should see fastboot device now .

celphtitled885 said:
im having the exact same issue doing what everyone says and nothing i need to lock my bootloader to send back to razer for warranty im pulling my hair out
---------- Post added at 11:18 PM ---------- Previous post was at 11:14 PM ----------
unless this is correct the phone comes up as samsung android phone and under the tab is android adb interface?
Click to expand...
Click to collapse
i got it to work for the fastboot devices ...but still unable to relock it

has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period

ghost9640 said:
has anyone figured this out yet im havin the exact same problem i go into bootloader and it shows android with caution sysmlo in device manager will no find device in fastboot mode period
Click to expand...
Click to collapse
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well ?
https://forum.xda-developers.com/and...ndows-t3999445

got it
JDBarlow said:
Copied from another thread.....
This is the biggest problem most people have if you don't do this part here below.
https://s3.amazonaws.com/cheryl-fact...on_Windows.pdf
You can use this tool as well to setup adb and fastboot with the correct cord it works well
https://forum.xda-developers.com/and...ndows-t3999445
Click to expand...
Click to collapse
my laptop was not seeing the device my pc is, now im trying to flash arter97 kinda stuck but thx bud

The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved

decode2533 said:
The CPU AMD and windows 10 has an issues with fasboot driver everytime that you put command in fastboot the screen changes and starts displaying following message "Press any key to shutdown" waiting for devices or stuck on fastboot "sending system ...123,456kb. No need to find any cable to fix this just install windows 7 and flashing step by step then the problem will be solved
Click to expand...
Click to collapse
Lol okay..that's about as random as "hey anybody reading this thinking about getting an S20 Ultra or one of the others"
I am....

I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.

Hi All,
Thought I would post this on here for you all, might help someone else like it did me.
What ImperialMe said is correct and I was able to do both my Razor 1 and 2 using it.
imperialme said:
I had the same problem. I never could get it to work in Windows. Luckily, however, I have an Ubuntu dual boot on my system, so I installed ADB & Fastboot on linux, put the phone in download mode, plugged it in, and it showed up without issue. This won't help for everybody, but if you have a linux machine, or a you can install a dual boot, it'll get you where you need to be. And it's a lot easier than Windows. You might be able to do a USB pass through, to a VM, but I haven't tested it. It could be worth a shot, if you don't have any other options.
Click to expand...
Click to collapse
The easy method is to download the Ubuntu Image for Windows (ubuntu.com/download/desktop)
Once you have it, burn it to USB using Rufus (rufus.ie)
Boot into the USB on your PC and when prompted just run as is, no need to install.
Once running, open a terminal window and with internet access and run the following:
Code:
sudo add-apt-repository universe && sudo apt-get update
Now run:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
When promoted press Y and enter
Now run:
Code:
sudo adb start-server
Connect your phone, turned on and on the home screen for example. Run the following
Code:
sudo adb devices
You should see your device listed as unauthorised and get a prompt for ADB access on the mobile phone.
run it again to confirm its authorised and then enter:
Code:
adb reboot bootloader
Once rebooted, use the menu to select boot into fastboot on the phone
Now back to the terminal window, enter:
Code:
Fastboot devices
You should now see your device listed and commands should work as expected.
If you need to copy anything over to the temporary USB OS then use another USB drive and copy them to it before you boot the OS.
I tried this in a VM and VMWare and HyperV both failed as the drivers they use are still Windows based and failed. Only a full OS worked.
Hope this helps someone else!

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.