Using the Appium process, and colleagues exchanged the next phone, suddenly connected to ADB only hint list of devices attached, no content of BAA ~
Later see the C-Big post, https://blog.cofface.com/archives/569.html
Replace the file under Platform-tools, OH yeah~ success
The following content from the C Big blog, reprinted annotated source, thanks to the Big C!
Brief introduction:
ADB believes that many Android developers will use it to debug the phone, the Assistant software is also dependent on it to achieve machine identification, software installation, software delivery and other functions.
The original ADB was unable to boot due to the use of the major phone helper class software under Windows. Specific adb introduction can be Google or Baidu.
Update Description:
1, V7.1 edition (2017-03-31)
1) based on 7.1 source code to modify and compile Windows edition;
2) Support all Adb/fastboot official functions;
3) Adb/fastboot modify support to identify all models, do not limit the brand model;
4) solve the conflict problems caused by opening other assistant software such as 360 Assistant/Mobile Butler/pea pod;
5) ADB push support transmission progress display;
6), support the transmission of more than 2G files;
7), compiled the Windows, Linux, ARM (ARM Development Board/ARM Platform mobile phone) version;
Demo Figure V7.1:
1, V7.1:
1), Windows version: Link: http://pan.baidu.com/s/1qXKjqw8 Password: e33w
2), Linux version: Link: http://pan.baidu.com/s/1sk9XNXz Password: y593
3), ARM Platform version: Link: http://pan.baidu.com/s/1slyIHWT Password: UGPP
Phone connection adb only shows list of devices attached