Lost TWRP and ADB/Fastboot can't see phone to sideload. What can I do?

[rajah sulayman]

Basically what happened was:

• After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
• Booted system to find endless crash dialogs
• Rebooted into recovery to find TWRP gone
• Did a Full Wipe under stock recovery, hoping it'd fix things
• I can now get back into system, but it's glitchy
• Neither adb devices nor fastboot devices see the phone

Troubleshooting I've tried:

• Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
• Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
• Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear

I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.

Does anyone know what's going on or any way to remedy the situation?

NOTE: I'm on a Mac

 

[sd_shadow]

(crossposting from here as this looks like a more active sub and I'm desperate).

Basically what happened was:

• After updating PureNexus on my Pixel XL, I flashed the vendor image to only one slot
• Booted system to find endless crash dialogs
• Rebooted into recovery to find TWRP gone
• Did a Full Wipe under stock recovery, hoping it'd fix things
• I can now get back into system, but it's glitchy
• Neither adb devices nor fastboot devices see the phone

Troubleshooting I've tried:

• Plugged usb-c thumb drive into phone. It works fine, so it can't be the port
• Plugged old Nexus 5X into computer. ADB and FB can see it just fine, so it can't be the cable or drivers
• Plugged Pixel XL into computer. Phone charges but pulldown notification doesn't appear

I don't know what else to do. Prior to this, I was always able to see my Pixel from ADB/FB. I don't know why it's not working now. I would've thought that a "fastboot devices" from bootloader would at least work, and yet it's not. I can get into stock recovery just fine, but there don't seem to be any helpful options there.

Does anyone know what's going on or any way to remedy the situation?

It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.

Sent from my PH-1 using Tapatalk

 

[rajah sulayman]

It can be the drivers, Windows isn't going to use the same drivers as the Nexus, unless you manually select them in device manager.

But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.

 

[sd_shadow]

But I never had a problem with the drivers before now. I've always been able to ADB my Pixel, which is how I rooted and installed TWRP originally.

do you know how to check which drivers are selected.?

Sent from my XT1254 using XDA Labs

 

[rajah sulayman]

do you know how to check which drivers are selected.?

Is it through the Android Studio SDK manager? I remember using that way back when to get everything set up, but I haven't really used it since then.

 

[rajah sulayman]

Actually I just remembered that Mac don't need drivers, right? Per Google:

"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. Instead see Using Hardware Devices."

 

[rajah sulayman]

Update: Pulled out my Windows laptop and installed everything (drivers, Android Studio, et al) to see if I'd have better luck there.

To test, I first plugged in my working Nexus 5X. Windows immediately recognized it. Pulled up a prompt and adb devices saw the phone no problem.

Unplugged the Nexus and plugged in my Pixel XL. Nothing. No "hardware plugged in" chime, nothing listed under Device Manager, nada. Likewise, the phone itself doesn't acknowledge that it's been plugged in because there's no Android System pulldown.

If it were a driver issue, Device Manager would still at least be able to see the phone (it just wouldn't know what it was). But I'm getting absolutely nothing.

I can only assume that the problem is indeed with the phone itself. I don't know what the problem is exactly, but I know it wasn't there before all of this. Either way, this means my only hope for a fix would have to be through the phone itself. But since Stock Recovery doesn't seem to offer me many options, I have no clue what to do next.

Is there some sort of "secret" key combo or command or something that'll do a low-level format of the phone or something? I'm grasping at straws here, I know, but I honestly don't know what else there is I can do.

-------

Update 2: If I plug it in while in Bootloader, Windows recognizes that a device was connected, but as an "Unknown USB Device (Device Descriptor Request Failed)"

None of the solutions I can think of (or Google) seems to work. Has anyone heard of this problem before? I'm vainly hoping there's a fix out there that I just haven't found yet.