Fastboot commands won't run properly about cve-2022-38694_unlock_bootloader HOT 7 CLOSED

Just noticed that I needed to run Zadig again and reinstall the libusbK driver, since it seemingly got cleared during the factory reset. Didn't change anything, but may have been related to the issue.

from cve-2022-38694_unlock_bootloader.

fastboot and adb need to use google USB driver.
So you need to check the driver by DriverStoreExplorer.

google USB driver:
https://developer.android.com/studio/run/win-usb

from cve-2022-38694_unlock_bootloader.

Okay, I think I installed it on the Unisoc Phone entry, (found it in the list, clicked Add Driver, and selected the android_winusb.inf file,) but now it can't even detect the device with adb devices. What did I miss?

from cve-2022-38694_unlock_bootloader.

When viewing it in Zadig again, while on charging mode only, it shows Hisense Phone and a WINUSB driver. When it's put into MTP mode, though, it splits into two drivers, one under ADB Interface (WINUSB) and one under MTP (WUDFWpdMtp).

from cve-2022-38694_unlock_bootloader.

The A7CC Zadig info list is below:
ADB interface: Driver USBSTOR(v10.0.22000.918)
one under MTP: WUDFWpdMtp(v10.0.22000.918)

from cve-2022-38694_unlock_bootloader.

search and install SPD Driver R4.20

from cve-2022-38694_unlock_bootloader.

It didn't do anything, as far as I can tell. Same < waiting for any device > result, and same two ADB and MTP input options.

from cve-2022-38694_unlock_bootloader.