Hi,
I am trying to connect sabresd mx6q board using ADB to the Ubuntu host machine.
So far i have figured out the way to enable debugging mode in JB422 image through menus as well as commands on hyper terminal.
Problem:
ADB server on host machine detects the device in offline mode, because when i connect the RSA key dialog box appears on board that is needed to be clicked OK, after that i hope adb commands should work fine.
Setup:
1. sabresd board is connected with HDMI display
2. uart usb is connected to hyper terminal pc
3. usb otg is connected to the adb host machine without usb hub
Question:
How can i click on RSA key dialog box that appears on HDMI display, when the usb otg is connected to the ADB host?
My USB hub does not seem to solve the problem in this case ,it does not support ADB connection, i do it by directly connecting a usb cable..
Thanks.
Ashish Gupta
Hey Ashish ,
Since you have serial connection on host machine you can give command from there to click OK on HDMI display :
input keyevent 66 ; you can try 19,20,21,22 to navigate and 4 to go back .
It works in my jellybean sabreSD setup .
And regarding my problem i am trying to do same thing but when i give adb devices it doesn't show any device . Did you use any SDK for android cause i am suing that . And one thing you mentioned USB-OTG without HUB so i'll try that since i am using Hub . And can you tell me in detail how exactly did you use sdk (if you used ) .
Thanks & Regards
Brajesh Sharma
Hi,You said it,I used usb to uart console to commit PC's RSA.
input keyevent 66 //commit
input keyevent 19//left
input keyevnet 22//down
then sabre connectted to Android Studio by usb-otg
You can set a property ro.adb.secure=0 to bypass adb_keys checking.
I set it in my init.rc device/fsl/imx6/etc/init.rc. (It's enabled in default)
setprop ro.adb.secure 0
Hi Ashish,
It's kind of a shame the SABRE SD doesn't have a USB Host port so you could connect a mouse.
You should be able to copy your ADB public key from ~/.android/adbkey.pub to /data/misc/adb/adb_keys on the device.
It's a text file, so you should be able to do this from the serial console.
From what I can tell, the ownership needs to be system/shell and the permissions set to 644:
root@nitrogen6x:/data # ls -l misc/adb -rw-r----- system shell 715 1970-01-02 00:02 adb_keys
Hello Ashish,
Have you updated to the latest version in the Android SDK Manager? (API level, Tools and Extras)