Originally Posted by Rachara
I'm stuck and wondering if I could get some help. I'm trying to use this so I can flash the factory image on my Pixel XL. It has previously been unlocked with a custom rom and root, and I'm trying to install a new rom but I need to flash an updated factory image first.
So the issue is, I'm able to get the device to recognize while it is powered on (even this seems to take some effort tho, doing the kill-server, start-server). I can get it to reboot into bootloader via command prompt, however once I'm there the device is no longer recognized. Flashing the factory image fails on all counts, and I am assuming this is because the device doesn't appear to be connected.
I have checked it in device manager, it appears there. I have also downloaded the latest SDK tools and updated usb drivers. I've tried searching for answers, but I'm not having any luck. Any help would be greatly appreciated.
Edit: I do get this error a lot, if it helps:
PS C:\AndroidTools> adb devices
List of devices attached
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully
First, the official guide on google factory images are quite useful. If you have not gone through it yet, try it first.
Then, I hope you do realize that once it reboots to bootloader, it is out of the reach of adb. You should be using fastboot now. For example, I would use "sudo fastboot devices" to check the connection (by the way, I am using Ubuntu, not windows, so you need to figure out whether you need that sudo in the beginning).
Finally, I suspect that you adb is not really the updated version based on your error message. But that doesn't really matter, because you don't really need adb to get into fastboot mode. You do need the latest fastboot though. You may have the latest SDK, however, it may very well be an issue with how to let the windows know where your latest SDK is, so that it knows to use the updated adb and/or fastboot for the task of flushing the image.