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 | 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.

更多相关文章

  1. 代码中设置drawableleft
  2. android 3.0 隐藏 系统标题栏
  3. Android开发中activity切换动画的实现
  4. Android(安卓)学习 笔记_05. 文件下载
  5. Android中直播视频技术探究之—摄像头Camera视频源数据采集解析
  6. 技术博客汇总
  7. android 2.3 wifi (一)
  8. AndRoid Notification的清空和修改
  9. Android中的Chronometer

随机推荐

  1. [置顶] android 多媒体和相机详解十
  2. Android(安卓)Studio安装配置及使用
  3. Android(安卓)ImageView设置边框
  4. Android(安卓)Activity 常用功能设置(全屏
  5. Android(安卓)Studio报错:the minSdk vers
  6. android 通过网址或者域名得到IP地址
  7. Android(安卓)判断某个APK是否已安装
  8. android小功能实现之SQLite数据库的基本
  9. [Android实例] android多点触摸demo
  10. Android(安卓)红圈营销项目 —— 自定义