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 | less and find the relevant section which will look something like this:
Bus 001 Device 027: ID 18d1:4e30 Google Inc.
Couldn't open device, some information will be missing
Device Descriptor:
...
idVendor 0x18d1 Google Inc.
Now do
sudo vi /etc/udev/rules.d/11-android.rules
it's ok if that file does not yet exist; create it with a line like this, inserting your own username and vendor id:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0640", OWNER="mbp"
then
sudo service udev restart
then verify the device node permissions have changed:
ls -Rl /dev/bus/usb
The even shorter cheesy version is to just run fastboot as
root.
参考:
http://stackoverflow.com/questions/7641939/android-fastboot-waiting-for-devices
本文介绍了解决在Fastboot模式下遇到的Waiting for Device问题的方法。主要原因是USB设备节点对于当前用户不可访问。解决方案包括使用lsusb命令查找设备、编辑udev规则文件并重启udevd服务,确保设备节点权限正确。
3405

被折叠的 条评论
为什么被折叠?



