The problem is that once the device is in fastboot mode, it shows up as a different device: "Google, Inc Android 1.0." So doing "lsusb" in the VM showed no device connected, and obviously "fastboot devices" returned nothing until I added the "second" device as a filter for the VM as well. The device I had added was "samsung Nexus 10". I had added the usb device as a filter for the VM (using virtual box in the virtual machine's settings). I had the same issue, but I was running Ubuntu 12.04 through a VM. E:\dev\android-sdk-windows\platform-tools>fastboot devices from the windows cmd line E:\dev\android-sdk-windows\platform-tools>adb devicesĮ:\dev\android-sdk-windows\platform-tools>fastboot devicesĮ:\dev\android-sdk-windows\platform-tools>adb reboot bootloader Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"Ĭlick "yes" when it says that driver might not be compatible Let me pick from a list of devices, select List All Devices Then look for on screen instructions to enter fastboot mode.Answer2:įind Unknown "Android" device (likely listed under Other devices with an exclamation mark) Some people recommend that on the internet.Īre you rebooting the device into the bootloader and entering fastboot USB on the bootloader menu? But someone knows why fastboot does not see my device, but adb does?
I returns and stays like that until I exit. fastboot flashall -w is also not working. But when I enter fastboot devices nothing returns.Īdb devices is working. At the moment I would like to reinstall Android on my device(custom hardware device).
0 kommentar(er)
