blocks|key|564890|text|下面是一个bash函数，用于检测和注册系统中的所有adb设备：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|564891|UpdateAdbUsbIni+()+{
++++INIFILE=${1:-$HOME}/.android/adb_usb.ini
++++mkdir+-p+$(dirname+$INIFILE)
++++DEVICES=$(find+-L+/sys/bus/usb/devices+-maxdepth+2+-path+"*/modalias"+-printf+"%25h\t"+-exec+cat+{}+\;+%7C+awk+-F:+'/icFFisc42ip0/+{print+$1}')
++++echo+-e+"\nRegistering+Vendor+IDs+for+the+following+ADB+devices:"
++++for+D+in+$DEVICES
++++do
++++++++echo+-e+"\tDEVPATH=$D+Serial=$(cat+$D/serial)+VendorID=0x$(cat+$D/idVendor)+($(cat+$D/manufacturer))"
++++++++echo+"0x$(cat+$D/idVendor)"+>>+$INIFILE
++++done
++++VIDS=$(grep+%5E0x....$+$INIFILE+%7C+sort+-u)
++++echo+"$VIDS"+>+$INIFILE
++++return+0
}|code-block|syntax|javascript|564892|此函数不依赖于现有的adb配置。因此，如果它没有列出任何设备--这意味着没有已连接的设备具有枚举的adb接口。|564893|以下是另一个有用的功能：|564894|InstallUniversalAndroidUdevRule+()+{
++++RULE='ACTION=="add",+SUBSYSTEM=="usb",+ENV{DEVTYPE}=="usb_device",+ENV{ID_USB_INTERFACES}=="*:ff420?:*",+MODE="0666",+GROUP="plugdev",+SYMLINK%2B="android/$env{ID_SERIAL_SHORT}"'
++++RULEFILE="/etc/udev/rules.d/${1:-90}-universal-android.rules"
++++if+[+"0$(id+-u)"+!=+"00"+];+then+echo+"No+permission+to+add+the+universal+Android+udev+rule!";+return+1;+fi
++++echo+"$RULE"+>+$RULEFILE
++++udevadm+control+--reload-rules
++++udevadm+trigger+--action=add+--subsystem-match=usb
++++return+0
}|564895|这个函数添加了通用的android+udev规则，它将匹配所有的android设备，而不管制造商是谁。不过，它确实需要root特权才能运行。|564896|这个问题促使我终于完成了我的关于如何在基于debian的linux环境中正确安装adb的最全面的说明。|564897|entityMap|0|LINK|mutability|MUTABLE|url|http://ktnr74.blogspot.com/2014/09/the-most-comprehensive-write-up-on-how.html^0|5|4|P|3|0|0|A|3|1D|3|0|0|0|I|4|W|7|1N|4|0|E|11|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|1F|8|@$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1M|8|@]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|U|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

Here is a <code>bash</code> function I use to detect and register all <code>adb</code> devices in the system:

<pre><code>UpdateAdbUsbIni () {
 INIFILE=${1:-$HOME}/.android/adb_usb.ini
 mkdir -p $(dirname $INIFILE)
 DEVICES=$(find -L /sys/bus/usb/devices -maxdepth 2 -path "*/modalias" -printf "%h\t" -exec cat {} \; | awk -F: '/icFFisc42ip0/ {print $1}')
 echo -e "\nRegistering Vendor IDs for the following ADB devices:"
 for D in $DEVICES
 do
 echo -e "\tDEVPATH=$D Serial=$(cat $D/serial) VendorID=0x$(cat $D/idVendor) ($(cat $D/manufacturer))"
 echo "0x$(cat $D/idVendor)" &gt;&gt; $INIFILE
 done
 VIDS=$(grep ^0x....$ $INIFILE | sort -u)
 echo "$VIDS" &gt; $INIFILE
 return 0
}
</code></pre>

This function does not depend on the existing <code>adb</code> configuration. So if it does not list any devices - it means no connected devices have <code>adb</code> interfaces enumerated.

Here is another useful function:

