ADB enhanced Putty (replacement for "adb shell" co

We all know that running "adb shell" from the command line is pretty crap, and when using a latter busybox version which has coloring support it‘s ultimately crap. One workaround was usually to start a telnet server on the phone, and use putty to connect to that telnet server. Actually there is a more easier way to do that which also works for non rooted phones.

Actually the Android Debug Bridge has a terminal connection feature (roughly speaking), which will be enabled after you connect to the adb server in "0006shell:" mode. You can actually use the putty to connect to this interface always, by setting the following things:
- Turn off line discipline in settings
- Use RAW mode to connect to localhost:5037
- Enter "0012transport-usb" (without quotes)
- Enter "0006shell:" (without quotes)

Now you‘ve got a full fledged connection to your device. The main drawback is that it‘s tedious to repeat the above all the time, so I‘ve made some modifications to the putty binary that adds a new type of connection, called "Adb"

To use the enhanced putty:
- Select Adb from the connection type list
- Enter "transport-usb" in the host (or any other connection string, check the adb socket interface documentation if you need something else than connecting via usb)
- Enter 5037 as port, if it‘s not already set there.
- Connect and enjoy (you might also save this connection, so next time you only have to double-click on the settings)

DL and source: http://github.com/sztupy/adbputty/downloads

Screenshot:

时间: 2024-12-19 16:04:05

ADB enhanced Putty (replacement for "adb shell" co的相关文章

adb命令查看apk信息, adb启动你的apk

1.用adb获得手机里面某个apk的应用信息.版本信息 adb shell dumpsys package com.sy.a268 2.列出所有 adb shell dumpsys 3.用adb启动apk adb shell am start -n com.sy.a268/com.sy.a268.MainActivity 4.随机产生事件给某个应用程序, 随机产生500个事件给程序.你会发现你的程序不断的被点击,旋转! adb  shell  monkey -p  com.sy.a268  -v

Ubuntu遇到Please ensure that adb is correctly located at '...adb.exe' and can be executed 问题解决方法

上次我们在SDK更新的到最新的Android L版本之后,我发现我的ADT和android指定的版本不对应,我的ADT是22版本的,android L需要23版本以上的,版本不对应的话就无法加载这个SDK进去,通过上网查一下说是修改Android SDK目录下tolols目录下libs目录中plugin.prop这个文件,该文件打开一看就很容易知道要修改的是plugin.version=23.0.0这个,把它改成22就可以了,我改之后加载还真的是可以了,但是一个麻烦的问题又混淆我了,在运行项目的

studio adb连接不上手机 ADB server didn't ACK

问题描述:在eclipse的Logcat出现错误 [2014-01-08 14:00:07 - adb] ADB server didn't ACK [2014-01-08 14:00:07 - adb] * failed to start daemon * [2014-01-08 14:07:24 - adb] ADB server didn't ACK [2014-01-08 14:07:24 - adb] * failed to start daemon * 解决方法:先找到adb服务是否

Android 如何开启与关闭adb 的认证机制(google adb secure) (adb RSA 指纹认证)

前言 欢迎大家我分享和推荐好用的代码段~~ 声明          欢迎转载,但请保留文章原始出处: CSDN:http://www.csdn.net 雨季o莫忧离:http://blog.csdn.net/luckkof 正文 [Description] 如何开启与关闭adb 的认证机制(google adb secure) [Keyword] adb secure , ro.adb.secure , adb RSA 指纹认证 [Solution] MTK 版本默认关闭adb 的地址认证机制,

ADB cannot bind 'tcp:5037' ADB server didn't ACK

当我们在系统中使用多个不同源的adb时,特别容易浮现标题所述的错误: adb server is out of date. killing... cannot bind 'tcp:5037' ADB server didn't ACK * failed to start daemon * error: 上述错误出现的原因是说,我们的adb 所绑定的端口,被其他服务占用了,或者说有多个服务占用了5037端口,导致彼此无法正常工作. 想印证上述猜测,可通过如下命令: [email protected

ADB端口被占用,adb server is out of date

adb server端口 打开CMD 先执行adb nodaemon server ,查看adb server的端口是多少 C:\Users\xxxx>adb nodaemon server   cannot bind 'tcp:5037' 再执行下netstat -ano | findstr "5037" C:\Users\xxxxxx>netstat -ano | findstr "5037"   tcp    127.0.0.1:5037     

putty 、xshell的使用 和 putty 、xshell、 shell 间免密登陆

相关软件的使用: ######################################################################### 以上是相关软件的使用! 以下是免密登陆的配制 两台服务器之间,免密登陆的配制: ############################################################################################# putty 免密码登陆的配制: #################

虚拟机使用PuTTY、SSH Secure Shell Client前的配置

1 仅主机模式 2 检查子网IP 为192.168.154.0 3 进入虚拟机,检查IP地址 ip addr show 添加IP地址 ip addr add dev eno16777736 192.168.154.18/24 ping ping 192.168.154.1

Putty以及adb网络调试

1.什么是SSH? SSH 为 Secure Shell 的缩写,由 IETF 的网络工作小组(Network Working Group)所制定:SSH 为建立在应用层和传输层基础上的安全协议. 传统的网络服务程序,如FTP.POP和Telnet其本质上都是不安全的:因为它们在网络上用明文传送数据.用户帐号和用户口令,很容易受到中间人(man-in-the-middle)攻击方式的攻击.就是存在另一个人或者一台机器冒充真正的服务器接收用户传给服务器的数据,然后再冒充用户把数据传给真正的服务器.