Android fastboot 等待设备
我正在尝试在我的 NVIDIA 测试 git 上加载自定义内核。 我输入 fastboot boot myImage 之后得到：
<Waiting for device>
我认为这是我设备上 fastboot 模式下的驱动程序的问题。 但我不知道如何在linux上安装驱动程序。
大家知道怎么安装驱动吗？
I am trying to load a customized kernel on my NVIDIA test git.
I typed fastboot boot myImage after which which I get:
<Waiting for device>
I think this is a problem with a driver on fastboot mode on my device.
But I don't know how to install the driver on linux.
Do you guys know how to install the driver?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
D Shu 链接的页面的简短版本（没有可怕的弹出广告）是，当当前用户无法访问 USB 设备节点时，就会发生这种“等待设备”问题。在fastboot模式下，USB id是不同的，因此你可以轻松地在adb中获得它的权限，但在fastboot下却没有。
要修复它（在 Ubuntu 上；其他系统可能略有不同）：
运行 lsusb -v | less 并找到相关部分，如下所示：
现在，
如果该文件尚不存在，就可以了；使用这样的行创建它，插入您自己的用户名和供应商 ID：
然后
验证设备节点权限是否已更改：
更短的俗气版本是仅以 root 身份运行
fastboot。但随后您需要以 root 身份运行与设备对话的每个命令，这往往会导致其他复杂情况。从长远来看，修复权限更简单。The short version of the page linked by D Shu (and without the horrible popover ads) is that this "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in fastboot mode, so you can easily have permission to it in adb but not in fastboot.
To fix it (on Ubuntu; other systems may be slightly different):
Run
lsusb -v | lessand find the relevant section which will look something like this:Now do
it's ok if that file does not yet exist; create it with a line like this, inserting your own username and vendor id:
then
then verify the device node permissions have changed:
The even shorter cheesy version is to just run
fastbootas root. But then you need to run every command that talks to the device as root, which tends to cause other complications. Simpler just to fix the permissions in the long run.只需使用
sudo，快速启动需要Root权限Just use
sudo, fast boot needs Root Permission要使用 fastboot 命令，您首先需要将设备置于 fastboot 模式：
一旦设备处于 fastboot 模式，您就可以使用您自己的内核启动它，例如：
上面只会启动您的内核一次，当您重新启动设备时，旧内核将再次使用。要替换设备上的内核，您需要将其刷新到设备：
希望有帮助。
To use the fastboot command you first need to put your device in fastboot mode:
Once the device is in fastboot mode, you can boot it with your own kernel, for example:
The above will only boot your kernel once and the old kernel will be used again when you reboot the device. To replace the kernel on the device, you will need to flash it to the device:
Hope that helps.
发生这种情况时，尝试使用编译器生成的
fastboot。文件路径为
out/host/linux(或其他)/bin/fastboot并且还需要
sudo。它在大多数时间都有效。
try to use compiler generated
fastbootwhen this happes.the file path is
out/host/linux(or other)/bin/fastbootand
sudois also needed.it works in most of the time.
就我而言（在 Windows 10 上），它可以很好地连接到 adb，并且我可以输入任何
adb命令。但是，一旦使用adb restart bootloader到达引导加载程序，我就无法执行任何fastboot命令。我注意到，在设备管理器中，当我连接到设备时它会刷新。接下来要做的就是检查连接时发生了什么变化。显然，fastboot 设备位于
Kedacom USB 设备内。不太确定那是什么，但我更新了设备以使用不同的驱动程序，在我的例子中是Fastboot 接口（Google USB ID），并且修复了我的等待设备问题In my case (on windows 10), it would connect fine to adb and I could type any
adbcommands. But as soon as it got to the bootloader usingadb reboot bootloaderI wasn't able to perform anyfastbootcommands.What I did notice that in the device manager that it refreshed when I connected to device. Next thing to do was to check what changed when connecting. Apparently the fastboot device was inside the
Kedacom USB Device. Not really sure what that was, but I updated the device to use a different driver, in my case theFastboot interface (Google USB ID), and that fixed mywaiting for deviceissue最短的答案是首先运行 fastboot 命令（在我的 ubuntu 情况下，即 ./fastboot-linux oem unlock）（这里我使用 ubuntu 12.04 和 rooting nexus4）
然后以快速启动模式打开设备电源（在 Nexus 4 中按音量下键和电源按钮）
The shortest answer is first run the fastboot command (in my ubuntu case i.e. ./fastboot-linux oem unlock) (here i'm using ubuntu 12.04 and rooting nexus4)
then power on your device in fastboot mode (in nexus 4 by pressing vol-down-key and power button)
在您的设备上转到“设置”->“开发设置，然后选择“允许 OEM 解锁”
如解锁所示你的引导加载程序
至少这对我的 MotoE 4G 有用。
On your device Go To Settings -> Dev Settings, And Select "Allow OEM Unlock"
As shown on Unlock Your Bootloader
At least this worked for me on my MotoE 4G.
您可能一切正常，但设备只允许您执行一个
fastboot命令。如果您可以成功执行fastboot devices，但随后尝试fastboot OEM解锁，并且遇到可怕的waiting for devices，请尝试执行fastboot oem解锁后直接重新启动到fastboot，无需执行任何其他命令。You may have everything OK but the device only allows you to execute one
fastbootcommand. If you can successfully do afastboot devicesbut you then try afastboot oem unlockand you get the dreadedwaiting for devices, try executingfastboot oem unlockdirectly after doing the reboot to fastboot without executing any other commands.