<pre><code>InstallUniversalAndroidUdevRule () {
 RULE='ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:ff420?:*", MODE="0666", GROUP="plugdev", SYMLINK+="android/$env{ID_SERIAL_SHORT}"'
 RULEFILE="/etc/udev/rules.d/${1:-90}-universal-android.rules"
 if [ "0$(id -u)" != "00" ]; then echo "No permission to add the universal Android udev rule!"; return 1; fi
 echo "$RULE" &gt; $RULEFILE
 udevadm control --reload-rules
 udevadm trigger --action=add --subsystem-match=usb
 return 0
}
</code></pre>

This function adds the universal android <code>udev</code> rule which would match all <code>android</code> devices regardless of the manufacturer. It does require <code>root</code> privileges to run though.

This question has prompted me to finally finish my <a href="http://ktnr74.blogspot.com/2014/09/the-most-comprehensive-write-up-on-how.html" rel="nofollow">The most comprehensive write up on how to properly install adb in a debian-based linux environment </a>

blocks|key|740524|text|在我的系统(Ubuntu12.04)上，您必须以root用户的身份运行亚行杀死服务器/亚行启动服务器。试着使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|740525|sudo亚行杀毒服务器|740526|sudo亚行启动服务器|740527|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

On my system (Ubuntu 12.04) you have to run adb kill-server/adb start-server as root. Try using: sudo adb kill-server 
sudo adb start-server

blocks|key|564959|text|哇，我真是个白痴。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|564960|我尝试了UpdateAdbUsbIni脚本，没有得到响应，然后去检查设备是否有问题。结果，在“设置”->+"{}+Developer选项“下，"USB调试”未选中。当我选中此选项并重新连接设备时，我确信：|564961|adb+devices
+++List+of+devices+attached+
+++4d773808680064314c9++device|code-block|syntax|javascript|564962|谢谢你的亚历克斯·P！|564963|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Wow, I'm such an idiot. 

I tried the UpdateAdbUsbIni script, got no response, and went to check if anything was wrong with the device. Turns out that under "Settings" -> "{} Developer options", "USB debugging" was unchecked. When I checked this option and reconnected the device sure enough I got:

<pre><code>adb devices
 List of devices attached 
 4d773808680064314c9 device
</code></pre>

Thanks for that Alex P!

I'm trying to be able to use adb with my tablet. The tablet and its file tree gets recognized in the Files directory navigator and I can navigate to <code>/media/me/SP1020</code>. 

What I don't understand is why adb can't recognize the device. I ran these instructions from terminal:

<pre><code>adb kill-server
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb devices
 List of devices attached 
</code></pre>

And nothing is displayed.

lsusb lists the device ID as:

<pre><code>Bus 001 Device 004: ID 1f3a:1000
</code></pre>

so I entered this ID, "0x1f3a" at the top of adb_usb.ini using vim in ~/.android; after this not working, I deleted this file adb_usb.ini and I also tried typing

<pre><code>echo "0x1f3a" &gt; ~/.android/adb_usb.in
</code></pre>

This time retaining the file. I have also created a file 51-android.rules in /etc/udev/rules.d with the following content:

<pre><code>SUBSYSTEM=="usb",SYSFS{idVendor}=="1f3a",MODE="0666"
</code></pre>

I then rebooted my system and my tablet, and tried

<pre><code>adb kill-server
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb devices
 List of devices attached 
</code></pre>

And still nothing is displayed.

Here's also the contents of the usb/004 

<pre><code>ls -l /dev/bus/usb/004
total 0
crw-rw-r-- 1 root root 189, 384 Sep 23 09:53 001
</code></pre>

Tablet mounted but adb devices not recognizing tablet in ubuntu 14.04

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正试着在我的平板电脑上使用亚行。tablet及其文件树在Files目录导航器中被识别，我可以导航到/media/me/SP1020。我不明白的是为什么亚行不能识别这个设备。我从终端机运行了这些指令：adb kill-serveradb start-server* daemon not running. startin...

问平板电脑安装但亚行设备不识别平板电脑的ubuntu 14.04
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问平板电脑安装但亚行设备不识别平板电脑的ubuntu 14.04EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问平板电脑安装但亚行设备不识别平板电脑的ubuntu 14.04
EN