I just had an idea. I know you can root some phones using ADB and I got to thinking. All android phones have an ADB daemon running in the background that you can connect to through usb on your pc using the ADB client application provided by google(adb.exe) and usb adb drivers provided by google.
Now that you can turn your phone into a USB host using USB OTG, wouldn't you be able to use your phone instead of a computer? With a Micro-B to Micro-B USB cable? Someone has already ported the ADB client to android(ARM-Linux ELF). So someone would just need to port over the drivers to android, and then we could connect to adb on one phone using another with a terminal emulator. Right?
What are your thought?
I have attached the adb and fastboot clients that were ported to android. (adb-fastboot for arm)
EDIT:
I found this for raspberry pi (which is arm based):http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=6130
So after reading a bit more it seems that the drivers aren't even needed. They are only needed when using ADB with windows. But, since Android doesn't use "udev" I don't know if or how android would recognize that another phone is connected.
Related
Hi, I want to got a windows tool works on ubuntu 9.10. It's used to communicate with the modem of my android phone. So I decided to use it via wine. But the tool just said it can't find usb port. What should I do? BTW, my android phone start up with two modes. When connector was plugged in, just the modem was power on, so it was detected to be a usb-serial device on windows. And if power on the phone, it was detected to be usb device on windows. Any ideas to support these two modes on ubuntu via wine?
Thanks a lot!
Okay, I know there are lots of posts about getting adb drivers to work on the g tablet but I can't seem to get to step 1. When I plug in my USB cable, my PC doesn't ask me to install anything. It just seems to assume that it is a USB drive. I tried to force the install via Install Hardware and pointed it to my modified android_winusb.inf file. When I did that it came up with three different options (Android ADB Interface, Android Bootloader Interface, and Android Composite ADB Interface). I tried all three but none of them will start successfully.
My cable connects to the mini-USB port (I have a keyboard connected to the full size USB port). I can't imagine that would make a difference, though.
I can copy files over to the g tablet from my PC; I just can't get ADB to work. What am I doing wrong?
First, you need to install the Android SDK on your computer. ADB shell is a program contained within the Android SDK. If you install the latest version, you also need to install "Android SDK Platform-tools" (launch the SDK and AVD Manager, then select the "Android SDK Platform-tools" package). You can connect the miniusb cable to your tablet and use adb shell, but I prefer to use adbwireless (free app in market); for some reason my computer won't recognize my tablet when connected via the cable. Then just open up cmd.exe (if you're using windows) and go from there. You'll need to locate the actual adb executable file, so you can run it in the command window. You'll also have to learn the commands as to how to do things, but lists of common commands can be found with a simple search.
I had problems with getting the debug usb drivers to install on a win7 dev machine. So I just installed adb wireless onto my gtab from the market. On my win7 box I just use 'adb connect x.x.x.xort' to use adb over the wifi.
It's pretty handy.
I figured it out. For others that run into this, I had to uninstall the drivers with USBDeview. I only uninstalled the one with a description of NVIDIA Tegra 2 USB Device. The second half of this YouTube video shows what to do for a phone:
youtube.com/watch?v=1UF5w1dKe2U
Then disconnecting and reconnecting the USB cable installed the drivers correctly. Weird.
Hi, I'm running Cyanogenmod 10.1.3 on my S3, the adb binary is up-to-date.
I'm trying to connect my S3 and my S4 or my S3 and my S Plus together via an OTG cable and usb debugging but it doesnt work.
The device gets listed but as "offline". Usually you get an prompt to accept the RSA key and you're done - that works if I connect any device to my PC - but if I want to connect any 2 devices together I just get an offline device and I have no idea why there is NO prompt at all.
Does anyone have an idea? Is therw any workaround?
Basically I just want to connect 2 devices (target >= 4.2.2) together via an otg host cable and adb.
Cheers
chris331022 said:
Hi, I'm running Cyanogenmod 10.1.3 on my S3, the adb binary is up-to-date.
I'm trying to connect my S3 and my S4 or my S3 and my S Plus together via an OTG cable and usb debugging but it doesnt work.
The device gets listed but as "offline". Usually you get an prompt to accept the RSA key and you're done - that works if I connect any device to my PC - but if I want to connect any 2 devices together I just get an offline device and I have no idea why there is NO prompt at all.
Does anyone have an idea? Is therw any workaround?
Basically I just want to connect 2 devices (target >= 4.2.2) together via an otg host cable and adb.
Cheers
Click to expand...
Click to collapse
Push
Push again - I'm also interested in that.
P.P.Push
Push
Sent from my GT-I9300 using XDA Premium 4 mobile app
..and again. :fingers-crossed:
Push
No one? Push..
Push
Adb on phone...
Well, I've been trying to get it though...have a SGW with kitkat rom and a SGT3 10.1 LTE on 4.2.2. Understand that the device need RSA auth to get it online. But the thing is, how to get it pop when we connect though phone. Updating the ADB on PC would help. So far, it works on kali linux (Serch for p2p-adb setup on kali linux tutorial [noob-friendly] by Jacker31). If we can get the adb updated on p2padb phone version...it might works.
Can someone explain me how to get ADB working on my SGS8? I've tried everything: installing drivers, Java, Android SDK, 15 sec adb driver, universal ADB driver, minimal adb. I can't figure out how to do that.
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
jaannnis said:
Do what? Get an ADB shell with a pc?
Just install the samsung drivers from here, enable debugging in developer options on your phone and connect via usb
Click to expand...
Click to collapse
Thanks, will try that
i was having one hell of a time as well. I tried everything on my laptop to no success. So i actually gave up. Than i thought well maybe its my laptop. So i ended up trying another one i had in the house and viola it worked like a charm. It seems like certain pc are just unable to connect to the samsung s8 via adb mode. Which is totally weird because I had been using adb mode on my pixel xl with no issues what-so-ever. So try a different pc if you can, it worked for me flawlessly.
Might be the USB port.
I had a similar problem connecting my Lenovo laptop to a Kindle Fire. I used a different USB port and everything worked.
9 bin
Hello,
I recently got a Pixel 2 on stock Android 11 with the intent of flashing LineageOS + rooting. But I haven't had any luck getting ADB to recognize the phone so far. I am using Windows 10 and Ubuntu Linux 20.04 LTS.
As a prerequisite, I enabled developer options, USB debugging, and OEM unlock.
I'm pretty sure the USB port of the phone is okay because the phone still fast charges.
Here's what I've tried:
- using Minimal ADB (device does not appear when adb devices is run)
- using platform-tools ADB (same as above)
- using wireless ADB (ADB is able to pair but the phone still doesn't appear when adb devices is run)
- checking Device Manager (device does not appear)
- Installing Google USB drivers
- using OEM cables from Samsung and other Android OEMs
- using a micro USB cable with a micro-to-C adapter
- using a USB hub
Am I missing something? What should I be doing to get my phone to be recognized by my computer?
Thank you in advance.
Hi, sounds like you've tried all the usual trouble shooting bits with cables, ports etc. Only other things I can think of at a stretch are to try enabling file transfer when you connect to a pc and see if that makes any difference or booting into bootloader via the button combo from powered off and then running fastboot devices from your adb and fastboot to see if it is recognised in fastboot mode?