I’m running Web Installer on brand new Pixel 7 via Windows 10. All went smoothly until Step 18/21.
When I click “Connect” in the Bootloader Connection window, no compatible device is found.
Web Installer error message says:…
“Error on step: connect-bootloader Cannot execute command connect bootloader The device is not connected Failed to connect: Cannot connect Bootloader Proposal: Check connection and that no other program is using the phone and retry.”
Thank you for the reply. My Windows machine does not have those tools/drivers.
I used Easy Installer years ago to setup my previous /e/OS Samsung phone (it just bricked during an update), so may be that why the prerequisite Windows drivers are missing.
I installed the ADB package and updated cmd prompt path
Put Pixel7 in Fastboot mode
Ran CMD “fastboot devices” but it returned nothing
Device Manager shows Pixel7 as a problem device
Ran Windows update for drivers (one update was a USB driver) and restarted
Device Manager still shows Pixel7 as a problem device
So it looks like a need to manually update driver? I found “Google USB Driver” on android Developers website, and, “Google Android Bootloader Interface Driver 10.0.0.0 for Windows 10” on Softpedia. Are either of these correct?
Usually Windows own search is sufficient. Did you already try as the animation marked with a [1] … many say that is the best way. Being a Google Pixel it should be well advertised.
Then the status window refreshed saying “Downloading pixel-7-rom.zip” This status message ran for quite some time, then the Installer page went completely blank.
The phone still appears to be running /e/OS fine but still starts up in bootloader mode.
That seems a strange mixture … I cannot really visualise what you mean by
Did you keep the Device manager open to see if the phone became a Problem device, at any time during the install?
In principle there should be no problem to run the installer again … personally if the situation was odd I would abandon the installer and perform a manual install.
When the original install stopped at Step 18/21 (because it no longer recognized the phone) the Installer had apparently loaded /e/OS, and, restarted the Pixel7 which was by then was running /e/OS in bootloader mode. Once past the bootloader mode warning, this one is still is running fine like my previous /e/OS phone…
I did have Device Manager open while Installer was running and there was no Problem Device indicator. With the phone plugged in, an Android Composite ABD device shows up in DeviceManager. When I unlock the Pixel7 screen, a Pixel7 Portable device also shows up in Device Manager.
I think I will try running Installer again. I have never done a manual install. Are there instructions?
I guess that a brief read through it should help to see where you are in the install process.
Notice how part of your error message displays here as a link … which points to a download of recovery-IMG-e-3.0.4-t-20250709507786-official-panther.zip
Next you report “Downloading pixel-7-rom.zip” which will be the main ROM.
Notice the eos installer is installing Android 13 (T) official and not a community build.
In another panther thread I show an image of e-Recovery
So with a quick scan through the manual install doc and considering that /e/OS is installed, running, and the bootloader is still unlocked, I should be able to pick up the manual install process at “Locking the Bootloader”, which I could start from the Recovery Main Screen.
Looking back, the problem was… I should have checked to see if I had the Google Android Bootloader Interface Drivers or Google USB Drivers before running Installer. Installer recognized the out-of-box Pixel phone without those drivers when starting up, but did not see it mid-way after loading /e/OS onto the phone.
Although Installer would not continue after installing the proper drivers, /e/OS was running on the Pixel with the bootloader unlocked, allowing me to complete the install by following the Manual Install instructions.
)
Problem device, at any time during the install?