[OnePlus 7 Pro Questions & Answers] one_minus:
I got my Oneplus 7 Pro today after upgrading from the Oneplus one; quite a leap.

I've been trying to get the bootloader unlocked and the phone rooted, but something appears to be wrong with either my phone, my PC, or my PC's OS... yeah, really narrows it down. I'll describe the symptoms.

First of all, I can't detect the phone when I put it into fastboot with the 'fastboot' utility, but that's beside the point. The more concerning point is that I can't even see a usb device detected in device manager (or powershell's "get-pnpdevices") when I get the phone into fastboot mode.

USB debugging connectivity and file transfer connectivity do not have this problem. It's only fastboot mode, as if there's some setting stopping the phone from even allowing usb connections when in fastboot mode, in the first place.

Some example output from powershell that checks for newly connected USB devices in the last 5 minutes when I connect the phone with only ADB enabled (no file transfer):

===

PS C:\WINDOWS\system32> get-pnpdevice |where hardwareid -like "usb*" | get-pnpdeviceproperty | where { $_.keyname -like "*arrival*" -and $_.data -gt (get-date).addminutes(-5) } | select instanceid,data

InstanceId data

---------- ----

USB\VID_2A70&PID_4EE7\[sn_redacted] 12/8/2019 2:43:07 AM

===

Some example output of the same, except with a 2 minute threshold, when I reboot into fastboot mode via ADB, then wait a few minutes:

===

PS C:\WINDOWS\system32> get-date

Sunday, December 8, 2019 2:45:34 AM

PS C:\WINDOWS\system32> get-pnpdevice |where hardwareid -like "usb*" | get-pnpdeviceproperty | where { $_.keyname -like "*arrival*" -and $_.data -gt (get-date).addminutes(-2) } | select instanceid,data

PS C:\WINDOWS\system32> get-date

Sunday, December 8, 2019 2:45:49 AM

PS C:\WINDOWS\system32> get-pnpdevice |where hardwareid -like "usb*" | get-pnpdeviceproperty | where { $_.keyname -like "*arrival*" -and $_.data -gt (get-date).addminutes(-2) } | select instanceid,data

====

As you can see, no newly connected devices. It's hard to illustrate exactly what's going on, with concrete proof beyond that. Now, on to why I'd bother with those commands.

Most people, when they hear "I can't see my device in fastboot mode", will think "Well, you must not have installed the drivers for the device". I will list off some of the thing I've tried:

-I've already tried installing drivers (it's own PITA on windows 10...), and eventually got oneplus' provided drivers installed for the Android ADB interface and Android Composite ADB interface (the latter being active when file transfer mode is enabled as well as debugging).

-I've obviously enabled USB debugging, or ADB wouldn't work, either.

-I've enabled OEM bootloader unlocking in the developer menu as well.

The problem is that there is no fastboot device detected to install drivers TO. What driver is installed is moot, because there is no way to install it. My PC doesn't even see it in the first place. Once I go into fastboot mode, it's as if I simply unplugged the device, even on the hardware level. It's as if my phone simply disabled its USB port.

What SHOULD happen, from my understanding is that there should be some device detected by Windows named "Android Bootloader Interface" or similar. Then windows attempts to install its 13 year old drivers to said interface, and you get to fight that for a good while.

If that were the extent of what I'm running into, it'd be a relief. There is simply no device being detected one the hardware level.

Has anyone run into this? I haven't really done much of anything with the phone; more or less just ran the setup wizard to confirm it was working fine with my sim card, then got to modding.

I even did a factory reset from stock recovery just now, but no dice. Not having fastboot mode accessible is a problem on a few levels.

Will fetch logs 4 tips